IBM Sterling Ideas
formerly Watson Supply Chain
Submit new product ideas for IBM Sterling solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed. Order Management, Store Engagement, Watson Order Optimizer, Inventory Visibility, CPQ and Call Center are now part of Watson Supply Chain
Connect with IBM experts and your peers on the
Supply Chain Collaboration Community and the Order Management Interest Group
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.
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.
|What is your industry?||Other|
|What is the idea priority?||Urgent|
|Link to original RFE|