Downstream Message Push Overview
Downstream message push (DMP) feature adds the ability to push appropriate notifications to the downstream on completion of an activity processing, before data is committed to the database. A user can configure this feature in Palette without any need for external files using the PushNotifications ABR and DownstreamMessagePushDefinition system rule. The DownstreamMessagePushDefinition allows to define a message structure and the PushNotifications rule can be configured to deliver messages to the downstream applications through the JMS/SOAP protocols. This functionality can be enabled by the configuration provided in these business rules.
OIPA supports DMP, when activities are run manually, through DI, Webservices and Cycle.
Important: Cycle properties file should contain the property downstream.service.event.mode enabled in order to support DMP for activities that run through Cycle.
A user can override DownstreamMessagePushDefinition rule at Primary company level and Plan level; PushNotifications ABR can be overridden at Plan Activity, Policy Activity, Client Activity, Company Activity and Customer Activity and is applicable for all activity types.
Unsupported Transactions for DMP
PushNotifications for DMP is not supported for the following transactions:
- PolicyExtract
- Client Extract
- Client import
- Client Batch
- Client-GCQuote
- Client-ScreenUpdate
- Cycle-Document
- Cycle-Extract
- Cycle-Import
- Intake-File
- Intake-Record
- Plan-Batch
- Plan-Document
- Plan-Document-Nonreversible-Nonreversing
- Plan-ExtractPlan-Financial
- Plan-Financial-Nonreversible-Nonreversing
- Plan-Import
- plan level transactions with type codes 09, 11,12 (Plan extract, Plan import, Plan batch)
TypeCodes not supported in OIPA Application
- Client Extract
- Client import
- Client Batch
TypeCodes not reflected in OIPA Application
- Client-GCQuote
- Client-Screenupdate
- Cycle-import
- Cycle-Document
- Cycle-Extract
- Intake-File
- Intake-Record
TypeCodes not available in Rules Palette Transaction Types
- Client Document Reversible Non Reversing
- Client Illustration
Message Templates
Downstream message templates can be constructed using custom configuration for push notifications. PushNotifications ABR can be configured to define an action that needs to be taken in case when a message push fails or an activity processing fails.
Codes for Downstream Message Push (AsCode)
Downstream Message Push feature uses a system code AsCodeOutboundSourceType to map the SourceType with the AcOutboundEvent table of Admin Console.
- Code Name: AsCodeOutboundSourceType
- Code Value: ACT
- Short Description: Activity
- Long Description: Source type Activity
DB table AcOutboundEvent
A database table AcOutboundEvent in Admin Console is used to capture the logs for all the events, messages generated, and response received into the table. Every step of the Downstream message life cycle sends a push notification to the database table.
Important: The Admin Console must be up and running, to track these outgoing messages.
