Workflow Due Dates
The [AWE] Workflow Due Dates job reacts to items that passed the deadline of the state they are in. Deadlines are configured per state, see States — without a due period on a state there is nothing for this job to find. Open its configuration via the Scheduler admin module and pick [AWE] Workflow Due Dates as the job type.
| Overdue Workflow Items | |
|---|---|
| A list of entries, each watching one workflow. | |
| Enabled | Disabled rows are kept in the configuration but ignored at runtime. |
| Workflow | The workflow to watch. |
| State | The state whose overdue items are handled. The drop-down offers All states plus every state of the workflow that has a due period configured — a state without one can never produce an overdue item. |
| When Overdue | Send a Reminder E-Mail or Apply a Transition. Apply a Transition is only available for a single state: a transition leaves one named state, so there is none that fits every item an All states entry finds. Switching an entry to All states therefore falls back to the reminder. |
| When an Item is Overdue - Send a Reminder E-Mail | |
|---|---|
| E-Mail Template | The reminder to send. The drop-down lists the templates of type AWE - Workflow Due Date Reminder; with exactly one such template it is used automatically. See E-Mail Notifications. |
| Also Notify the Members of an Assigned Group | Expands an assigned group to its members. Off by default. |
| When an Item is Overdue - Apply a Transition | |
|---|---|
| Transition | The escalating transition, for example one that moves the item to a supervisor's state. The drop-down lists the transitions leaving the selected state. |
| History Comment | The comment recorded in the history when the transition is applied. |
What the job does when it runs
For every enabled entry:
- Resolves the workflow and the state. Missing, disabled, unconfigured or invalid workflows, deleted states and an escalation entry without a transition are reported, and the run fails with the list of entries that could not be run.
- Looks for the items whose deadline lies in the past, narrowed to the configured state.
- Sends the reminder to the item's assignees, or applies the escalating transition.
- Continues with the next item when one is rejected.
A reminder writes nothing onto the item, so the job's cron schedule is the reminder frequency — a job running daily reminds daily until the item moves on. Choose the schedule accordingly.
An escalating transition moves the item into another state and therefore stamps that state's deadline, if it has one. Reminders and escalation can be combined by configuring two entries for the same workflow on different schedules — put them in two jobs, since the schedule belongs to the job, not to the entry.