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.
Maps with JSON output cards are building very slowly
I have some maps in the design studio. They take 15 minutes each to build. While the build is occurring you can see exactly what is being checked in each map - that's how slow the build is. I have never come across this before. Normally you ca...
Document verification: Support for Ignoring undefined attribute
With ITX 9 FP3(when using native schemas), we have the option to Ignore Undefined XML elements that comes in an input file from the customer that are not defined in the XSD. This way we don't need to update the maps and its reference when the inpu...
ITX Design Studio Eclipse in sync with Rational Developer for z Systems
We deploy Eclipse tooling to our developers. It would be very benificial if we can include the ITX plugin in our RDz package. The request therefore is to have the ITX Eclipse plugin upgraded to the same Eclipse version as being used for RDz. It sh...
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 say...
automapper should also work with same input/output types
It is a common pattern to work twice on a output card, e.g.:- when the output should also include summarized amounts of several output records that need to be built/calculated first- when the header should announce how many records will followNow ...
Autmoapper from output to output
The automapper is very useful, but only does input to output. In some cases, we need to prepare mapping in one output card, and enrich it later in a following output card. Currently, it can be done but needs some cards copy and moving, and this wo...
format string parser
Please add a parser/validator of format srings into the compiler, so that WTX developers are being notified of invalid format strings that won't work in the WTX engine.
WTX should not crash when a resource value is too large.
Although the limits in resource values is documented, it is still possible to enter too long a value in a mrn file.This crashes the studio when running a map, even if the faulty resource is not used by the map.The resource registry tool should als...
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.
Need to be able to specify columns when inserting data in a table from a card.
At the moment, the DB adapter does an INSERT INTO table_name VALUES (..., which implies that we insert into all columns.This makes the map depending on the table design, and in out case, where multiple projects may update the tables, create confli...