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
Legacy Inflight to have search option based on User ID for protocols (FTP/SFTP/AS2ID/HTTP/OFTP2(SSID/SFID))
We have request from high volume customers like VF Services/Ceva etc requesting for change in the protocol relationship as the partner has moved to other service provider/change in the protocol url's or moving from one protocol to other like (FTP ...
Display Partner Communication Details under Inflight Event Details Section
Currently, We can only see Partner protocol profile ID and communication POD Process ID details at the final delivery step ( Protocol Started Step in Inflight ) while delivering the outbound document to trading partner. Since these are Internal in...
Add a new filter that allows customers to search by the Output File Size. This should have an 'Equal / Greater Than / Less Than (Variable Condition). We should ALSO make this field available as a Column Selection in InFlight so customers can "show...
Add version manager for BPN rules and version change history(Salesforce Case number) as searchable field
Current BPN rules(specific to a customer) does not have any unique name(like partner name or anything unique)which troubleshooter can use to collect/trace all rules where message can pass to.
As we have version manager for...
XML to EDI outbound data does not inlcude reference to ST envelope within InFlight
Whether source format is FLAT file or XML file, we should always display ST envelope details in inflight (if we can find a match during enveloping service). In a nXML_TO_EDI flow, XML flow uses typing service where a typing map is executed (instea...
In advanced search option In InFlight please add feature for checking the InFlight entries giving the protocol profile ID.
In case if an existing connection to TP or customer is having multiple flows running using the same connections then with this suggested idea one can easily list entire flows in single search option. So this suggested option will be helpful in lis...
Ability to create single relationship setup which can handle multiple folders for FTP/SFTP
Business scenario : Currently our system configuration allows only one FTP/SFTP folder to be pointed under single Sterling Commerce Inflight relationship. Sometimes we get request from client for 1xFTP/SFTP setup but route different file type to r...
Include Interchange Recipient Internal ID option in the EDIFACT UNH envelope
In SPE02 while working on client Celestica we came across a limitation for the EDIFACT UNH envelope options. Celestica has two SAP systems A1 and GT. catering for plants of different regions involving multiple vendor codes. A1 SAP system is identi...
Issue: When we need JSON to XML or XML to JSON conversion, we always depend on new ITX Map. Its kind of extra work for us to convert JSON to XML and XML to JSON. We should develop a new map for every XML and JSON structure.
Why cant we have a ...
Using Inflight reports we can fetch numerous types of customer and trading partner volumes based on the data. However, we don't have any report or Analytical Dashboard for checking the volumes and health of the Relationship setups and Protocol pods.
Do not place IBM confidential, company confidential, or personal information into any field.