updatedAt as a labelled proxy because the dataset has no formal approvalRequestedAt. Any RAG transition is hypothetical until a previous approved snapshot is connected.Notification queue
Click an alert to review message text, underlying evidence, and escalation rationale.
| Notification / evidence | Owner / recipients | Priority | Escalation | Simulation state |
|---|
Selected message preview
Recipient, subject, action and source record
Recent simulation events
Generated on this browser only
Governance boundaries
Eight notification automation rules
Business rules and escalations are configurable proposals for assessment, not policy already approved.
| Rule | Trigger | Recipients / channel | Action / escalation |
|---|
Simulation audit log
Immutable in production. This local example log can be reset.
Data exchange and deployment controls
Reusable with the Deliverable 2 dashboard JSON export and Deliverable 3 agent.
Production workflow design
Power Automate scheduled cloud flow (weekday 08:00 Asia/Dubai) and SharePoint/Dataverse item-change events → read governed lists with least-privilege service identity → validate required dates, status and ownership → evaluate rules → write a notification outbox item with an idempotency key → send via approved Teams/email connector → record delivery attempt and retry status → escalate through a separate timer-driven flow → close/suppress only when source state or approved exception warrants it.
Safety and implementation boundaries
The demo runs entirely client-side; no real connector, recipients' emails, push notifications, scheduling service, authentication or server-side audit store. Import only fictional or non-sensitive data. Production must support RBAC, error and dead-letter queues, exception monitoring, local holidays, quiet hours, retention policy and change-controlled escalation thresholds.