- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2014 11:19 AM
When a workflow is kicked off, it takes a 'snapshot' of the current workflow to follow. Any changes to the current workflow will not be available to any ticket that was already generated. It will only work going forward.
(If you think about it - the workflow could be on an activity that no longer exists... it really has to be this way)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2014 12:07 PM
So what your saying is that there is no way to force it to look at the new version so we can close these tasks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2014 12:11 PM
Correct, if you want to 'close' the loop, you can go to 'Active Context' under Live Workflow and kill/delete the ones that are still executing. But you would have to create new tickets if you want the new workflow followed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2014 12:54 PM
In current scenario, only option you have is to update workflow context.
- Go to active workflow contexts
- Find workflow with correct version
- Go to that workflow and update the related activity.
This fix works if workflow has not reached to that activity, or some way workflow again can come back to same activity.
Be careful while doing this. I would suggest to use this first on non prod instance.
I hope this helps!!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2014 04:15 AM
I don't see workflow correct version anywhere when I go into workflow contexts.