A Scheduled Trigger starts an Assignment of a Procedure on a recurring schedule, such as every Monday and Wednesday or on the first of each month. Portfolio Administrators and Leads may create Scheduled Triggers. A Procedure's Triggers start Assignments only while the Procedure is Published.
Create a Scheduled Trigger
- Select the Procedure and press the Triggers tab in the detail pane.
- In the Scheduled panel, press the create button to open the Create Trigger dialog.
- In Assignment Details, describe the Assignments this Trigger will start:
- Name: the name each Assignment gets.
- Assignee (optional): who the Assignments go to. Leave it empty to use the Procedure's Default Assignee. The line below, such as "Assignments go to: Position: HR Generalist (currently Bobbe Thomas)", shows who will get them.
- Priority.
- Requestor (optional): who the Assignments are for. The Trigger starts them on its own authority, so leave it empty unless a member asked for this work.
- Description: context for whoever does the work.
- In Inputs, supply the Fields the Procedure takes in on every Assignment. Any you leave empty can be captured after the Assignment starts.
- In Staff Roles, choose who fills each Role on every Assignment. A required Role must be staffed; an optional Role left empty falls back to the Assignment's Assignee, then to a Portfolio Administrator.
- In Recurrence, set the schedule:
- Start: the date and time of the first Assignment.
- End: Never, On a date and time, or After a number of occurrences.
- Repeat Every: a number of Day(s), Week(s), Month(s), or Year(s). For weeks, choose the days On which to start.
- Press Save.
The Scheduled panel lists each Trigger's Assignment Name and Recurrence, such as "Every week on Monday and Wednesday at 8:49 PM". Press a row to edit it, or use its menu to Edit or Delete it.
When a Scheduled Trigger has a problem
- Needs staffing: a required Role on the Trigger is unstaffed. Hover over the label to see which Role, then edit the Trigger to staff it.
- Stopped: the Trigger failed to start Assignments several times in a row, so TaskTrain stopped it and e-mailed the Portfolio's Administrators. Hover over the label to see why. Fix the cause, then republish the Procedure to start the Trigger again.
Unpublishing a Procedure pauses its Scheduled Triggers; publishing it again resumes them. If a member named on a Trigger leaves the Organization, TaskTrain clears them from the Trigger and it keeps running, following the Procedure's own Default Assignee.
Related Articles
Overview
Step-by-Step
