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
BPN Rule duplicate validation to avoid conflict in different files handling.
GISHI Orcharstration System does not have the validation to cross verify the duplication of existing rules, due to that, Implementation or Support Team creating the new duplicate rules for handling Customer or Partner new enhancements and it cause lot of impact for the Customer later point of time.
If this feature exists it would be good avoid duplication and Business impact will not be there.
What is your industry?
How will this idea be used?
If we have the request from the Customer where Partner already sending the 856 document to us and already Business Process exists to handle the file with the validation of AS2 SenderID, AS2 ReceiverID and later point of time, Customer came back with new implementation for CONTRL message where Customer want us to generate STATUS message, so IBM team may create the with the same set of conditions and as System not alerted they simply created and it cause all docs processing through new created business process instead of categorization and that cause impact for the Customer business docs handling way.
Do not place IBM confidential, company confidential, or personal information into any field.