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.
Utility to check compatibility and compliance of maps when upgrading to a new ITX version
ITX to provide an utility that can check if th existing maps are compatible with the new version of ITX or needs recompilation/modification. For shops with hundreds of maps this will identify the maps that need some action, hence improving the mig...
Expand MapName Field
Expanding the map name field will help us us maintain standard Map naming convention with proper description of the map function and the associated standards. The current limitation of 32 bytes is not sufficient. Other mapping tools like Sterl...
Include ISA information in either the data passed to the hcsvu exit for implementing a type 7 rule in the qualifier file or in the data passed to a type 7 custom user exit
We currently have a requirement to compare one of ISA value to 1000A NM1 values to ensure they are same and it is currently no doable in ITX. We received this as a suggestion from support ticket TS005672303
Claim level reject enhancement
Currently with claim level rejection if there are duplicate CLM01 values, claim level rejection is not possible. We would like the recommend an enhancement to check the entire CLM segment for duplication which may eliminate the duplication of the...
Reset reused workfiles for maps in the Launcher
Reusing workfiles makes map faster as it speeds up the alidation process.However, changes in data mean special care has to be taken to avoid issues for the concerned maps. Currently, one has to manually remove the workfiles after the Launcher was ...
Reset Launcher "Black list" for failed messages
Whenever a message triggers a map failure, even if the failure is not related to the message's content, the message is blacklisted by the launcher and will not be trigered again. This avoids "poison messages" but needs a restart to have the messag...
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...
Database Interface Designer should take care of all character sets, and not only the obsolete ones
Currently (in 18.104.22.168 and earlier), Database Interface Designer cannot be told to use character sets other than the "historic" ones.It is of course possible to convert the type trees later, but would be better not to have to.
ORACLE adapter cannot take benefit of DEFAULT values
We have maps which need to be able to use the DEFAULT value for some columnes, based on business rules.At the moment, there's no way to use the DEFAULT values, and a DEFAULT ON NULL does not solve all our issues.
redesign Oracle adapter for BLOB datatype
The current Oracle Adapter has the following restriction: columns with datatype BLOB can be used on input/output cards only. It's not possible to use them in DBQUERY/DBLOOKUP commands due to string restrictions that are caused by the fundamental a...
Do not place IBM confidential, company confidential, or personal information into any field.