Zinnia Event Catalog
A governed event publishing framework for standardized, versioned, and contract-scoped event access.
A governed event publishing framework for standardized, versioned, and contract-scoped event access.
The Event Catalog is a centralized and governed source of truth for all externally published events. It helps business, partner, product, and engineering teams understand which events are available, what data they include, and which plans, tiers, or personas are eligible to consume them.
By making event availability, eligibility, and authorization rules visible and consistently enforceable, the Event Catalog reduces ambiguity and creates a trusted, scalable foundation for external event consumption.
7 current events · 15 upcoming events
New business application case has been successfully processed.
New Business · LIFE/ANNUITY
An exception occurred during new business application processing.
New Business · LIFE/ANNUITY
New business life policy issuance has been completed.
source: BPM.NBLife · LIFE
Policy update transaction has been completed successfully.
12 completion subtypes · LIFE/ANNUITY
An exception occurred during policy update processing.
11 exception subtypes · LIFE/ANNUITY
Generic, versioned transaction lifecycle events — applicable across all transaction types
Triggered when a transaction request is received from an upstream channel, partner, distributor, customer, or internal source.
Upcoming · Lifecycle
Triggered when a received request is accepted and transaction processing is initiated.
Upcoming · Lifecycle
Triggered when business rule validation for the transaction is completed.
Upcoming · Lifecycle
Triggered when the transaction is successfully submitted to the system of record.
Upcoming · Lifecycle
Triggered when the transaction is successfully processed by the system of record.
Upcoming · Lifecycle
Exception, document, case, and task events may also fire depending on the transaction journey.
Triggered when a transaction request is received from an upstream channel, partner, distributor, customer, or internal source.
Upcoming · Lifecycle
Triggered when a received request is accepted and transaction processing is initiated.
Upcoming · Lifecycle
Triggered when business rule validation for the transaction is completed.
Upcoming · Lifecycle
Triggered when the transaction is successfully submitted to the system of record.
Upcoming · Lifecycle
Triggered when the transaction is successfully processed by the system of record.
Upcoming · Lifecycle
Exception, document, case, and task events may also fire depending on the transaction journey.
Triggered when a transaction request is received from an upstream channel, partner, distributor, customer, or internal source.
Upcoming · Lifecycle
Triggered when a received request is accepted and transaction processing is initiated.
Upcoming · Lifecycle
Triggered when business rule validation for the transaction is completed.
Upcoming · Lifecycle
Triggered when the transaction is successfully submitted to the system of record.
Upcoming · Lifecycle
Triggered when the transaction is successfully processed by the system of record.
Upcoming · Lifecycle
Exception, document, case, and task events may also fire depending on the transaction journey.
Triggered when a transaction request is received from an upstream channel, partner, distributor, customer, or internal source.
Upcoming · Lifecycle
Triggered when a received request is accepted and transaction processing is initiated.
Upcoming · Lifecycle
Triggered when business rule validation for the transaction is completed.
Upcoming · Lifecycle
Triggered when the transaction is successfully submitted to the system of record.
Upcoming · Lifecycle
Triggered when the transaction is successfully processed by the system of record.
Upcoming · Lifecycle
Exception, document, case, and task events may also fire depending on the transaction journey.