This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
firstname.lastname@example.org - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Idea Review. As part of our policy for regularly reassessing aged ideas we have recently discussed this enhancement request again. With just a single vote since this idea's creation in 2017, unfortunately on this occasion it has been decided that we won't be taking this idea further forward as a business priority. As mentioned in the last review comment, the basic building blocks for the design being requested are already present in the ACH pattern, so creating a time-based replay and sequencing behaviour in the transformation flow would be possible (admittedly with more effort on the part of the user).
RFE Review. Thank you for taking the time to raise this RFE and apologies for the length of time it has been in Submitted status. In general although it is possible to achieve this use case already with the product capabilities for pubishing monitoring events to MQ, and the IIB/ACE Record & Replay feature, we appreciate that you would like some of these behaviours baked in to the pattern solution. In particular the HL7 to HL7 DFDL pattern utilises MQ queues for separating the inbound (Receiver) and outbound (Sender) flows usage of TCP sockets for the support of MLLP, from the use of MQ as a helpful persistent asynchronous transport.. so the basic building blocks are in place such that the middle transformation flow could be instrumented to utilise record and replay. Status of the RFE is updated to Uncommitted Candidate.