Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Not under consideration
Workspace Product Master
Created by Guest
Created on Aug 9, 2019

Need ability to define hidden exit values for a workflow step



When defining a workflow step, sometimes we need to define exit values that should NEVER be clicked by a user.  These exit values are only meant to be used by internal/automated processes (automated reports or imports or exports).  Ideally, these exit values should not even be displayed to the user.  That is the request.  As part of defining an Exit Value within a step, please provide a flag (or a naming convention) to indicate that the Exit Value should be "hidden" from the user.  A flag would be an extra flag to set on each exit value (which might be a challenge to add to the existing Admin UI).  For a naming convention - we can put the word "[HIDDEN]" at the front of any Exit Value that should be hidden/not displayed to the user.   That would work.  As long as the user UI (the new UI) is updated to NOT display exit values (buttons) that start with the world "[HIDDEN]".


Currently - we are placing a "don't click here" symbol at the front of the Exit Values we want the users to avoid.  Obviously, this doesn't stop the users from clicking the button.  So we have additional code that checks the role of the user.  If the user is not an admin, then our code keeps the item in the current step (by removing the item from the step transition in the "out" script of the workflow step). 


But we want to simplify the user interface. We don't want to show users buttons they shouldn't click.  But - because of the way workflows are defined - in order to move an item from one step to another step in the same workflow - we are required to create an Exit Value and a mapping for that Exit Value.  Then - in code - we can call "set exit value" on an item to move the item from one step to another step.  For *some* of these step transitions, we only want reports to perform the move, never users.  In order to support this functionality, we want to "hide" the buttons that are the exit values that users should "never" click.




  • Guest
    Oct 13, 2019

    Rejecting this RFE as it is not inline with our roadmap.