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.
Improve performance of SERIESTOTEXT function
Currently the SERIESTOTEXT function does not distinguish the type of an object when the same field from the type tree is passed at different level. To make things clear, below is an example of a typical ANSI X12 type tree and the 'X12 Segment'...
Expand MapName Field
Expanding the map name field will help us us maintain standard Map naming convention with proper description of the map function and the associated standards. The current limitation of 32 bytes is not sufficient. Other mapping tools like Sterl...
Option to fail map warning return codes
In addition to current min/max size for each field in type tree design of a layout, enable a starting position for each field in layout once type tree is construcred.
When handling flat files or implicit file it is difficult to locate a data without its position. It is time consuming to locate a value in the input file that has to indicator or delimiter.
In addition to current min/max size for each field in ty...
Creation of an ANSI X12 type tree that supports Plan Member Reporting.
The transaction is actually an 834 but is different from the 005010X220A1 834 used for Benefit Enrollment and Maintenance. The GS08 value for this transaction is 005010X318 and the TR3 was releases in November 2016.
HIPAA Pack Compliance Check add additional segment terminator defined in the X12 implementation guide.
Compliance check is failing when the File Separator <FS> x'1C' is used along with carriage return and line feed. <FS><CR><LF> will cause a compliance error, <FS> without the <CR><LF> passes compliance. Co...
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.
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.
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...
Do not place IBM confidential, company confidential, or personal information into any field.