Essentially an extension of the scheduled trigger, not only does a recurring trigger allow you to specify the date and time at which a workflow will start, but also the number of instances of the workflow that will execute, in addition to a wealth of recurrence options. As a simple example, you could use a recurring trigger to initiate regular, monthly campaigning activity across a whole year.
The following options are available in the mini toolbar when you select a recurring trigger:
•Activate/Deactivate trigger:
o If the interaction contains no unsaved changes, the workflow’s active status is Inactive and the interaction contains no validation errors, the button is enabled and its tooltip reads Activate trigger. Invocation causes the workflow to enter a Waiting for Trigger state.
o If the workflow’s status is Inactive and the interaction has validation errors, the button is enabled and its tooltip reads Activate trigger. However, attempting to activate the trigger causes display of a warning message, and the workflow is not activated.
o If the workflow’s status is Waiting for Trigger and a workflow instance has not yet been created, the button is enabled and its tooltip reads Deactivate trigger. You can re-activate the trigger if required.
o If the workflow’s status is Waiting for Next Trigger, the button is enabled and its tooltip reads Deactivate trigger. Invocation causes the workflow to assume a Completed status. You can re-activate the trigger if required.
o If you have created a workflow instance in a production recurring workflow, you can make changes to its configuration post-deactivation.
o If you deactivate a production recurring workflow that has yet to create a workflow instance, you can make changes to its configuration.
o You cannot execute in Test mode a deactivated Production recurring workflow.
•Rollback current Workflow Instance: only available post-completion of production execution. Removes the most recent workflow instance entirely.
•Fire trigger: fires trigger immediately, creating the next workflow instance.
•Play/Pause workflow instance:
o If the currently-executing activity’s status is Playing, the button is enabled and its tooltip reads Pause workflow instance. Invocation pauses the workflow instance.
o If the currently-executing activity’s status is Paused, the button is enabled and its tooltip reads Play workflow instance. Invocation plays the workflow instance.
o If the currently-executing activity’s status is not Playing or Paused, the button is disabled.
•Stop workflow instance: only available if the currently-executing activity’s status is Playing or Paused.
•View results: displays the Results Window, within which the current workflow’s results are displayed.
•Show configuration panel
A recurring trigger’s configuration panel contains a single tab (General):
The General tab contains the following properties:
Trigger section:
•Create: this dropdown field allows you to define whether the recurring workflow will create a single or multiple workflow instances. It exposes the following values:
o Single workflow instance: the default value. If this is selected, when the trigger is activated, a single workflow instance will be created. Any contacts targeted within the workflow will only ever be contacted once.
o New workflow instance each time trigger fires: selecting this option allows the recurring trigger to be responsible for the creation of multiple workflow instances. If a contact is targeted within a workflow instance, he or she may also be contacted within the others, meaning that the recurring trigger can be responsible for the same person receiving communications multiple times.
•Start at: the date and time at which to commence creating workflow instances. Start at defaults to the date and time at which the trigger was added to the interaction.
It refers to the date and time at which the system will begin checking as to whether to create a new workflow instance; for example, if set to 06:00 and scheduled to fire Daily, Once every 1 day at 18:00, the trigger would fire at 18:00, not 06:00. Between 06:00 and 18:00 the trigger's status would be Waiting for Trigger.
An information icon is displayed to the right of the property. Hovering over it displays a tooltip:
You can specify Start at manually, or by using a calendar control. Provision of a Start at date/time is mandatory.
•’and’: a dropdown is provided, exposing the following values, each of which necessitates additional configuration:
o never end: selection of this value specifies that the recurring trigger will continue creating workflow instances, in accordance with its configuration settings, in perpetuity. No other configuration accompanies selection of this value
o end after: this value is selected by default and indicates that the trigger will create a specific number of workflow instances. When selected, an accompanying text field is displayed (‘event(s)’) that defines the number of workflow instances to be created. Provision of this integer value, which defaults to 2 and which must be greater than 0, is mandatory.
o end by: if this value is selected you must define a date and time at which the recurring trigger will cease creating workflow instances. The date defaults to today’s date + 1 week; the time defaults to the trigger’s original Start at time (the time at which the trigger was added to the interaction). You can set the date/time manually, or by using a calendar control.
Recurrence section:
•Daily/Weekly/Monthly/Manual: four tabs are presented within the section. Selection of one of Daily, Weekly, Monthly or Manual defines the basis upon which workflow instances will be created by the recurring trigger.
•Daily is selected by default. If selected, the following fields are shown :
o Once every…: this field is accompanied by a radio button that is selected by default (its counterpart is Every…, which is also accompanied by a radio button). If the radio button is selected, the following fields are enabled:
§ Day(s): a mandatory integer that defaults to 1, and which must be greater than 0.
§ At: separate, mandatory hour and minute fields that default to the time the trigger was added to the interaction. An information icon is displayed to the right of the properties. Hovering over it displays a tooltip:
o Every…: this field is accompanied by a radio button and is a counterpart to Once every…. If selected, the following fields are enabled:
§ Duration: a mandatory integer that defaults to 1, and which must be greater than 0.
§ [units]: a dropdown field exposing the values minute(s) and hour(s) (the default).
§ From: a mandatory hour and minute field that defaults to 00:00. An information icon is displayed to the right of the property. Hovering over it displays a tooltip:
§ To: a mandatory hour and minute field that defaults to 23:59. An information icon is also shown to the right of the property.
§ Only fire trigger on specific days of the week: this switch allows you to specify that the trigger should only fire on the selected day(s) of the week. It is switched off by default. When on, separate checkboxes are displayed for each day of the week. All are checked by default.
§ If firing missed, trigger will fire as soon as able to. Thereafter: this property is displayed when a recurring trigger's Recurrence is set to Daily, Every... is selected and units is set to hour(s). It allows you to define the action to be taken when an hourly trigger is unable to fire. A dropdown field, it exposes the following values:
•'Commence hourly schedule based on new most recent firing time' (the default)
•'Continue original hourly schedule based on Start at time'
When set to Commence..., if the trigger fails to fire due to the Node Manager service's unavailability:
•The trigger fires as soon as the service becomes available.
•The next firing time occurs in one hour's time.
•An hourly cadence is maintained thereafter.
When set to Continue...:
•The trigger fires as soon as the service becomes available.
•The next firing time occurs when the trigger's Start at time is reached.
•An hourly cadence is maintained thereafter.
•If Weekly is selected, the following are shown to the right of the General tab:
o ‘Every’
o Week(s): a mandatory integer that defaults to 1, and which must be greater than 0.
o At: a mandatory hour and minute field that defaults to the current time. An information icon is displayed to the right of the properties. Hovering over it displays a tooltip:
o on: one separate checkbox is provided for each day of the week. The current day is checked automatically.
•If Monthly is selected, the following fields are shown to the right of the General tab:
o Specific day of month: accompanied by a radio button that is selected by default (its counterpart is Relative day of month, which is also accompanied by a radio button). If the radio button is selected, the following are enabled:
§ Day: a mandatory integer, which must be greater than 0. Day [x] defaults to today’s date.
§ Of Every: a mandatory integer that defaults to 1, and which must be greater than 0.
§ ‘month(s)’
§ At: a mandatory hour and minute field that defaults to the current time. An information icon is displayed to the right of the properties. Hovering over it displays a tooltip:
o Relative day of month: accompanied by a radio button and is a counterpart to Specific day of month. If selected, the following fields are enabled:
§ On The: a dropdown field that exposes the following values: first (default), second, third, fourth and last.
§ [Day of week]: a dropdown that lists the days of the week, which defaults to the current day. In addition, two other values – weekday and weekend day – are also available
§ Of Every: an integer that defaults to 1.
§ ‘month(s)’
§ At: a mandatory hour and minute field that defaults to the current time. An information icon is displayed to the right of the property. Clicking it displays a tooltip:
o Offset By: two fields accompany this setting, which allows you to adjust the trigger’s scheduled firing time by pulling it forward or pushing it back by a given number of days:
§ [n]: this integer value defaults to 0 and can be maximum of 999.
§ [offset type]: this dropdown field exposes values ‘None’ (the default), ‘day(s) after’ and ‘day(s) before’.
•Manual tab: allows you to fire the trigger on an ad hoc, manual basis.
•Time Zone: this dropdown property allows you to specify the time zone within which the trigger's recurrence pattern will operate. It defaults to the local time zone. Note that the specified time zone only affects the trigger's recurrence once active; its Start time will be acted upon on a local basis. Note also that changing the Time Zone will have an effect on the displayed time, which may need to be adjusted to reflect the selection.
•Input Workflow: optionally, you can elect to define an input workflow for the recurring trigger. This property is documented separately elsewhere as it shared across all trigger types.
Note that all time values specified reference your local time setting.
Constraints and Input Workflow sections are displayed. They are covered separately in this documentation.