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.
-
Transformation Extender to provide Map Coverage in a similar way Sonar provides code coverage.
We would like to have a tool, similar to the code coverage tools that they have for traditional code, available for ITX maps.
Requirements:
This functionality must be invokable both through the graphical map design tooling and available ...
-
Support for JSON schema : natively and type tree Importer
Currently the ITX product is designed to be used with JSON data, and not the JSON schema (Native and Importer).Example : "age": { "$ref": "secondary.json#/properties/age"}With more systems adapting to JSON based message transformation and use swag...
-
ITX output validation
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 ...
-
Using Valid JSON Schema as the Type tree in the Output Layout ,Array Element/Values are getting generated without closing square brackets
In JSON Output, Array Element/Values are generated without square brackets
When we use the Valid JSON Schema as the Type tree in the Output Layout ,
ITX reading the JSON Schema successfully, but the Array Elements/Values are getting generated...
-
JSON Outputs are Getting Generated with Indentation Turned OFF
JSON Outputs are Getting Generated with Indentation Turned OFF
In ITX Map : When we Import JSON File as a Type Tree, Output Layout by default is getting generated with Indentation Turned off.
Currently below are Missing in ITX Type Tre...
-
Add a feature to load codelist to IBM Transformation Extender (ITX) Design studio for local testing
We are using codelists for 90 percent of clients and currently, we do not have an option to load the codelists to the ITX design studio for local testing as we do for the SI mapping server. We are depending on CTE/Production testing to validate ma...
-
Enabling support for FF0D in ITX for ibm-930 code page
When we receive FF0D character in request to Datapower service, ITX map is unable to handle in ibm-930 code page. Can you please enhance ibm-930 code page to handle FF0D character in ITX maps.
-
Display Starting position of the field in field level properties for "FIXED, IMPLICIT" group/file.
In ITX, when the group is defined as fixed and implicit, to identify a field position most of the time we must sum up the field length of previous fields when there is no layout. This would simplify the identification of field in positional files.
-
X12 Transaction 005010X216 278N
EDI X12 Transaction 005010X216 278N is not included in the type tree for compliance check for the HIPAA Pack. The transaction is also not included in the EDI X12 pack (per Greg McEachern). Please create the type tree and update the compliance che...
-
Enhance PDF to type tree importer
Currently PDF to type tree importer doesn't work on extensibility on field or data level. Also most version of PDF are not supported. The enhancement of this importing would make is feature more user friend and product usability would increase
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.
1
Not under consideration