You can use variables in workflows to add customized details to notifications and task messages. The main benefit of variables is that you need only one message template to get a variety of unique messages without any additional actions.
Each time a trigger event occurs, Kladana generates a notification or task message and replaces variables used there with relevant transaction details. So your teammates always receive clear tasks and notifications.
Default templates
Customer Service prepared some message templates. You can simply copy them to the message field when creating a workflow.
- Verify order picking for {DOCUMENT_NAME}.
- Payment on the {DOCUMENT_NAME} is overdue. Send {COUNTERPARTY} a payment reminder letter.
- Contact {COUNTERPARTY} and confirm the total cost {OPERATION_SUM} of their {DOCUMENT_NAME}.
- Prepare shipping documents for {DOCUMENT_NAME} to ship order by {PLANNED_SHIPPED_DATE}.
If default templates don’t suit your needs, you can create your own templates using variables listed in the table.
List of supported variables
This table provides a complete list of variables that you can use in workflows. You can add them to the title line and body of your message.
When adding a variable enclose it in the set of curly braces.
| Variable | Description |
| {ACCEPTED} | The amount received by customer invoice. |
| {APPLICABLE} | Status of the transaction confirmation: confirmed or draft transaction. |
| {COMMENT} | A comment text added to the transaction. |
| {CONTRACT} | The name of the contract linked to the transaction including a contract number and agreement date. |
| {COUNTERPARTY} | The name of the customer or supplier depending on the transaction type. |
| {CURRENT_DATE} | Date and time when trigger event occurred. |
| {DOCUMENT_NAME} | Full transaction name including transaction type and transaction number. |
| {OPERATION_DATE} | The date transaction was created. |
| {OPERATION_SUM} | The total amount of purchase or customer order. |
| {ORGANIZATION} | The name of your company. |
| {OWNER} | The name of a team member who owns the transaction. |
| {PAYED} | The amount you paid to the supplier. |
| {PLANNED_ACCEPTANCE_DATE} | The date you wish to receive products. |
| {PLANNED_PAYMENT_DATE} | The latest date payment can be made. |
| {PLANNED_SHIPPED_DATE} | The date you plan to ship the order. |
| {PROJECT} | The name of a project linked to the transaction. |
| {RETURNED} | The amount of returned order. |
| {SHIPPED} | The amount of shipped order. |
| {STATUS} | The current transaction status. |
| {TEMPLATE_NAME} | The name of the running workflow. |