CAB Meeting - Use Change addition conditions to only pull tickets pending approval from chg team

[Rene Ferretti J]

I'm not sure if perhaps our scenario is specific to our enterprise, but given the small size of our team (2 members) we're hoping there is a way to use the Change addition conditions in the CAB Meeting form to filter and only load change tickets into the Agenda Items which are pending sign off from our Change Management group members. 

We require that change ticket requesters follow their change ticket approval lifecycle to ensure all prior approvals are received before requiring Change Management team's sign off.  We then pull those tickets into our CAB Meeting agenda to review the proposed changes for discussion and provide approval on call for implementation.

Any guidance/suggestions with regards to our processes OR on how to accomplish our filtering would be greatly appreciated, thanks! 

[Kieran Anson]

Hi Rene,

OOTB you would do this based on state. The 'assess' state is used for peer-review and other technical approvals, where-as the Authorize state is used when CAB approval is required. That is a super broad and is often tweaked/customised by customers.

When your changes are awaiting change management/CAB approval, are they in the Authorize state? or does your Authorize state also consist of other approval levels?

[Rene Ferretti J]

Hi Kieran,

Thank you for your feedback! Interesting you should say the state flow for the change should utilize the 'assess' state for the approvers and implementers sign off and then switch to 'authorize'.

In our environment, when you hit 'request approval' it moves from 'new' to 'assess' and waits for the Approval group sign off first, once approved then it moves to the 'authorize' state and bundles the implementer assignment group and change management group for sign off.

We inherited our SN instance from a previous group, who I guess would've changed the OOTB flow, but I was under the impression that this was the flow when we compared it to a new PDI?  

[Kieran Anson · Accepted solution]

Ah!

Unfortunately developers do weird and wacky things with change management. Below is a snippet of a clean instance where CAB approval triggers in Authorize state for high and moderate changes.

You may have a field added on your change requests that is be checked/set to a value to show cab approval is required. Without being in your instance it is hard to say and might require an admin to poke-around before looking at changing your workflows/flows

[Rene Ferretti J]

Hi again Kieran, looks like we're going to have to check our setup and see if we can get back to the config your instance is in, that should take care of our filtering issue.  Thanks!