Skip to Main Content

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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace App Connect
Created by Guest
Created on May 15, 2018

SOAP Envelope Enhancement Request

Change the SOAP Envelope node to support both SOAP 1.1 and 1.2.  Specifically, we would like the SOAP Extract node to store the entire SOAP Envelope (independent of SOAP version), which includes the Soap Envelope tag, SOAP Body tag, SOAP Header tag and all of the SOAP Header Tag's children, in the “Envelope Destination” configured on the SOAP Extract node.  Then, the SOAP Envelope node, later in the flow, could retrieve the entire saved SOAP Envelope (independent of SOAP version), which includes the Soap Envelope tag, SOAP Body tag, SOAP Header tag and all of the SOAP Header Tag's children, from the “Existing Envelope Location” configured on the SOAP Envelope node.

Currently, the SOAP Envelope node has the ability to add a new SOAP Envelope. 

Add a user selectable property that would identity a SOAP version, either SOAP 1.1 or 1.2, to use when creating a new SOAP Envelope.

Idea priority Medium
RFE ID 120077
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Admin
    Ben Thompson
    Mar 11, 2023

    Idea Review. As part of our policy for regularly reassessing aged ideas we have recently discussed this enhancement request again. Unfortunately on this occasion it has been decided that we won't be taking this idea further forward as a business priority. Despite being open for several years now, this particular request has only garnered a single vote, and there are already other means of achieving this use case in the product. It's possible to construct a SOAP structure prior to a SOAPRequest node using a graphical mapping node or using code in a Compute/JavaCompute/.NETCompute node ... so whilst the suggestion would provide usability benefits there are other options available.

  • Guest
    Oct 9, 2020

    RFE Review. Thank you for raising this RFE and apologies for the time period it has been in Submitted Status. We agree that this usability enhancement would assist users with SOAP 1.2 processing. We're surprised this RFE has not received more public support in the time that it has been open, but will continue to monitor it for popularity. Status is updated to Uncommitted Candidate.