SLAs on Approvals? (sysapproval_approver) Is it even possible?

[howard8]

Hi All,

I have a business requirement to impose performance targets on the approval/rejection of changes, to ensure that our approvers follow the timing of our CAB process. We have several groups sent separate technical approvals at the same time (application approval, infrastructure approval, security approval). I want to put an SLA on each approval but is seem that SLA definitions only work for tables based on the Task table. Approval records are on sysapproval_approver which is not based on the task table. Because approvals run in parallel it's difficult to link the SLAs to the parent record (change_request).

Has anyone ever tackled this scenario? What was your approach?

Thanks in advance.

Howard Elton

[howard8]

Yeah I could do it on the workflow but that only measures the overall approval task, and not the individual groups who make up the approval.   I am trying to weed out the 'regular offender' when it come to taking too long to approve. I might have to look at metrics or trend jobs.

[NamrataJain]

Hi Howard,

Were you able to figure out any solution for this?

Best Regards,

Namrata Jain

[howard8]

Unfortunately we were unable to come up with a solution.

[randrews]

certainly... create an SLA on the change reqeust table.. with a start condition of approval   is requested and a stop condition of approval is approved

[howard8]

Thanks Doug,

That certainly would work if the is just one approval and one approver.   It doesn't work when a change has 3 different approver groups (i.e. all must approve) each of which needs it's own SLA. It must be tied to the approval records because their can be many of them.

Howard