The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
| # | Surface | Action | Capability | Expected | Provenance |
|---|---|---|---|---|---|
| 1 | listWorkflowTriggerPoints | List the host’s available timers and its registered event trigger. | CAP-PFM-INT-018 | The listing includes host timers, the event trigger and its registered event. | test services-platform:modules/workflow-actions/tests/e2e/workflow-actions.e2e.spec.js#lists the automation host’s points: the timers of every host, `event`, and the registered event |
| 2 | listWorkflowActionTypes | Inspect the action types available for this trigger. | CAP-PFM-INT-018 | Only configurable, enabled action types appear. | test services-platform:modules/workflow-actions/tests/e2e/workflow-actions.e2e.spec.js#lists the types configurable at a trigger, the switched-off one left out |
| 3 | createAutomationRule | Create an automation for the event. | CAP-PFM-INT-020 | A draft is associated with the application that owns the event. | test services-platform:modules/workflow-actions/tests/e2e/workflow-actions.e2e.spec.js#creates it as a draft, owned by its event’s application |
| 4 | saveAutomationRuleDraft | Save a condition and the two actions in the draft. | CAP-PFM-INT-020 | The editable draft retains the configuration. | test services-platform:modules/workflow-actions/tests/e2e/workflow-actions.e2e.spec.js#saves the draft in place |
| 5 | publishAutomationRule | Publish the automation. | CAP-PFM-INT-020 | The rule becomes enabled with a frozen first current version. | test services-platform:modules/workflow-actions/tests/e2e/workflow-actions.e2e.spec.js#publishes it, enabled, with the version as its current one |
| 6 | listWorkflowActionRuns | Inspect the shared run list. | CAP-PFM-INT-020 | Runs are visible across applications when host views supply them; without those views the list is empty. | test services-platform:modules/workflow-actions/tests/e2e/workflow-actions.e2e.spec.js#answers the tenant’s runs as a page, empty while no host publishes a view |
| Path | From step | Condition | Path taken | Outcome | Provenance |
|---|---|---|---|---|---|
| failure | 5 | No application registers the selected event | Reject publication and identify the missing registration | Leave the draft editable | test services-platform:modules/workflow-actions/tests/e2e/workflow-actions.e2e.spec.js#refuses a publish of an event no application registers, naming the problem (400) |
| Id | Statement | Provenance |
|---|---|---|
01 | Publication requires eligible actions and the permissions their types require. | test services-platform:modules/workflow-actions/tests/integration/services/automation/publish-automation-rule.integration.spec.js#refuses a publisher without the permission an action’s type requires |
End-to-end policy: none: Service acceptance covers automation configuration because no automation screen exists in scope. A connected host event run requires separate evidence.