Reuse workflow recipes and working-time configuration

Purpose

Administrators reuse action and workflow recipes and define the working time used for schedules.

How It Works

An administrator chooses a shipped recipe or saves a reusable workspace recipe. The action registry checks whether its contents can be configured in the intended host. Copying a recipe lets a definition keep its own frozen configuration. Staff also describe the working calendar that gives business-duration schedules meaning. Provisioning supplies an initial calendar rather than assumes every customer must retain it. Calendar replacement protects concurrent edits and changes the default atomically when requested. Existing timers keep the dates already calculated for them. There is no connected console for this configuration yet. The product should expose recipe reuse and working-time setup as distinct choices within the workflow configuration experience.

Relationships

Requires keep the action builder aligned with deployed applications to supply the prerequisite configuration or operation.
Connects with publish event-driven automation and follow its work through shared integration records.

Show evidence (sources, provenance, origins, pinned commits)

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes: Saved recipes contain actions that pass configuration validation.Provisioning supplies an initial working calendar for each workspace.
Surfaces: api
Intent sources: services-platform:docs/proposals/application-processes-and-workflow-actions/14-decisions.md#D-03services-platform:docs/proposals/application-processes-and-workflow-actions/14-decisions.md#D-08

Controls

29 controls apply, from the corpus control catalogue.

TC-AVL-004 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-CHG-001 TC-CHG-002 TC-CHG-003 TC-CHG-004 TC-CHG-005 TC-CHG-006 TC-DAT-001 TC-DAT-003 TC-DAT-004 TC-IAM-001 TC-IAM-006 TC-LOG-004 TC-LOG-005 TC-PI-001 TC-PI-002 TC-PI-003 TC-PI-004 TC-PI-005 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-VEN-001 TC-VEN-002 TC-VEN-003

Permissions

Key	Checked at	Scope
`platform.workflow-actions.registry-read`	api	tenant
`platform.workflow-actions.templates-manage`	api	tenant
`platform.workflow-actions.calendars-manage`	api	tenant

Business Rules

10 rules, 10 to be proved before approval. A rule's product intent is derived from its origin: 4 confirmed by a product decision, the rest inheriting this capability's proposed.

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Proposed	Lists place Rhythm’s eight shipped action recipes and six workflow recipes first, identify them as shipped and refuse customer edits or deletion. proved by `ATS-PFM-INT-019-01`, `TST-PFM-INT-587`, `TST-PFM-INT-591`, `TST-PFM-INT-604`	policy	api, service	test services-platform:modules/workflow-actions/tests/integration/services/persistence/action-templates.integration.spec.js#refuses a replacement of one (405)
`02`must prove Proposed	Recipe saves validate every action against active enabled registry types, host and trigger restrictions, current contract version, settings schema and configurator permissions, with workflow stages also checked against their contract. proved by `ATS-PFM-INT-018-07`, `ATS-PFM-INT-019-02`, `TST-PFM-INT-591`, `TST-PFM-INT-600`, `TST-PFM-INT-605`	validation	service	test services-platform:modules/workflow-actions/tests/integration/services/persistence/action-templates.integration.spec.js#refuses a type that is declared and switched off
`03`must prove Proposed	Customer recipe identifiers are unique within the workspace, cannot use Rhythm’s reserved prefix and require the read version on replacement. proved by `ATS-PFM-INT-019-03`, `TST-PFM-INT-591`	validation	service	test services-platform:modules/workflow-actions/tests/integration/services/persistence/action-templates.integration.spec.js#refuses an id in Rhythm’s own prefix, which the configuration-id grammar reserves (400)
`04`must prove Proposed	A recipe is copied into its using definition, so later template edits do not change that definition. proved by `ATS-PFM-INT-019-09`, `ATS-PFM-INT-020-10`	policy	service	documented services-platform:docs/workflow-actions/README.md#Workflow actions: Platform's part of the Workflow Action Engine
`05`must prove Confirmed	Calendars require a valid IANA zone, distinct working weekdays, optional forward working hours and at most four hundred holidays; one default at most must be active and a new default atomically clears the previous one. origin: services-platform:docs/proposals/application-processes-and-workflow-actions/14-decisions.md#D-08 proved by `ATS-PFM-INT-019-04`, `TST-PFM-INT-588`, `TST-PFM-INT-596`	validation	service, database	test services-platform:modules/workflow-actions/tests/integration/services/persistence/business-calendars.integration.spec.js#refuses more than 400 holidays
`06`must prove Confirmed	Provisioning gives a workspace a Monday-to-Friday, nine-to-five Standard week in its own zone with no holidays, uses the seed ledger once and does not recreate a user-deleted seed. origin: services-platform:docs/proposals/application-processes-and-workflow-actions/14-decisions.md#D-08 proved by `ATS-PFM-INT-019-05`, `TST-PFM-INT-590`	lifecycle	service	test services-platform:modules/workflow-actions/tests/integration/services/maintenance/tenant-participant.integration.spec.js#gives the tenant Standard week in its own zone, as its default
`07`must prove Confirmed	Business-duration arithmetic uses the calendar’s zone, working days, hours and holidays, so two business days after Friday at four in the afternoon with Monday closed reaches Wednesday at the same time. origin: services-platform:docs/proposals/application-processes-and-workflow-actions/14-decisions.md#D-08 proved by `ATS-PFM-INT-019-06`, `TST-PFM-INT-002`	calculation	service	test macroservice-libraries:packages/workflow-actions/src/business-days.spec.ts#P2D business from a Friday 16:00 with a Monday holiday lands on Wednesday 16:00, across the DST change (08 §10 case 8)
`08`must prove Confirmed	Calendar changes leave previously calculated timer dates unchanged. origin: services-platform:docs/proposals/application-processes-and-workflow-actions/14-decisions.md#D-08 no proof recorded yet	policy	service	documented services-platform:docs/workflow-actions/README.md#How a host reads a calendar
`09`must prove Proposed	Registry read permits recipe and calendar reads, templates manage permits recipe changes and calendars manage permits calendar changes. proved by `ATS-PFM-INT-019-07`, `TST-PFM-INT-587`	permission	api	test services-platform:modules/workflow-actions/tests/e2e/workflow-actions.e2e.spec.js#refuses a caller without templates-manage a write (403)
`10`must prove Proposed	A workspace holds no more than one hundred calendars; stale replacements and applicable locked mutations refuse without changes, while deletion of the sole unlocked default can leave no default. proved by `ATS-PFM-INT-019-08`	validation	service	observed services-platform:modules/workflow-actions/services/persistence/business-calendars.ts:createBusinessCalendar

Scenarios

Id	Given	When	Then	Provenance
`01`	The working calendar closes weekends and a Monday holiday.	A reminder adds two business days to Friday at four in the afternoon.	The reminder falls on Wednesday at four in the afternoon.	test macroservice-libraries:packages/workflow-actions/src/business-days.spec.ts#P2D business from a Friday 16:00 with a Monday holiday lands on Wednesday 16:00, across the DST change (08 §10 case 8)

Planning

Implementation

Reuse workflow recipes and working-time configuration ​

Purpose ​

How It Works ​

Relationships ​