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.
|Priority||Medium - Important|
|IBM's success depends on gathering feedback from customers like yourself. Aha Ideas Portal is the third party tool through which IBM Offering Managers gather feedback from customers such as yourself.|
|IBM is a global organization with business processes, management structures, technical systems and service provider networks that cross borders. As such, the information collected through Aha Ideas Portal (Customer Name, Customer Email Address) will be stored by them in the United States, and handled only as per IBM's instructions and policies. Your data (Name and Email Address) will NOT be shared with other IBM customers.|
|In order to safeguard your information in Aha, do not leave your workstation unattended while using this application, log off after using it, and print only if necessary. If you need to make a hardcopy, remember to pick up the print-out immediately, keep it under lock, and destroy it immediately when no longer needed.|
|NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "firstname.lastname@example.org" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions|