IBM Sterling
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 updates on 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
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Priority
High
Ask
•Insights into the failed messages on inflight
Details of Ask
•Provide insights into failed transactions, by providing further categorization on failed transaction .
•Grouping of failures based on sender/receiver ID combination based on error types to pinpoint unique errors
,and indicating the how long these errors in the system.Example: Total Translation failures 100:
i) Sender “ABC” /Receiver “XYZ” : Mandatory data missing: 50 (Map name:xxx , Oldest failure date/time )
ii) Sender “ABC” /Receiver “XYZ” Doc Type : Envelope Failure 25 (Missing Envelope, Oldest failure date/time)
iii) Sender “123” /Receiver “879” Doc Type : Protocol failures :25 (PPID, Oldest Failure date/time)
Impact to Clients
• Manually examining each repetitive failure, is extremely time-consuming
•Leads to Customer dissatisfaction
Impact to Support
•Capable of promptly identifying distinct error types from numerous failures
•Reduce Support efforts
Current Challenge
•Reviewing every error is a duplicate effort and time consuming
Use Case
•When encountering serval failures, identifying unique issues helps to expedites faster issue resolution.
• Knowing the age of the failures helps customers/Support to focus on resolving them.
From Dashboard Support/Customer should be able to drill down to transaction level to work on the issues.
Translation failure :Grouping based on Sender/Receiver/Doc Type /Map name /Direction/Source of the message will help to narrow down the Unique Error Types.
Protocol Failures: Grouping Protocol Failures transaction based on the PPID messages are delivered and Error message
Envelope Failures: Grouping failures based on the Missing envelope failures.
Along with grouping based on error types and if we can also have insights into from how long this issue exist in the system ,will help to Identify the repetitive issues which can help support to concentrate on reducing the repetitive errors in the system.
This will save efforts to support teams