Integration


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 updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

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.


Add a new idea Subscribe
Status Submitted
Workspace webMethods Hybrid Integration
Created by Guest
Created on May 7, 2026

RELATED IDEAS

Fields/doc defined in Flowservice Output to be available throughout the entire pipeline of flowservice

In webMethods Flowservices, when you define Input and Output Fields, the default behavior is that the Output fields only show up at the very last step of your flowservice

To add further, when you use a Try-Catch block, the output field now shows only at the last step in your Catch block (and is not available in the last step of the Try block where your mapping logic is)

Since this behavior existed even self-managed, the norm for legacy webMethods developers was to to re-add the field/document in the mapping step's pipeline (or some temporary variables), implement mapping logic and then perform one additional map at the end of flowservice to map those values from temp variables to the specified fields/doc of the flowservice.

For new developers to IWHI, this is not intuitive as they are wondering why the output fields which they specified in Flow Service "define I/O" section dont show up in any of their flowservice intermediate steps (except at the very end).

Ideal behavior -
The fields/document defined in the flow service's Output should be available in the mapping pipeline throughout the entire flow and not just at the very last step of the flow service

IWHI - Flow ser...
IWHI - Flow service - Defined Output.png
Open full size
Idea priority Medium

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.