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
Database Interface Designer should take care of all character sets, and not only the obsolete ones
Currently (in 188.8.131.52 and earlier), Database Interface Designer cannot be told to use character sets other than the "historic" ones. It is of course possible to convert the type trees later, but would be better not to have to.
ORACLE adapter cannot take benefit of DEFAULT values
We have maps which need to be able to use the DEFAULT value for some columnes, based on business rules. At the moment, there's no way to use the DEFAULT values, and a DEFAULT ON NULL does not solve all our issues.
The current Oracle Adapter has the following restriction: columns with datatype BLOB can be used on input/output cards only. It's not possible to use them in DBQUERY/DBLOOKUP commands due to string restrictions that are caused by the fundamental a...
Current version (184.108.40.206) added a feature where timestamp based information is added to the compiled maps.We request to have this information optional and not by default.We also request to have the feature extended so that we can inject appropriat...
Claim Level Reject at the Provider, Subscriber or Patient Level
We have received the explanation that claim level rejection works as designed in the 2300 Loop of the 837 and does NOT have rejection capability in the Provider, Subscriber and Patient Loops. Based on our competitors’ capabilities and our client n...
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 ...
Remove limitation to not install in C:\Program Files
As per the release notes: https://www.ibm.com/support/pages/node/6362027 It is mentioned not to specify C:\Program Files as the install directory. It is requested if you could remove those compatibility issues
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.
Do not place IBM confidential, company confidential, or personal information into any field.