Community Tip - Did you know you can set a signature that will be added to all your posts? Set it here! X
Anyone know why the OOB Review Workflow would be needed for a Change Request workflow when it is not in the CR workflow?
If I have Review as not Enabled, then the CR workflow will not go past the Submit task!
Perhaps a Preference setting?
Solved! Go to Solution.
Check the life cycle template you are using (asigned) for your CR workflow, and if you do not want to execute the "Review" Workflow, then within the life cycle state or life cycle phase, simply delete the "Review" workflow. Save the changes to the change request life cycle template and check it in...Then create a new change request to test it...
You have a fork with 2 options:
If you choose Oberse, you will not promote any object.
Is editing, the workflow to remove the Review activity to jump to Promote, a option?
Check the life cycle template you are using (asigned) for your CR workflow, and if you do not want to execute the "Review" Workflow, then within the life cycle state or life cycle phase, simply delete the "Review" workflow. Save the changes to the change request life cycle template and check it in...Then create a new change request to test it...
Thanks for the replies but I do not have a Review workflow in my workflow... that's my question, where / why is it getting launched.
My workflow starts but the workflow will not move past the first task unless the Review (OOB) is checked as active in the list of Workflows.
With the Review not active, the CR will show in the Submit (but the workflow is not Running) but will not move to Assign CRB task (first task on my workflow).
You might in fact have a "stealth" Review workflow in there...
When you first save a lifecycle, sometimes it automatically fills in additional workflow templates, for the phase / gate of certain states. This is really horrible system behavior. Need to agressively monitor this by looking at the saved lifecycle, Workflow tab, each state.