Setting up a Change Approval Policy seemed fairly straight forward from looking at documentation and this blog post
instance i'm working in upgraded from Kingston to Madrid, so to incorporate the new change approval policy i had to replace the change request workflow activity and and in place of our original CAB approval activity, swap in the new Change Approval Policy activity, and set it to use the Change Approval Policy i created.
Issue: currently when it reaches the CAB approval activity it skips through as Approved rather than execute the group Approval that is defined in the associated Change Approval definition
there are a few moving parts with these, heres what i have setup:
self created change approval policy that references change request table, and has no condition (intended for any change request)
For Decision inputs, i had setup a couple different ones:
1. change request.assignment group is "group A"
2. change request.assignment group is " group B"
each of the above has their own Answers (Change Approval Definition) which is to trigger a group approval to different groups.
instead, the change request workflow gets to the authorization approval activity and just skips through it: Results = Skipped, and goes down the Approve branch of the activity (there is only Approve or Reject).
i've looked at it over and over comparing to documentation and other community posts, closest i've found to anything that seemed at all related was this post but i'm a little cautious about editing the Workflow Activity Definition as Dak proposes without allowing other gurus to shed light and point me in a good direction for troubleshooting my setup. Also in that post it seemed to have to do with an approver not actually being in the system whereas that isn't my scenario. i'd really like to know why the workflow activity is resulting in Skipped vs triggering the Group Approval
thanks
update:
so in a developer sandbox i was able to successfully copy the original "Normal change policy" and make it my own and it worked as expected in the normal change request workflow. I also noted that the new normal change request workflow is different than ours (even our OOB Normal Change request workflow- as in didn't get updated in the last upgrade. so i may see about adding the deltas which are some Hold activities that happen adjacent to any Approval activities). Also, in the customer instance i'm going to try copying Normal change approval policy wheras last time i simply created a New one. i dont see anything in documentation that would say contrary but apparently i've not got something right.
ideas welcome, thanks
