This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
ITX being a robust product , there a strong feeling that when we look in to the trace on failure of a file its being bewildered or unclear at which point of input data error has occurred. New option can be introduced showing only the failing value...
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' is ...
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 Sterling ...
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. Com...
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.
Do not place IBM confidential, company confidential, or personal information into any field.