dohertj2/scadalink-design
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

docs(notification-outbox): fix stale cross-references after outbox addition

Browse Source
This commit is contained in:
Joseph Doherty
2026-05-18 23:45:43 -04:00
parent ba166bf503
commit bb35453d58
9 changed files with 41 additions and 52 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/requirements/Component-CentralUI.md
View File

@@ -98,7 +98,7 @@ Central cluster only. Sites have no user interface.
- Track deployment status (pending, in-progress, success, failed).
### System-Wide Artifact Deployment (Deployment Role)
- Explicitly deploy shared scripts, external system definitions, database connection definitions, data connection definitions, notification lists, and SMTP configuration to all sites or to an individual site.
- Explicitly deploy shared scripts, external system definitions, database connection definitions, and data connection definitions to all sites or to an individual site. (Notification lists and SMTP configuration are central-only and are not deployed.)
- **Per-site deployment**: A "Deploy Artifacts" button on the Sites admin page allows deploying all artifacts to an individual site.
- **Deploy all**: A bulk action deploys artifacts to all sites at once.
- This is a **separate action** from instance deployment — system-wide artifacts are not automatically pushed when definitions change.
@@ -115,7 +115,7 @@ Central cluster only. Sites have no user interface.
- Subscribe-on-demand — stream starts when opened, stops when closed.
### Parked Message Management (Deployment Role)
- Query sites for parked messages (external system calls, notifications, cached DB writes).
- Query sites for parked messages (external system calls, cached DB writes). (Parked notifications are managed centrally on the Notification Outbox page, not here.)
- View message details (target, payload, retry count, timestamps).
- Retry or discard individual parked messages.