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
ITX has option to validation the input file against schema by using the Schema-validation Option on the input card. Same can be disabled by choosing Well-formed. This option is not available for output file that is generated by the map.
It would be really helpful for all the client maps that use industry standards, to be able to validation if the output file generated was with values in all the mandatory fields and satisfy the conditions. This feature is not present at the moment.
It would be really good as a product, if the tool throws a warning or error when no value is mapped to a mandatory field or when it is run, the input does not hold a value that is mapped to a mandatory output field.
What is your industry?
How will this idea be used?
A Retail customer which uses say for example GS1 standard does translation from Json/xml to GS1 xml standard. There are many systems where there are limitations to add an additional validation map or external validation process. It will be much simpler if the map on itself is able to fail when the output generated is not valid per the schema that is invoked. This will help avoid invalid files from being sent to end customer or further processing and fail right in the middle-ware application.
Do not place IBM confidential, company confidential, or personal information into any field.