|
Comment |
Description: Transactional event used to drive reevaluation, recommendations, scheduling, and notification workers. Usage: This transactional and auditable record is used in the 08 Notifications and Operations subject area as the authoritative representation of outbox event data. This is intentionally polymorphic through Aggregate Type and Aggregate Reference and therefore has no direct Child relationship. |
|
Name |
Comment |
|
Outbox Event ID |
Description: Stable system identifier for a Outbox Event record. Usage: Used as the conceptual primary identifier and as the stable reference from relationships to Outbox Event. Required for every record. |
|
Aggregate Type |
Description: Discriminator identifying the domain aggregate represented by the outbox event. Usage: Used to select business rules, validate compatible relationships, group records, filter queries, and drive user-interface behavior. Required for every record. |
|
Aggregate Reference |
Description: Identifier of the domain aggregate represented by the outbox event. Usage: Used for provenance, external integration, traceability, and reviewer verification. Required for every record. |
|
Event Type |
Description: Controlled classification value for event type. Usage: Used to select business rules, validate compatible relationships, group records, filter queries, and drive user-interface behavior. Required for every record. |
|
Payload JSON2 |
Description: Flexible structured payload used by workers or delivery channels without changing the core schema. Usage: Used for extensible PoC data and asynchronous processing while stable, frequently queried concepts remain modeled as first-class attributes and relationships. Optional and recorded only when known or applicable. |
|
Created At5 |
Description: Timestamp recording when the created event occurred. Usage: Used for scheduling, recency rules, effective dating, audit history, and chronological reporting. Required for every record. |
|
Processed At |
Description: Timestamp recording when the processed event occurred. Usage: Used for scheduling, recency rules, effective dating, audit history, and chronological reporting. Optional and recorded only when known or applicable. |
|
Retry Count |
Description: Numeric measurement for retry count. Usage: Used by services, rules, search, reporting, or audit processing that operates on Outbox Event records. Optional and recorded only when known or applicable. |
|
Status20 |
Description: Lifecycle or workflow status of the Outbox Event record. Usage: Used to gate workflow transitions, exclude inactive or incomplete records, support operations dashboards, and preserve processing history. Required for every record. |
|
|
|