IBM Sterling Ideas

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:

Post your ideas

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Handling XML data Using WTX map

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.
  • Guest
  • Jan 9 2018
  • Not under consideration
DeveloperWorks ID DW_ID87686
Link to original RFE
  • Guest commented
    8 Oct, 2019 05:36pm

    Native XSD/schema negate need for this

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.