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
get the Rollout ID to check which activity rolled out
Currently in the PEM: Activities > Monitoring page we can't see any reference of which activity is being Rolled out, we just need to reply upon the Rollout Name provided and can't really see way to know which activity with what version is used to trigger this Rollout.
This issue is getting even more serious on PP: Activities > Monitoring when we can't even have any reference and we just see the code in place of Name and its extremally troublesome that we need to open each activity to find out what the definition of it.
If We have the Rollout ID to check which activity is rolled out then monitoring would become manageable for us.
Screenshot is attached for reference purpose.
Open full size
Open full size
What is your industry?
Travel & Transportation
How will this idea be used?
With this idea we are hoping to have Rollout ID to check which activity is rolled out so we would know exactly which definition to check for troubleshooting/monitoring purpose.
Currently we need to open each Rollout to know that and then start over if its not the one we are looking for, this makes monitoring painful and makes the Product not easy to work with.
Once more and more customers starts using this troubleshooting would become more and more difficult.
Do not place IBM confidential, company confidential, or personal information into any field.