Recurring Tickets
On this page
A recurring ticket is a stored set of answers to a Create Action's form, plus a schedule. On each scheduled run, the service creates one ticket by executing that Create Action with the stored answers.
You create recurring tickets in the Web App, where the form carries the whole definition. The Settings App side, which changes only the schedule and the enabled state of an existing recurring ticket, is covered in Scheduled Tasks.
Recurrent Create Actions exist for Incidents, Problems, Change Requests, and Work Orders, not for Service Requests. A Create Action is recurrent when its Available for setting is Recurrent Tickets only or Regular and Recurrent Tickets. For Create Actions in general, see Workflow Overview. For the ticket classes, see Tickets.
In the Web App
Before you begin
- The Recurrent Tickets list is shown only to technicians who have the right to manage recurring tickets. See Permissions Reference.
Create a recurring ticket
- In the sidebar, open the Recurrent Tickets list in the Miscellaneous group.
- From the list's new-object choices, choose the entry for the Create Action you want to recur. There is one entry per recurrent Create Action, captioned with the ticket class's name, a colon, and the action's caption (or its name when the caption is empty). The recurring-ticket editor opens.
- On the General tab, enter a Name (required). Category is an optional free-text box with no list of values behind it. Description is also available.
- Next to Recurrence Schedule (required), click the edit icon at the end of the box, set the schedule as described in Set the schedule, and click OK. OK checks the schedule and writes its description into the Recurrence Schedule box.
- On the Data tab, fill in the fields of the Create Action that the recurring ticket runs.
- On the General tab, select or clear Enable Recurrence. When it is cleared, the recurring ticket is saved switched off.
- Click OK to validate and save the recurring ticket. If validation returns a message, it is shown before the save continues.
The editor's Cancel button closes it without asking. Closing the editor in another way while it has unsaved changes asks you to confirm first.
Set the schedule
The schedule panel opens with an Occurs choice of Daily, Weekly, Monthly, or Yearly; next to it are the chosen pattern's own fields. A new recurring ticket opens on Weekly, every 1 week, with Monday selected.
- Daily: Every N day(s), from 1 to 366.
- Weekly: Every N week(s) on, from 1 to 52, and a check box for each day from Monday to Sunday. Select any combination of days. If you select none, OK refuses with "You must choose at least one day of the week".
- Monthly: one of two rows. Day N (1 to 31) of every N (1 to 99) month(s), or The followed by First, Second, Third, Fourth, or Last, and a day (Sunday to Saturday, Day, Weekday, or Weekend day), of every N (1 to 99) month(s). The row you do not choose stays visible but unavailable. The two rows keep separate month counts.
- Yearly: Months, a list of the twelve months with a Check All entry. Below it, choose day(s) to pick days from 1 to 31 and Last, or On to pick one or more of First, Second, Third, Fourth, and Last together with one or more weekdays; for example, the first and third Monday and Friday. Months and each list of the option you chose must have at least one value; OK refuses an empty one with a message such as: The "Months" field is mandatory, it can't be left blank.
The Daily and Weekly counts cannot be left empty or out of range: an empty or too-low value becomes 1, and a value above the maximum shows as the maximum.
When you switch to a pattern that the saved schedule does not use, that pattern starts with its own values: Daily every 1 day; Weekly with Sunday selected; Monthly on Day 1 of every 1 month, with the other row preset to First Weekend day.
Below the pattern:
- Daily frequency: Occurs once at: a time, or Occurs every: an interval, between Starting at and Ending at.
- Duration: Start Date, and either End Date or No end date.
On Alloy Navigator Cloud, the Occurs every: interval starts at 15 minutes instead of 1, and a lower value typed while the unit is minutes is raised to 15 when you leave the field; see Administering Alloy Navigator Cloud.
The description that OK writes into the Recurrence Schedule box, such as "Occurs every 1 day(s)", is in English whatever your interface language.
Change or delete a recurring ticket
The Recurrent Tickets list shows each recurring ticket's name, next and last run dates, last run status, enabled state, and schedule, sorted by name. Opening a row opens the saved recurring ticket in the current page, not in a new tab. There you can change any of its fields, or clear Enable Recurrence to save it switched off.
To delete recurring tickets:
- On the Recurrent Tickets list, select one or more rows.
- Click Delete on the toolbar.
- When asked "Are you sure you want to delete the selected item(s)?", confirm.
The list clears the selection and refreshes.
Review the runs of a recurring ticket
An existing recurring ticket's editor also has a Sessions tab that lists its runs. Opening a row shows that run's log text. Delete removes the selected sessions, and Clear All removes all of them; Clear All is unavailable while the list is empty.
What happens when a recurring ticket runs
- Each run creates one ticket by executing the Create Action as a technician would: it starts from the action's template defaults, applies the stored answers, and copies the recurring ticket's stored attachments onto the new ticket. The new ticket's number is recorded in the run's history.
- Recurring tickets run one at a time. Two recurring tickets never run at the same time, even when their schedules coincide.
- If the Create Action has been disabled, the run fails, and its remark reads "Create action name, # n is disabled".
- If the Create Action no longer exists, the run ends without creating anything and without an error.
- If the Create Action is changed so that it is no longer recurrent, every recurring ticket built on it stops running. The recurring tickets are kept.