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.
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
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.
Enhance the Excel adapter design to accommodate\control Excel worksheet cell properties for data added by the Excel adapter.
We would like to create $ input amounts as a 'CURRENCY' field. Since the adapter only handles output as General TEXT format we are confined to this format and no other.
ITX should be system aware with regard to the 'Native' Data language (i.e. code page) for non-Unicode applications, not hard coded to ISO-8859-1 on Windows machines.
See Case numberTS004330611 in ITX support.
Output data control
Add data control for JALE adapted, and more.
Enhancement request to create EVAL() function to calculate final value from excel formula
My input is Excel (excel adapter). Excel cell is having mathematical functions (ex: =100+200-50). While execution data is reading as 100+200-50. But my requirement is to map the final value i.e 250.
USE OF -F OR -FILE PARAMETER SHOULD NOT BE NEEDED IF USING THE THIRD PARAMETER IN THE GET() FUNCTION AS SEEN IN ITX 220.127.116.11
On ITX 18.104.22.168, the document says, The -FILE command is optional on input cards and GET rules. (For example, the workbook name is not required if a map uses the File adapter to read an Excel workbook and passes the data in memory to the Excel adap...
We need support for 277DRA (Data Reporting Acknowledgement X364)
In last meeting they did say they will provide companion guide in september.
Here is the link if you want to know more:
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.
Do not place IBM confidential, company confidential, or personal information into any field.