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).
Shape the future of IBM!
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:
Search existing ideas
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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Callable flows from designer to enterprise to set message properties, so message body can be returned
As discussed in the case number TS014404341, when using a callable flow node from an app connect designer instance, the message properties are not set in ACE, as they are when using a callable flow node from ACE to ACE.
This causes the message body to always be returned empty whenever you use this callable flow, unless you manually set these values within the ACE flow, which will of course lead to worse integration design. Especially if an ACE flow needs to be called by different callable flow nodes, one from designer needing to manually override these values, one from ACE which sets these values themselves as needed.
Because of this reason, I would like to have an update that makes the callable flows set message properties sufficiently so that designer can receive the message body that the callable flow returns from ACE.
Do not place IBM confidential, company confidential, or personal information into any field.