Messages can be sent out periodically (Time Period Trigger) and on-demand (e.g. when an Event starts or ends, or when a limit is exceeded for a specified interval)
The "Message Triggers" tab in the Message configuration screen defines when a message will be compiled and sent.
A trigger can be one of the following types:
|
This defines a scheduled trigger based on a Calendar period (e.g. daily). |
|
This defines an event trigger based on an Event definition (e.g. end of batch). |
|
This defines a limit trigger based on a measure’s limit being exceeded (e.g. temperature too high). |
Right-click in the Message Triggers section to create a new “Trigger”.
The “Time Period Trigger” has the following properties:
|
Either the start or the end of the period, in this case “Daily” (e.g. at the end of the day). |
|
This specifies which calendar the time period is derived from. If the calendar’s day starts and ends at 06:00, then this will be the time period used for “the end of the day” trigger evaluation. |
|
This is a number of seconds after “the end of the day” that Flow will attempt to compile the message contents. A default value of 300 seconds (i.e. 5 minutes) is set. If you find that some information is not being provided in the compiled messages, you may need to increase this value. |
|
This is the number of seconds after “the end of the day” that Flow will send the message. If the delay is set to the same value as the Refresh Offset, then Flow will send the message as soon as it is compiled. If “the end of the day” is 06:00, you may want to set the delay to 1800 seconds (i.e. 30 minutes) to send the message at 06:30. |
The “Event Period Trigger” has the following properties:
|
Either the start or the end of the event, in this case “End of every” (i.e. at the end of the Event). |
|
This specifies which event the time trigger is derived from. All events configured will be displayed in the drop-down next to the “When to trigger” section. |
|
This is the number of seconds after “the end of the day” that Flow will attempt to compile the message contents. A default value of 300 seconds (i.e. 5 minutes) is set. If you find that some information is not being provided in the compiled messages, you may need to increase this value. |
|
This is the number of seconds after “the end of the day” that Flow will send the message. If the delay is set to the same value as the Refresh Offset, then Flow will send the message as soon as it is compiled. If “the end of the day” is 06:00, you may want to set the delay to 1800 seconds (i.e. 30 minutes) to send the message at 06:30. |
The “Limit Exceeded Trigger” has the following properties:
|
A measure can be dragged from the model to serve as a trigger when a limit exception occurred on the measure value for its latest time period. |
|
This specifies whether the limit is based on a calendar time period or based on event context. Limits must be enabled on the event context on a measure to be available in the drop-down. |
|
Select the relevant Limit to be a source for the trigger as multiple limits can be configured on a single measure. |
|
This is a number of seconds after “the end of the day” that Flow will attempt to compile the message contents. A default value of 300 seconds (i.e. 5 minutes) is set. If you find that some information is not being provided in the compiled messages, you may need to increase this Refresh Offset. |
|
This is the number of seconds after “the end of the day” that Flow will send the message. If the delay is set to the same value as the Refresh Offset, then Flow will send the message as soon as it is compiled. If “the end of the day” is 06:00, you may want to set the delay to 1800 seconds (i.e. 30 minutes) to send the message at 06:30. |