awe:job-autostart
Workflow Autostart
The [AWE] Workflow Autostart job puts items that are not in a workflow yet into one, by applying one of its initial transitions. It is what makes items created outside the user interface — an import, a hotfolder, another scheduled job — enter a workflow without anybody clicking. Open its configuration via the Scheduler admin module and pick [AWE] Workflow Autostart as the job type.
| Autostarted Workflows | |
|---|---|
| A list of entries, each starting items in one workflow. | |
| Enabled | Disabled rows are kept in the configuration but ignored at runtime. |
| Workflow | The workflow to start items in. Only its target table is processed. |
| Initial Transition | The transition to apply. The drop-down lists only the initial transitions of the selected workflow, and is rebuilt when the workflow is changed. |
What the job does when it runs
For every enabled entry:
- Resolves the workflow and the transition. Missing, disabled, unconfigured or invalid workflows and transitions that are not initial are reported and skipped, without stopping the other entries.
- Looks for the items of the workflow's target table that are not in this workflow yet, i.e. that are in none of its states.
- Narrows that set with the transition's Only Items Matching query when it has one.
- Applies the transition to every item found. An item that is rejected is logged and the run continues with the next one.
- Reports per entry how many items were started.
An initial transition that requires a comment can never be autostarted — the job has no comment to supply. Use the Only Items Matching restriction instead if the intent was to limit which items start.
awe/job-autostart.txt · Last modified: (external edit)