SOP: FRESHSERIVCE: AUTOMATIC APPROVAL FLOW SET UP
Custom Objects for Approval Set Up
The new design of approvals on Oatly uses a series of so-called Custom Objects. These are data tables that hold information about how approvals should work, who are approvers, if groups should be assigned automatically, if a note should be created on the case and if a user should be added to a software asset. The design consists of a total of 4 Custom Objects:
Access Requests Master
This object controls how approvals are made for the software, if users should be assigned to the software automatically in Asset Management, if any specific note should be added to the request after approval, and if the request should be assigned to a specific team after approval.
Multi Stage Approval Type
This object controls how approval is done for the different steps in cases where a piece of software has multi-stage approvals
Named Approvers Stage 1
This item has approvers designated for approvals that have named approvers (as well as for multistage approvals where the first step is named approvers
Named Approvers Stage 2
This item has approvers designated for multi-stage approvals that have named approvers in the second stage.
FLOW VIEWS
SIMPLIFIED VIEW OF THE STANDARD APPROVAL FLOWS USED IN STAKEHOLDER COMMUNICATION
