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,
Post an idea
Upvote ideas that matter most to you
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 offering manager 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.
For product documentation, see Knowledge Center. Create and View Support Cases and Use the Discussion Forum here
Workflow bulk termination and restart enhancements
In developing GRC workflows, it's apparent that if we publish a workflow version and users begin to use it, and then we publish a newer version of the workflow later on, the users are expecting to see the newer version reflected in their existing data.
This is not possible currently. We have to terminate the existing instances of the older workflow version, and then we have to resubmit those objects to the new version of the workflow.
Right now, this is a manual process. We have to select all the running instances of the workflow to terminate. Then we have to recall which objects we terminated on, so that we know which ones to start the new version of the workflow on. We are not able to use bulk start because the bulk start will start the new version on any object that meets the applicability. For manual start workflows, where the user chooses when to start the workflow, this is undesirable.
These challenges and cumbersome steps could be alleviated if there were enhancements for any of the following:
1. A way to push out the new version of the workflow to existing running instances? I.e. as long as the current stage of the running workflow instance matches a stage in the new version of the workflow, would be wonderful to have a way to migrate objects running the old version directly to the same stage in the new version of the workflow.
2. Bulk termination of workflow instances (instead of having to select the ones to terminate, can there be a way to terminate all running instances of a particular workflow, similar to the bulk start operation)?
3. Bulk start of workflow. Rather than having to restart on all objects meeting the applicability rules, would be greatly helpful to allow us to filter which objects we want to start the workflow on, check them off, then start in bulk.
4. Bulk Restart of a workflow in a single step. Would be great if we can choose objects to terminate and in addition to a "Terminate Workflow Instances" button, we also had button for "Terminate and Restart Workflow Instances", so that it would both terminate and then restart the workflow in one step. This would prevent the need for "remembering" which ones we terminated. When we want to restart the workflow for some of the objects.
Do not place IBM confidential, company confidential, or personal information into any field.