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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Please see this doc topic
https://www.ibm.com/docs/en/control-center/6.3.0?topic=hdisbps-setting-up-ensure-something-finishes-time-workflow-slc
Soon this will be possible. Currently, SLC events generated as a result of another event, for example a step end event, perhaps for a file transfer, or a process end event, include that "source" event's event ID and date/time value. We will be adding the message ID and return code values from the source event to the SLC event. This will allow a user to simply add one additional rule to watch for an "SLC was satisfied" event. For example, CSLC037I - Ended as expected. (Rule priority wise, this new rule would be lower than the rule that watches for the SLC events that indicate whatever was supposed to happen, did not, but higher priority than a rule that handles the SLC events that indicate everything worked as it should.) By adding a rule that watches for CSLC037I, along with a criteria that specified the source events return code, one could have an action associated with that rule that informs someone that a transfer did occur when it should, but that it failed.
Thank you for submitting the request for enhancement. We will be reviwing this with development and provide an update shortly.
Enhancement