AWE ships as a single plugin that is installed from the normal plugin registry: [AWE] Attention Workflow Engine. It contains everything at once — the ACC authoring module, the scheduler jobs, the transition actions and the native Fylr plugin for the web frontend.
The AWE Fylr plugin contributes one setting to Fylr's base configuration, Workflow execution → Run transitions as user. It decides whose Fylr permissions are used to read and change an item when a transition is applied in the Fylr web frontend:
| (empty) | The permissions of the user who applies the transition. This is the default: a user can only move items forward that they may edit themselves. |
| a user | The permissions of this fixed account. Use it when users should be able to move items through the workflow without being given write permission on them. The applying user still needs read permission: items they cannot see are left unchanged. |
The setting does not change who the transition counts as. The workflow's own conditions — Restrict to Users or Groups, Restrict Assigned Items to Their Assignees and Require a Comment — are always evaluated against the user who applied it, an Assign to User Applying the Transition step assigns that user, and it is their name that is written into the history. Only the item permissions come from the configured account. If Fylr cannot tell which user applied the transition, it is refused.
The fields a workflow needs are created when the workflow configuration is saved. When an update introduces a new one, open the ACC Workflow Engine module and save once — the fields of every workflow are created together, there is no need to visit each workflow. Until that save, applying a transition reports a missing field.