Every input field in a node accepts a fixed value or a variable of the collection order. This lets you base, for example, the due date, a document name or a condition on data from your delivery. If a variable gives an unusable value, the collection order stops with an error and an employee gets a task.
Which variables are there
| Group | Examples |
|---|---|
| Customer | customer number, name, language, gender, email address, phone number, address, label |
| Collection order | payment reference, description, amount, type, invoice lines, due date, creation date, batch |
| Status | payment status, days past the due date, reminder phase |
| Free variables | variable 1 to 500, filled from your delivery (for example contract number, gross rent, department) |
| Outcome of a calculation node | the variable in which a calculation is stored |
You choose a variable from a list in the field; do not type the name yourself.
Where you use variables
- Logic: "amount greater than 1000" or "variable 5 equals BUSINESS".
- Calculate: "amount * 0.15" or "due date + 14 days".
- Create document: the document name, for example "Invoice #INVOICE1_NUMBER#".
- Add costs: invoice number and description of the cost line.
- Create task: title and text of the task.
If a variable cannot be used
If a variable is empty or has the wrong type (for example text where a number should be), the collection order goes to Error and becomes a task for an employee. Correct the data and resume the collection order.
Good to know
- Give free variables a name in Settings > Workflows > Labels and variables; then the editor shows "Gross rent" instead of "Variable 35".
- Variables with their own name and data type (named variables) are planned, so comparisons and calculations become more reliable.
- In templates you use the same data as
#VARIABLE#fields. See Variables in templates.