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.
DTXDS APIs for the Launcher
We are currently trying to automate a bit our software lifecycle management and we would like to automate the compilation and deployment of maps on our Linux system.We are using Azure pipeline for this automatization and we would like to have a wa...
Support ITX on Alpine Containers
This would benefit those who want to use a smaller container image that is more secure with fewer Linux library dependencies.
ITX SDK - Error handling improvement
ITXA support Bulk Update Codelist API without Version Number
Implementation-Version: 18.104.22.168(17)Build-Date: 20181003.0829
Case Number: TS001467199
We are referring here Bulk Update Codelist API . Not the Update Codelist API
We want to use the API from Sterling Business process
The below i...
Allow Terracotta to be used as REDIS Server
THis is Enhance request For REST API Asynchronous call allow Terracotta to be used.
SPE Envelope support for multiple ST/SE loops for non XMl files using the SPE.encode API
SPE.encode() translates a document and wraps the X12 output in ST/SE, GS/GE, and ISA segments. This means that to be compliant the translated output must fit within a single transaction set and a single functional group,which does not follow the H...
Request for caching to work with WTX Oracle adapter
Hello ,We have review your questions and comment with our developers in order for this result caching to work with WTX Oracle adapter, a design change would be needed in order to cache the Oracle statement handle.Currently, WTX Oracle adapter only...
WTX-Plugin: 64bit EXIT() call
While WTX is available in 64bit, its C-API (runmerc.h) remained 32bit. This leads to a bottleneck. WTX mappings without C-API EXIT() calls work with huge files (>4GB), but WTX mappings that make use of the C-API EXIT() call can handle 1.9GB onl...
static nature of calling TX maps from Java
currently, the APIs to call maps via Java works well. However, when a map is instantiated, it is via static method. Further attempts to instantiate the same class throws an error. IBM to look at this and see if there is someway to relax this behav...
SPE deenveloping service corrects automatically output BAD_GROUP link
When SE01 contains an incorrect segment count, the SPE deenveloping service fails with transaction non-compliant but the output BAD_GROUP is actually corrected data. Why and how it is corrected. If the input data is bad , we donot expect it to be ...
Do not place IBM confidential, company confidential, or personal information into any field.