18/11/2024 - 1.0.8
- Option to combine receiver and interface determination in one single XSLT mapping for an improved runtime behavior
- Option to bypass interface determination pipeline step in case of Recipient List pattern without interface split
- Option to bypass receiver determination pipeline step in case of interface split scenarios with one single receiver only
- Supporting header-based XSLT routing conditions if message body is non-XML
- Extension for custom receiver determination instead of XSLT from Partner Directory
- Extension for custom interface determination instead of XSLT from Partner Directory
- New pipeline processing log providing more details if message is stored to the dead letter queue
- Fixed standard retry handling for generic integration flows with splitter to avoid message duplicates

08/10/2024 - 1.0.7
- Add custom header properties to improve message monitoring
- Allow headers starting with dc for passing dynamic configuration parameters to the generic integration flows, e.g., to support header-based routing conditions

08/08/2024 - 1.0.6
- Revised partner id approach due to lengths restrictions of the partner id
- Option to use alternative partner in case of sender wildcard scenarios and to overcome partner id restrictions
- Changed default max retry to 5 instead of unlimited retry
- For messages in test mode, failed messages are not put into retry
- For generic integration flows, adapter parameters were externalized
- Option to configure message end event type in case of message stored in dead letter queue, default is Escalated
- Option to bypass receiver determination and interface determination steps in case of Point-to-Point pattern
- Option to configure a pipeline JMS queue prefix which makes configuration of queue names easier if you create another set of generic integration flows

31/05/2024 - 1.0.5
- Extension for custom error handling
- In generic IDoc inbound processing flow, display list of IDoc numbers in case of IDoc bulk messages
- For IDoc inbound, sender interface is calculated as a combination of MESTYP, IDOCTYP and CIMTYP
- Supporting test mode via testMode header in the allowed headers configuration
- In standard error handling, copied messages from the dead letter queue are switched to DEBUG log level

22/04/2024 - 1.0.4
- Removed the deletion of the payload exchange property to avoid that an empty payload is written into the dead letter queue
- Generic inbound processing for IDoc flow now assigns the IDoc number to the SAP_ApplicationID header for better monitoring
- Generic inbound processing for XI flow now assigns the XI ID to the SAP_ApplicationID header for better monitoring
- For both generic inbound processing for IDoc and generic inbound processing for XI the custom status is set to DuplicateDiscarded in case of duplicate messages

12/04/2024 - 1.0.3
- Changed the dead letter queue names to ensure that the queues are automatically created when deploying the integration flows
- Stored the payload in an exchange property for the generic outbound processing flow to ensure that in case of an error the payload before mapping is stored in the dead letter queue

08/04/2024 - 1.0.2
- Switched on transaction handling for flows reading and writing into JMS queues

19/03/2024 - 1.0.1
- Changed names of the integration flows for better readability

18/03/2024 - 1.0.0
- First shipment