After releasing the Change management module to our users on Istanbul, we are in the process of upgrading to Kingston. We noticed the new ui action "Revert to New" but it wasn't functioning for us. After some digging I found that the script include it calls has the names of the workflows hard coded. I updated the OOB change workflow to a new name and changes our custom workflow to the OOB name. However, I'm still running into issues:
Observations in a personal dev instance:
- Create new change request (workflow initiated and waits for "Assess")
-
- Log shows entry of "Workflow starting: Change Request - Normal, for CHG003007"
- Click Request Approval (workflow moves forward and assigns first level approvals)
- Click Revert to New (approvals show cancelled)
-
- I kept the workflow context open when reverting because I was under the impression the current workflow gets deleted and a new one is initiated, but:
-
- Refresh of the previous workflow context record doesn't show "Not found", it refreshes and shows that it's back at the waiting for assess
- Log shows a second entry of "Workflow starting: Change Request - Normal, for CHG003007"
- Click Request Approval
-
- New approval entries are created
- No new log entries
Observations in our instance:
- Create new change request (workflow initiated and waits for "Assess")
-
- Log shows entry of "Workflow starting...."
- Click Request Approval (workflow moves forward and assigns first level approvals)
-
- We have a sub workflow handling the approvals, so the log shows "Workflow starting: Primary Approval..."
- Click Revert to New (approvals show cancelled)
-
- I kept the workflow context open when reverting, like above
-
- Refresh of previous workflow context record shows "Record not found"
- Log shows a second entry of "Workflow starting" for both the parent and child workflow, without the change being at assess. However, there are no new approvals
- Click Request Approval
-
- No new approval entries are created, so nobody can approve (change is moving to assess)
- Now new log entries
I'm going to attempt something to delete the subworkflow if the parent is deleted. Perhaps this is our issue? Just wondering if anyone has run into this before or has ideas on what else might be the problem.
I am able to trigger the sub-workflow delete. I did some further testing in our instance:
- Create change (workflow shows started at 1:35) and submit for approvals
- Revert to new (workflow shows started at 1:40)
- Request approval again (workflow shows started at 1:40)
So the issue seems to be that upon "Revert to New" it is triggering a new workflow, but it's moving through assess immediately and moving to the approval step, but also no triggering new approvals. I checked the conditions on both the OOB and my workflow and I'm not seeing any reason for this.
