Write messages for rules and conditions
Rules, condition sets and conditions each have three optional message fields. When a record matches, the messages from the matching parts are combined into a summary, which you can put into emails, SMS or WhatsApp messages, and API requests.
The three message fields
| Field | Use it for |
|---|---|
| Message (API / default) | The standard wording. It's used by the plain summary token and is ideal for recording in another system through an API request. |
| Email message | Wording for emails. |
| SMS message | Wording for SMS and WhatsApp. Keep it short, as messages are capped at 1,600 characters. |
How messages are combined
For each record, AutomatedOn goes through every matching rule and adds, one per line:
- the rule's message
- the message of each condition set that matched
- the message of each condition in that set that matched
Because the rule's and condition set's messages come first, they act as headings for the condition messages below them. That's why the rule pages on the AutomatedOn site label them Message prefix, Email prefix and SMS prefix. Conditions that didn't match are left out, so with Any you only see the reasons that applied.
Example
- Rule message:
This learner may not be eligible: - Condition message:
Date of birth $$DateOfBirth:dd/MM/yyyy$$ is outside the age range.
gives:
This learner may not be eligible:
Date of birth 04/03/2009 is outside the age range.
Using record values
- Write
$$FieldName$$to insert a field from the record. - Add a date format after a colon, such as
$$StartDate:dd/MM/yyyy$$or$$StartDate:d MMMM yyyy$$. Dates that include a time zone are shown in UK time. - If a field name isn't found, the token is left as written, which makes typos easy to spot on the process's Test tab.
Good to know
When you choose email or SMS wording in the summary token, items whose email or SMS message is empty are left out. They don't fall back to the default message, so fill in every level you want to appear.