Normal Change Workflow, Defer to CAB from Technical Approvals

[Michael Brady]

Hello all, 

I am hoping to that someone can help me out, and it must have been done before. I am trying to create a defer to CAB option from an approval request. 

I am struggling to progress a workflow, i have created a new condition in the Technical Approval options. The Approved and Rejected conditions work fine, but i added another option called Deferred to defer to CAB as opposed to rejecting it back to New. Attached is a screen shot of the Workflow, 

I created a new option in the approvals state called Deferred - matched it to the condition so that i could select an option to approve. I am sure i missing things, as i cannot get the condition when selected to move to the next part of the workflow. What am i missing please? 

[Dr Atul G- LNG]

Hi @Michael Brady 

With my lil understanding on this, you added a deferred state but how the system will know what to do on this click. Means is it on sysapproval table or not. Like we have Approve and reject which system know and as far i understood deferred system did not knwo what to do.

correct me if I am wrong.

[Michael Brady]

Hello Atul,

Correct - that is exactly that. I have never added a new condition in before, so this is new territory for me. 

you mention SysApproval table, what controls do i add and where please? do i need to create a business rule or something? I have searched through many threads, but not finding the answers. 

[Dr Atul G- LNG]

Hi @Michael Brady 

Thanks for confirmation and making my understanding correct.

Now i have few quetsions

1. Why you need deferred state in change?

2. By name i can understand the meaning of same.

A change either approved or reject never be Deferred. 

If you add this

1 Need to do changes in flow

2. Add new state in sysapproval table 

3. It will be a huge customization as you need to update flow/ scripts and other code where sys approval is used

4. It will impact globally means, will appear on RITM / Knowledge as well. 

So my personal experience, (worked as change manager) dont add deferred here. (also as per ITIL it is not good)

[Michael Brady]

Hi Atul, thanks for the response. 

Why you need deferred state in change?

This is based on Risk. If the Risk is measuring LOW then the change will not go to CAB but move to a technical approval instead. If approved, it will go on to IT Senior Management. 

If the Risk is medium or higher, it will to direct to CAB for approval and not Technical Approval, and then on to IT Senior Management. 

The Defer Option is to enable someone in the Technical Approval to Defer to CAB if they feel Technical approval is not best suited for the approval of a particular change - as opposed to rejecting it - which usually resets back to New. The Deferred condition is only to be available on the approval request. 

Does this help?