---
id: JNY-PFM-INT-006
title: Publish an automation for a registered business event
feature: FEAT-PFM-INT-06
product_area: platform
module: integrations
revision: 1
status: draft
product_intent: confirmed
implementation_evidence: partially-observed
supersedes: []
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
actor: ACT-PFM-022
goal: Configure a task and an email reaction to an overdue-invoice event and inspect the shared run list.
capabilities:
  - CAP-PFM-INT-018
  - CAP-PFM-INT-020
screens: []
steps:
  - 'n': 1
    surface: listWorkflowTriggerPoints
    action: List the host’s available timers and its registered event trigger.
    capability: CAP-PFM-INT-018
    expected: 'The listing includes host timers, the event trigger and its registered event.'
    provenance: test
    source: >-
      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
  - 'n': 2
    surface: listWorkflowActionTypes
    action: Inspect the action types available for this trigger.
    capability: CAP-PFM-INT-018
    expected: 'Only configurable, enabled action types appear.'
    provenance: test
    source: >-
      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
  - 'n': 3
    surface: createAutomationRule
    action: Create an automation for the event.
    capability: CAP-PFM-INT-020
    expected: A draft is associated with the application that owns the event.
    provenance: test
    source: >-
      services-platform:modules/workflow-actions/tests/e2e/workflow-actions.e2e.spec.js#creates it as a draft,
      owned by its event’s application
  - 'n': 4
    surface: saveAutomationRuleDraft
    action: Save a condition and the two actions in the draft.
    capability: CAP-PFM-INT-020
    expected: The editable draft retains the configuration.
    provenance: test
    source: >-
      services-platform:modules/workflow-actions/tests/e2e/workflow-actions.e2e.spec.js#saves the draft in
      place
  - 'n': 5
    surface: publishAutomationRule
    action: Publish the automation.
    capability: CAP-PFM-INT-020
    expected: The rule becomes enabled with a frozen first current version.
    provenance: test
    source: >-
      services-platform:modules/workflow-actions/tests/e2e/workflow-actions.e2e.spec.js#publishes it, enabled,
      with the version as its current one
  - 'n': 6
    surface: listWorkflowActionRuns
    action: Inspect the shared run list.
    capability: CAP-PFM-INT-020
    expected: Runs are visible across applications when host views supply them; without those views the list is empty.
    provenance: test
    source: >-
      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
alternates: []
failures:
  - from_step: 5
    condition: No application registers the selected event
    path: Reject publication and identify the missing registration
    outcome: Leave the draft editable
    provenance: test
    source: >-
      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)
rules_in_play:
  - BR-CAP-PFM-INT-018-05
  - BR-CAP-PFM-INT-020-01
  - BR-CAP-PFM-INT-020-03
  - BR-CAP-PFM-INT-020-04
  - BR-CAP-PFM-INT-020-07
assertions:
  - id: AS-JNY-PFM-INT-006-01
    statement: Publication requires eligible actions and the permissions their types require.
    provenance: test
    source: >-
      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
e2e_policy: none
e2e_reason: >-
  Service acceptance covers automation configuration because no automation screen exists in scope. A connected
  host event run requires separate evidence.
evidence:
  - >-
    Steps, alternates, failures and assertions cite the acceptance journeys and service tests at the commits
    in source_sha.
intent_sources:
  - 'services-platform:docs/proposals/application-processes-and-workflow-actions/14-decisions.md#D-10'
proved_by: []
---
# Publish an automation for a registered business event

## Story

A configuration administrator selects a registered overdue-invoice event, configures a condition and two actions, then publishes the draft. The shared list can expose runs supplied by the owning application. This service sequence does not prove that Accounting emits the event or executes these actions in a complete product journey; host execution remains outside the examined implementation boundary.