I'm facing a challenge while trying to append an MD5 hash value to payment order files after performing an initial format transformation (for SEPADD format) in IFS Cloud 23.2 My current setup has two routing addresses connected to a single routing rule:

- Core Transformer(XSL Transformer) Connected Routing Address: Handles the SEPADD file transformation.

- MD5 Transformer(Java Transformer) Connected Routing Address: Appends the MD5 hash to the file content.

The problem is that the MD5 transformer only receives the receipt response/Message response from the core transformer, rather than the fully transformed file content.



According to the documentation, some address types only pass the receipt instead of the transformed output.

Does anyone have experience handling this kind of transformation sequence? Is there an alternative routing strategy or configuration that ensures the MD5 transformer receives the fully transformed file content?




