- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-10-2017 11:21 PM
We are investigating making some changes to the Change Management Workflow. In our Dev environment we are using Helsinki and have upgraded Change Management to use the state model.
A couple of changes we have made for context as they may relate to the question:
- The Assess State has been renamed Peer Review
- The original out of box workflow has been renamed Change Request - Normal (original)
- A copy of the Out Box workflow has been made and named Change Request - Normal. This is the workflow the changes have been made to.
- A field named Peer Reviewer has been created and is on the change form (u_peer_reviewer, see below)
The original workflow had an initial stage called Assess where the change would be sent to all members of the implementing group for approval at the Assess stage. See shot of original workflow below:
We have modified this to rename the original stage Peer Review where the change should only be sent to the "Peer Reviewer" specified in the change. See shot of modified workflow below:
Within the Approval - User step this is what it looks like:
When creating a change it still sends the approval request to all members of the implementing group, rather than the individual specified peer reviewer.
I can't seem to figure out why this is happening? I can't tell whether I am missing something in the workflow, or am doing something wrong where the Change Management process is still referring to the original workflow. It seems like it should be simple?
Any help is appreciated
Solved! Go to Solution.
- Labels:
-
Change Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-11-2017 12:00 AM
Hi Damian,
Exactly this is what I assumed and because of this I have said 'along with the new Workflow'.
Well, you need to change the triggering condition of the Old Workflow such a way that it won't trigger at all. Open the workflow-->Go to it's properties-->Set the condition, something similar as shown below.
I hope this helps.Please mark correct/helpful based on impact
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-10-2017 11:31 PM
Hi Damian,
Could you please check that whether the Old workflow is attached with the Change request instead/along with the new Workflow. I doubt this is the scenario. Please checked the attached workflow of the raised change request.
I hope this helps.Please mark correct/helpful based on impact
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-10-2017 11:42 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-10-2017 11:48 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-11-2017 12:00 AM
Hi Damian,
Exactly this is what I assumed and because of this I have said 'along with the new Workflow'.
Well, you need to change the triggering condition of the Old Workflow such a way that it won't trigger at all. Open the workflow-->Go to it's properties-->Set the condition, something similar as shown below.
I hope this helps.Please mark correct/helpful based on impact