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.
Allow HIPAA Compliance Edit to be Configurable
Allow type 2 errors to be Configurable, turning the edits on or off. Please include Stacy Barber firstname.lastname@example.org in all communication on tis RFE
WTX Type Tree needed for X12 6020 275 (X314 TR3 for HIPAA)
We have a need for a type tree for the X12 6020 275 transaction. Specifically the HIPAA voluntary TR3 X314 implementation. It is a HIPAA transaction, though not mandated, but the HIPAA Pack doesn't have a tree.
WTX EDIFACT pack outputs the unexpected CONTRL error message
About RFE No.78594, IBM has provided us with a patch. But it did not work on DataPower WTX runtime. I would like you to create a patch to work even on DataPower.
Provide single pass HIPAA compliance checking
The WTX HIPAA compliance check application is made up of multiple validation processes. The first step is to pass the data through a structural type tree to determine which transactions are valid and which are invalid. If it is determined that a t...
Provide support for VDA version 03, and incorporate into EDI standards
Provide support in SB2BI for VDA version 03 - currently only version 02 is supported. In addition, these would ideally be incorporated into existing EDI standards for use in the SB2BI map editor, similar to how X12 is handled.
Fix issue with WTX Leap second
Need fix/work around for WTX leap second issue
Improve swift typetree validation feature related to charset
When receiving a swift message, maps using swift typetree on input card may validate the message whereas it is invalid as per swift book.Indeed, current IBM WTX swift typetree don't check for invalid character used, and swift book well specify the...
WTX MQ Adapter command does not allow BOQNAME definition
In the WTX MQ adapter command list, there is no BOQNAME command to define the back out queue name. And the -EQN may not have the same results as BOQNAME. This is a request to create the -BOQNAME in the WTX MQ adapter command.
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...
Enable wildcard MSL with multiple Launchers as with single Launcher
When setting up a single Launcher source directory there is no need to specify which MSL files to run. The single Launcher event will go to the assigned directory and find/run all MSL files found. This is effectively a wild card usage of *.msl. We...
Do not place IBM confidential, company confidential, or personal information into any field.