Recurrence

The figure below shows the “Recurrence” tab which allows a user to create recurring actions. A recurring action is a special type of action in ATMS™ which allows the user to create an action once, and then have it recreated automatically after a designated time interval.

Any user with permission to create actions can create recurring actions. Existing non-recurring actions can also be converted into recurring actions.

The “Recurrence Tab” on Action Edit Screen can be used to create a Recurring Action. Actions can recur by day, week, month or year. To create a recurring action simply edit an existing action or create a new one and click on the “Recurrence” tab. Select the frequency (daily, weekly, monthly or yearly) at which you want the action to recur. Depending upon the frequency selected other recurrence options will be available, such as the option to “Copy Custom Controls Data” and the option to “Not Send E-mail on Recurrence”. Setting an end date will stop the action recurring as soon as the date is reached.

If you don’t want the action to stop recurring after a certain date, then leave the recurrence end date as blank. Once an action is configured for recurrence, then when that action reaches its due date it will recur – a new copy will be made. When that new copy of the action will recur will depend on the setting you have chosen.

Recur by Day

This example shows an action which is configured to recur by day. If an action is configured to recur after every three days and it was created on 01/01/2018 with due date 02/01/2018 then the first time it will be recreated on 02/01/2018 with due date of 05/01/2018 and the second time will be recreated on 05/01/2018 with due date 08/01/2018 and so on until recurrence end date, if set, is reached.

Recur by Week

This example shows an action which is configured to recur by week. If an action is configured to recur after every 4 weeks on Tuesday (every 4th Tuesday) and it was created on 01/01/2018 with due date 02/01/2018 then the first time it will be recreated on 02/01/2018 with due date of 30/01/2018 and the second time will be recreated on 30/01/2018 with due date 27/02/2018 and so on until the recurrence end date, if set, is reached.

Recur by Month

This example shows an action which is configured to recur by month. If an action is configured to recur after every 2 months on the 31st day of the month and it was created on 31/01/2018 with due date 31/03/2018 then first time it will be recreated on 31/03/2018 with due date of 31/05/2018. If there is no 31st day in the month then it will be replaced with the last day of the month. The second time will be recreated on 31/05/2018 with due date 31/07/2018 and so on until the recurrence end date, if set, is reached.

Recur by Year

This example shows an action which is configured to recur by year. If an action is configured to recur after every 2 years on the 19th of February and it was created on 31/10/2018 with due date 31/12/2018 then the first time it will be recreated on 31/12-2018 with due date of 19/02/2018 and the second time it will be recreated on 19/02/2018 with due date 19/02/2020.

Copy Custom Controls Data

The “Copy Custom Controls Data” checkbox is used if custom controls are used for the action screen and the user wants to copy the data of those controls into the recurred actions.

This option is provided because if the user populates the custom controls at different review stages then copying the data for those controls into the new recurred actions doesn’t make any sense. By default, custom controls data will not be copied into recurred actions until this checkbox is ticked.

An extra column is included to flag recurring and recurred actions. This icon represents recurring actions and any recurred actions are represented by this icon .

If there is a small green arrow appearing on a recurring action, then by clicking on it a user can view a list of all the actions recurring from this action as shown.

Audit and Action Notes
Reminders