Escalate overdue attention and plan reminders

Purpose

Persistent overdue conditions may need a wider audience or a reminder. Escalation and reminder planning provide that follow-up.

How It Works

A kind declares any escalation target and delay. Workspace settings can override only the permitted parts. The sweep adds the target audience after the delay while preserving existing recipients. Escalation remains with the occurrence after later refreshes. Reminder planning resolves recipients and their personal visibility state. The sender rechecks pending work before delivery. Current delivery collects a person’s items into a communications message. The product should instead use Notifications for delivery and its timing preferences. The product should also keep reminders off until an administrator enables them.

Relationships

Maintain attention conditions throughout their lifecycle supplies the condition’s lifecycle and follow-up declarations.
Deliver relevant attention with a reason resolves the current audience for follow-up.

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: Escalation adds a recipient once while retaining the original audience.Reminder planning addresses due, overdue and escalated work.
Surfaces: job
Intent sources: services-platform:docs/milestones/plans/PLAT-M16-plan.md#2. Scopeservices-platform:docs/milestones/plans/PLAT-M16-plan.md#D2services-platform:docs/milestones/plans/PLAT-M16-plan.md#D3services-platform:docs/milestones/PLAT-M16-attention-follow-up-and-tuning.md#Decisionsservices-platform:docs/proposals/responsibilities-and-attention/16-decisions.md#D-07services-platform:docs/proposals/responsibilities-and-attention/16-decisions.md#D-10

Controls

24 controls apply, from the corpus control catalogue.

TC-AVL-004 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-LOG-002 TC-LOG-003 TC-LOG-005 TC-MON-001 TC-PI-002 TC-PI-004 TC-PI-005 TC-PRV-001 TC-PRV-002 TC-PRV-004 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-VEN-001 TC-VEN-002 TC-VEN-003

Permissions

Key	Checked at	Scope
`platform.attention.use`	service	tenant

Business Rules

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

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Confirmed	A 15-minute sweep escalates an overdue occurrence once after its configured delay, adds the declared role or responsibility audience and audits the change while retaining original audiences. origin: services-platform:docs/proposals/responsibilities-and-attention/16-decisions.md#D-07 proved by `ATS-PFM-ELG-019-01`, `TST-PFM-ELG-402`	lifecycle	service	test services-platform:modules/attention/tests/integration/services/sweep/sweep-tenant.integration.spec.js#escalates an item overdue past its escalation: stamped, and its role added as an escalation audience
`02`must prove Confirmed	Escalation is permanent, is not repeated and survives provider refreshes, with occurrences short of the delay unchanged. proved by `ATS-PFM-ELG-016-15`, `ATS-PFM-ELG-019-02`, `ATS-PFM-ELG-019-07`, `TST-PFM-ELG-402`	invariant	service	test services-platform:modules/attention/tests/integration/services/sweep/sweep-tenant.integration.spec.js#escalates an item once: a second sweep stamps, adds and records nothing
`03`must prove Confirmed	Reminder policies combine application defaults and workspace overrides field by field, defaulting to due-soon and overdue reminders, daily up to three and escalation where supported; disabled or empty policies plan nothing. proved by `ATS-PFM-ELG-019-03`, `TST-PFM-ELG-405`	calculation	service	test services-platform:modules/attention/tests/unit/reminders.spec.js#takes the tenant’s override part by part over the declaration
`04`must prove Confirmed	Reminders are planned per matching person: once near due date, by overdue cadence up to a maximum without late catch-up and once for escalation recipients, skipping snoozed, dismissed or hidden attention and preventing duplicate plans. proved by `ATS-PFM-ELG-019-04`, `TST-PFM-ELG-401`, `TST-PFM-ELG-405`	calculation	service	test services-platform:modules/attention/tests/integration/services/reminders/reminders.integration.spec.js#plans nothing for a person who snoozed the item
`05`must prove Confirmed	Sending rechecks due reminders and records skips for closed, dismissed, snoozed or hidden attention, disabled policies and inactive or unaddressable recipients. proved by `ATS-PFM-ELG-018-08`, `ATS-PFM-ELG-019-05`, `ATS-PFM-ELG-019-08`, `ATS-PFM-ELG-019-09`, `ATS-PFM-ELG-020-10`, `TST-PFM-ELG-401`	policy	service	test services-platform:modules/attention/tests/integration/services/reminders/reminders.integration.spec.js#skips a due reminder whose item was resolved before it went
`06`must prove Confirmed	Each sender run groups a person’s reminders into one communications message with kind, reason, workspace-zone due date and console link, using an idempotency key for retries. origin: services-platform:docs/proposals/responsibilities-and-attention/16-decisions.md#D-10 proved by `ATS-PFM-ELG-019-06`, `ATS-PFM-ELG-019-10`, `TST-PFM-ELG-401`	policy	service	test services-platform:modules/attention/tests/integration/services/reminders/reminders.integration.spec.js#sends one message per person, the admin’s listing both of their items
`07`must prove Confirmed	The product should leave reminders disabled until a workspace administrator enables the kind. origin: services-platform:docs/milestones/plans/PLAT-M16-plan.md#D2 no proof recorded yet	policy	service	unknown FND-PFM-ELG-019
`08` Confirmed	The product should send reminders through Notifications and use its digest and quiet-hour preferences; current attention code still sends communications e-mail and retains those preferences. origin: services-platform:docs/milestones/plans/PLAT-M16-plan.md#Approval	policy	service	unknown FND-PFM-ELG-017

Scenarios

Id	Given	When	Then	Provenance
`01`	Batch posting escalates to financial close after a day overdue.	A batch passes that delay.	The next quarter-hour sweep adds the financial-close holder’s view with an escalation reason and retains the posting holder’s view.	documented services-platform:docs/milestones/plans/PLAT-M16-plan.md#3. How it works for the user

Planning

Implementation

Escalate overdue attention and plan reminders ​

Purpose ​

How It Works ​

Relationships ​