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 (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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
We have a WTX translation map from xml to Legacy format. The source xml type tree has been created with the XSD schema. Currently the map was working fine with the xml data because it is matching with type tree structure. However the client is saying now there might be a situation and possibility that their customers will send undefined xml xpaths (Refer Note1 below) in the xml file and the WTX map should not fail in this case. We known in general the map will fail because type tree structure miss mach with the xml file. Since the undefined xpaths are not been mapped/used further downstream to target Legacy systems and so we need to ignore them. (FYI - Refer Note 2 below). To make client happy and do not want to impact client business, we need a solution for the above mentioned. Note1 - Elements not defined in the source type tree / xsd, also which is not known the place holder in the complex xml file. Note2 - During map development, the xsd was used only to a create a input type tree because it contains huge structure definition. Here the map should not do a xsd schema validation and so we selected input card settings under document verification as well formed option. Another Option we selected direct xsd file in input card setting at type tree location and then selected document verification as well formed option.
ignore unknown xml elements when verification is well-formed only
Please add an XML parser option, that checks for well-formedness only and ignores unknown elements, so that WTX maps run successfully when the XML contains the elements that are used in the map. Unknown elements should not raise an error. Only ele...
Do not place IBM confidential, company confidential, or personal information into any field.