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.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
This feature was delivered as part of ACEv12.0.6.0 (for more information please see the section "Removal of restrictions when visually debugging flows deployed as .cmf" in blog entry https://community.ibm.com/community/user/integration/blogs/ben-thompson1/2022/09/26/ace-12-0-6-0). Status of the idea is updated to Delivered.
Idea / RFE Review. Thank you for taking the time to raise this suggestion. In general we would like to encourage users to move away from compiled message flow formats in the BAR file. Source artifact deployments are more flexible in the event you wish to recover build time artifacts from runtime systems, and it can also save on processing required to compile the artifact into the BAR and then interpret the compiled artifact at deployment time. That said, we appreciate that a minority of our users who have chosen not to move away from .cmf and are currently moving up to v12 are hitting this published limitation of the product for the first time. We would like to help, and we are updating the status of this enhancement request to "In development".