Skip to Main Content
IBM Sterling

This portal is to open public enhancement requests for IBM Sterling products and services. 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 Delivered
Categories Design Studio
Created by Guest
Created on Feb 12, 2019

Document verification: Support for Ignoring undefined attribute

With ITX 9 FP3(when using native schemas), we have the option to Ignore Undefined XML elements that comes in an input file from the customer that are not defined in the XSD. This way we don't need to update the maps and its reference when the input structure changes.

However this rule does not apply to XSD attributes. We would need similar functionality or enhance the existing functionality to ignore both the XML elements and its attributes.

What is your industry? Other
How will this idea be used?

The existing ITX functionality  :  'Ignore undefined constructs' limits/restricts the usability to only XML elements.

By ignoring both the XML elements and attributes, the existing functionality can be fully utilized



1) Customer can make changes to their XSD/structure  without having to inform its consumers

2) This would support true CDM type of implementations where in changes to main XSD need not be applied everywhere.

  • Guest
    Feb 11, 2020

    Delivered in v10.0.2