Downstream Message Push
OIPA can send messages to systems (downstream systems) expecting OIPA data as input after an activity completes processing. Messages can be defined in PushNotifications business rule as per customers requirement. Push notifications business rules has configuration to define actions that need to be taken in case of message push failure or activity processing failure. Currently SOAP and JMS protocols are supported for communication with downstream systems. With this enhancement downstream message push adds REST protocol for communication. Message defined in XML format can be sent either in XML or JSON formats using REST protocol based on customer's choice.
Details required for message delivery like downstream endpoint details and security details are saved to DownstreamMessagePushDefinition business rule for JMS and SOAP protocols. With this enhancement these details will be captured to new database tables AsOutboundApplications and AsOutboundSecurity for all the protocols (JMS,SOAP and REST). Maintaining (Posting, updating and deleting) downstream application and security details can be done through REST APIs.
Required Manual Updates
With this enhancement DownstreamMessagePushDefinition business rule is deprecated and should be removed manually. All details from the business rule that are required for connection and security should be moved to database tables manually using REST APIs provided.