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 Future consideration
Workspace App Connect
Created by Guest
Created on Jan 2, 2014

XMLNSC parser will set unset nillable elements with the xsi:nil attribute

If a message model defines an element as nillable, and a flow does not set that element to a non-empty and non-null value, then the XMLNSC parser should be able to, upon serialization and without code or map explicitly doing so, set that element with the xsi:nil attribute. Maybe the the user could toggle this behavior off/on, through a configurable service or by some other means.

Idea priority Medium
RFE ID 43276
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Admin
    Ben Thompson
    Oct 25, 2021

    Idea / RFE Review. Apologies for the length of time this idea has been held in the status of Uncommitted Candidate / Future Consideration status. The position on this request has not changed and it is noted that currently a user (flow developer) needs to explicitly set values to be NULL in the logical tree in order to cause the serialization process at the end of a flow to write out xsi:nil attributes for the XML elements. Whilst this can be done using a relatively short loop in a Compute or JCN, we acknowledge this is inconvenient and difficult in particular for new/inexperienced users, so we are keen to keep this enhancement request open and will continue to monitor. Status is maintained as Future Consideration.

  • Guest
    Jul 4, 2016

    Apologies for the delay in responding to this RFE. We agree this would make an excellent enhancement to the product. If implemented the behaviour would need to be specifically requested to avoid impacting existing behaviours, but there are means by which this could be done without impacting existing users. Status of the RFE is updated to Uncommitted Candidate.

  • Guest
    Oct 7, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Connectivity and Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB