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.
Upgrade Jetty webserver inside Sterling Integrator/SFG from Jetty 6 to latest version
Jetty 6 is old and depreciated. Please upgrade to the latest supported version.
CX/ZOS OXBL138I INCOMING COMMUNICATION : if SSL, have the SSL Profile
When a SSL incoming communication arrive and the hanshake fails, it can be because of the SSL Profile used. But, without looking precisely in the SYSSSL member, it can be difficult to see the SSL Profile which is used. It would be great if this in...
ITXA-Enhance ITXA to give option to receive only bad transaction in TAck_EDI
Currently we are receiving full EDI wrapped in HTML causing not able to troubleshoot compliance issues quickly
Compliance Check App - Consistently create REF(D9) Segment in the 277CA to tie Claim Ack back to the original good/bad 837.
Our organization needs the capability for the HIPAA Pack's Compliance Check application to consistently generate a 277CA (005010X214) with a REF (D9) segment for both good and bad claims so that the 277 Claim Ack may be tied back to the original c...
SNDPOR and SNDPRN are not mapped
Using the JALE Adapter, if SNDPOR if not mapped it defaults to CUSTOMERLS. Using the ALE Adapter, if SNDPOR if not mapped it defaults to MERCATOR. We are migrating from the ALE Adapter to the JALE Adapter are require the same behaviour for both ad...
S/EDIFACT - EDIFACT Packs
The EDIFACT type trees included in the EDIFACT packs 2.8.1 (specifically edifd96a.mtt) do not include the segments USH, USA, US, UNO which are included in the standard version.
Validate in RD8 that beginning date is chronologically before ending date
In the case of an X12/HIPAA field being a RD8 (date range), the beginning/starting date should be chronologically before the ending date. If it is not, then it should fail a Type 2 or higher check. We originally experienced this in an 820 transact...
Request for debugger in Map Editor
I was developing the map and it broke the whole system. Upon requesting for for information regarding the process, I was told that because the issue is not with the map editor but with the map, every thing is fine and ticket should be closed. I ha...
WebSphere Extreme Scale Adapter
Many validation and enrichment applications require database lookup. If the data is accessed very often, performance will be degraded. Having the ability to read from WebSphere Extreme Scale cache will solve this problem.
ITXA support for Windows10
We are planning on upgrading developers workstations enterprise wide to Windows10 and checking IBM product compatibility and found out ITXA does not support yet.
Do not place IBM confidential, company confidential, or personal information into any field.