Skip to Main Content
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 (

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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Apr 11, 2023

One Activity with the final Name rather than having all activity with the different Name.

Currently in PEM, if we "Mark as Final" one activity with a certain name then we cannot use the same name for any other activity even if we delete that particular activity. This cause a lot of issues with the non-development personal as to which version they should use because the development personal keeps on developing and creating new versions.


My Proposal is: That we should have a one common name of against the activity like "Partner_Onboard_AS2_SFTP" like this and in addition to that we should have a new option just like we have "Mark as Final" with the name "Final Activity" and once we click on "Final Activity" against any activity then that such activity will become the partner of the main activity "Partner_Onboard_AS2_SFTP". This way, person call always use the new activity without even thinking about which version to use.

Example: Let's say we have a PEM activity with the name "Partner_Onboard_V1" and this activity contains the custom DSV configuration for the DSV Partners. Now, when we click on "Mark as Final" to final the activity so that we can test it and can confirm if the done configurations are good or not?

Now, once we are sure that the done configurations are good. I need to click on "Final Activity". That way, this activity "Partner_Onboard_V1" becomes a Part of Main activity "Partner_Onboard_AS2_SFTP" and when we do the rollout against this activity, it will trigger the latest activity which we make the "Final Activity". Similarly, if we have another activity "Partner_onboard_V2" and we click on "Final Activity" then it will become the main activity by replacing the old activity "Partner_Onboard_V1" and the main activity "Partner_Onboard_AS2_SFTP" will not trigger the new activity "Partner_Onboard_V2".


Reference: Just like we do when we add a new version of BP, the name remains the same but that name triggers the newly added version and not the old version. So we need something like this in PEM also.