Need ability to define hidden exit values for a workflow step

Description:

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.