Approval
  • 28 Mar 2024
  • 12 Minutes to read
  • PDF

Approval

  • PDF

Article summary

Watch as Every Workflow Becomes a Grand Parade of Approvals!

The Approval component enables you to set up an approver who can take the necessary approval actions according to the business needs. It also helps in organizing and simplifying the approval process for different IT tasks and requests.

You have the flexibility to customize the approval process by configuring different types of approvers, specifying conditions, and defining actions. This detailed customization ensures the smooth and efficient functioning of the approval component.

User Persona - Application Designer

Figure: Workflow Approval Process

Configure Approval Component

To configure approval component, perform the following steps:

  1. Navigate to Design Studio, select module from the list and click Workflow Designer.
        The Workflow list screenshot is displayed:
    Figure: Workflow List Screenshot

  2. Click New to create a new Workflow Designer.

  3.  In the Workflow Canvas, drag and drop the User Approval component.
         The User Approval component is displayed.
    Figure: Workflow Designer Canvas

  4.  Click and select Configure Properties or double-click the Approval component.
    The User Approval - Properties screenshot displayed.
    Figure: User Approval - Properties

  5. Enter values in the required fields as described in the following table and click Save.
FieldDescription
Workflow Name*Enter the name of the workflow which reflect the purpose of the workflow, making it easy to identify and manage for which this workflow is designed to achieve.
DescriptionSpecify a brief informative description of the workflow. The description should offer a clear and concise purpose and key details of this workflow and to understand the workflow's scope and functionality.
Approval Options
Approval TypeSelect the type(s) of approval required for this workflow. The approval types specify the review and authorization processes necessary for different stages within the workflow.
The types of approval list are:
  • Static Approval
  • Dynamic Approvals
  • Based On User Attributes
  • Role Based Approval
  • User Selectable
Minimum Number of Approval
Approval Conditions *Approval Condition enables you to streamline the workflow and ensure that approvals are triggered based on the requirement which enhance the efficiency and compliance of the Workflow.
The listed approval conditions are:
  • All Members - should approve
  • Any One Member - should approve
  • Minimum approvers (in number) - should approve
  • Minimum approvers(in %) - should approve
Default Approval TypeEnables you to select the individual's name to act as the default approver if the designated approver cannot be determined.
Approval ActionThe Approval Actions (Approve and Reject) are selected by default based on the configuration in Form Designer.
The listed actions are:
  • Approve
  • Reject
  • On-Hold
  • Forward To
  • Refer Back

Types of Approvals

The type(s) of approval required for the workflow which ensures that tasks are properly authorized and executed in compliance with organization's standards. It specify the review and authorization processes necessary for different stages or actions within the workflow.

The following are the approvals type in Workflow Designer:

Static Approval

Static approvals involve fixed authorization procedures with predefined rules that remain unchanged unless formally updated. Their effectiveness varies depending on an organization's specific IT environment. The approval configure based on the combination of User or Group approvals for all approval component.

Figure: Static - Approval Type

By Users

The Users field enabled you to select an individual or an additional users as an approvers for this component. Click Select User(s) by Filter to configure filters or conditions based on the requirement.

  • Allow Requestor to Select Additional Approver(s) : Enables you to select additional approver. If the approval setup is configured for Level-1, the requestor select additional approvers; for Level-2, it can be either the requestor or Level-1, depending on the configuration.

  • Approval Selection is Mandatory : Enable to ensure that the user must select an approver during the workflow creation and ensure that an approval is an integral part of the process. It is necessity for explicit approval at that stage for the workflow to progress. This option is displayed only when the Allow Requestor to Select Additional Approver(s) is enabled.

  • Approval to be Select Additional Approver(s) : Enables you to select additional individuals for approval ensuring flexibility in the approval process.

Figure: By Group

By Groups

The groups field enables you to select from various predefined groups of approvers. When you select a static group, it displays the current count of members within the selected group, reflecting the number of individuals in that specific state.

  • Allow Requestor to Select Additional Group Approver(s) : Enables you to select additional group of approvers.
     
  • Approval Selection is Mandatory : Enables that you must select an approver during the workflow creation and ensure that an approval is an integral part of the process. It is necessity for explicit approval at that stage for the workflow to progress. This option is displayed only when the Allow Requestor to Select Additional Approver(s) is enabled.

  • Group Approval to be Selected by : Enable to select a group for making approval selections. If you have configured an approver for Level-1 then only the requester can select an additional approvers. For Level-2 approver configuration, the requester or Level-1 can select a group of approvers based on the configuration. 

The following use case from the ITSM domain on the importance of Approval Type - Static Approval.


Let's explore the following use-case.


Use Case
User Persona: Application Designer
Solution
In NovaTech, Sandra the administrator concerned about data security and wants to regulate the use of USB devices (e.g., flash drives) on its company's network and sends for approval.Fredrick the Super Admin review the request sent by Allen and approves it ensuring that USB usage aligns with security policies and business needs.


Dynamic Approvals

Dynamic approvals enable adaptable and automated approval processes within the IT environment, tailored to the unique circumstances and requirements of each task or request, rather than being rigid and static. Based on the field values in the form decides the approval is called Dynamic Approval.

Approval of dynamic groups is contingent on the values defined within the record. Once a dynamic group is selected, you have the option to select from the groups configured for the transaction table. The dynamic groups appears based on the master table of the workflow.

Figure: Dynamic Approval

Dynamic Group - The dropdown will display dynamic groups that correspond to the transaction table on which the workflow is configured. When selected, a message will display indicating the criteria that determine when the approval will occur. 

Example:

Selecting the CAB_Master group signifies that the approval will be contingent upon the Change Type, Category, and Workgroup.


Figure: Dynamic Group - Approval

The following example from the ITSM domain on the importance of Workflow Designer.

Let's explore the following use-case.


Use Case
User Persona: Application Designer
Solution
At NovaTech, Adam the analyst, submits a request to gain access to the designer tool and the Finance portal to fulfill an essential task.The requests are forwarded to various approval processes determined by the access control settings.

Based On User Attributes

In this type of approval, the approvals defined based on user attributes by dot walking mechanism. It navigates to the data by specifying a series of attributes or fields separated by dots (periods).

  • Transaction Table - The dropdown will display dynamic groups that correspond to the transaction table on which the workflow is configured.

  • User Object - Select the transaction table column that serves as the basis for defining approval. All columns are pre-defined in the transaction table.

  • Group Approval - Select the reference table associated with the selected column.

Figure: Based On User Attributes

The following use case from the ITSM domain on the importance of Approval Type - Based on User Attributes.

Let's explore the following use-case.


Use Case
User Persona: Application Designer
Solution
An employee, Sarah, needs specific software installed on her workstation to perform her tasks effectively.

The system evaluates the user attribute, which, in this case, is the employee's department. Sarah is in the Marketing department.

Based on the user attribute (Marketing department), the workflow is configured to have department-specific approvals. John, as the Marketing Department Head, receives a notification about Sarah's request. He reviews the request and the software's compatibility with the department's needs and approves it.


User Selectable

User-selectable approval allows you to select from a list of available approval options during the request is process. This provides flexibility and empowers requesters to specify who should approve their request, based on the available choices.

This type of approval simplifies the procurement process by allowing requesters to specify the most appropriate approver based on their unique needs and circumstances.

Figure: User Selectable

By Users : Select individual and additional users as an approvers for this component. Click Select User(s) by Filter to configure filters or conditions based on the requirement.

By Groups : Enables to select different static group for approver. On selecting the Static group, it indicates reflection of states how many members are present in the selected group.

The following use case from the ITSM domain on the importance of Approval Type - User Selectable.

Let's explore the following use-case.


Use Case
User Persona: Application Designer
Solution
An employee, Sarah, needs to request a new laptop for her remote work. She initiates a procurement request through the IT system portal.

Sarah is presented with a list of predefined approval options, each representing a different level of management  head. Options include:

  • Sarah's immediate supervisor, John (IT Manager).
  • The department head of the Sales team, Maria.
  • The department head of the Marketing team, Alex.
Sarah evaluates the request and considers the urgency, budget, and department requirements. She selects John, her immediate supervisor, as the approver.

Role Based Approval

Approval defined in the based on the user role by using dot walking mechanism. The approval process is established by taking into account the specific roles assigned to users within a organization. The term "dot-walking mechanism" used to automate or define the approval workflow based on the user's role, ensuring that the appropriate individuals with the necessary permissions are involved in the approval process.

Figure: Role Based Approval

Select the column names are displayed based on the selected transaction table. 

IconDescription
 To add additional records role based approval. Ensure that the data provided for the new item adheres to the relevant requirements.
Enables you to specify whether the selected Approval Role is required or optional. You can set the field as mandatory, indicating that users must approve this record before proceeding to other. In the list of records at least one record should be mandatory.
Enables you to delete the approval role record.

The following use case from the ITSM domain on the importance of Approval Type - Based on User Attributes.

Let's explore the following use-case.


Use Case
User Persona: Application Designer
Solution
In NovaTech, Sandra an administrator raise a change request to her reporting manager to upgrade the Operating System on her Laptop.The reporting manager of Jennifer evaluate the request based on the alignment with IT policies and approves the request which route to the concern team to take appropriate actions.

Configure Field To Be Filled by Approver

The "Configure Field To Be Filled By Approver" section allows you to specify the access level (view and edit) granted to selected approvers. Fields with restricted access are configured in the Security tab of the Sub Form within the Form Designer. Here, you can define which fields the approver can view on the sub forms.

Figure: Configured Field To be Filled By Approver

Click the Select Field dropdown to view configured fields, for which you can specify the type of access for the selected approval.
 Figure: Select Field

Select the check box corresponding to the field, then enable the appropriate switch option provided in the "Select Field" dropdown to grant the following accesses to the approver

View - Enables the approver to view and review certain information without the ability to make any changes. It ensures transparency and facilitates the approval process by allowing approvers to assess the relevant data before making decisions.

Edit - Enables the approver to modify specific information, granting them the flexibility to update, correct errors, or make adjustments as required. Turning on the edit switch also enables the view access.

Mandatory - Enables the approver to provide approval on specific fields. Without this approval, the process cannot proceed to the next step. When the fields are marked as mandatory, then it must be filled by Approvers for the approval action on a record to be completed. In approval reminder emails, if mandatory fields are present, the Approval Action buttons should not be visible. Instead, a message “This record has some mandatory fields to be filled as part of Approval Process. To approve the record please click here.” should guide approvers to the ticket page to fill these mandatory fields and complete the approval process.

Approval Conditions

The required number of approval conditions varies based on the organization's specific process complexity. It can range from a single condition in basic workflows to multiple conditions in more intricate processes.

The defined minimum approval conditions are:

  1. All Members – should approve - In this approval type, every member's approval is necessary for the process to be finalized.

  2. Any One Member - should approve -  In this approval type, any one member's approval is necessary for the process to be finalized.

  3. Minimum approvers (in number) – should approve - In this approval type, defined number of approval is necessary for the process to be finalized. 

  4. Minimum approvers (in %) – should approve -  In this approval type, define the minimum % of approvers who should approve is necessary for the process to be finalized.

    Note
    The define number should be whole number only.

Approval Action

The approval actions are the actions performed by the approvers are authorized to perform approval actions which are:

  • Approver 1 can Approve, Reject, On Hold, Forward To, Refer Back

  • Approver 2 can only Approve & Reject

  • Approver 3 can Approve and keep it On-Hold but not Reject

Approval actions are activated accordingly. You can customize the display name to appear on the transaction screen and establish a workflow action, which appears as a node within the Approval component. Subsequent workflow steps can then be defined based on this approval action.

Figure: Approval Actions

The table provides explanations for the following listed actions:

ActionDescription
ApproveThe Approve action validates and authorizes a request, to move to the next stage of the workflow.
RejectEnables you to reject a request if not align with the requirements.
On-HoldEnables you to temporary suspension of a workflow request. This can be necessary when additional information or clarification is required.
Forward ToEnables you to delegate a task or request to another individual or team when the initial recipient is unable to handle the task, is out of the office.
Refer BackEnables you to refer the task or request back to a previous step for correction and reevaluation.
Approval Not RequiredEnables you to progress without the delays associated with approval steps.

Refer Back

Using the Refer Back feature allows for a reassessment of the task to ensure alignment with organizational objectives and handling exceptions by returning to a prior stage in the workflow.

Figure: Refer Back

FieldDescription
Permitted Refer Back Levels*The configured approval levels, with the display reflecting the approval hierarchy (L1, L2, and L3).
Default Action on Resubmission*Specifies the action that occurs when a request is resubmitted after a 'Refer Back' action. The request can either be routed directly to the referring approver or follow the standard sequence of approvals once more.
Allow approver to select action on resubmissionEnables you to empowers approvers to determine the Action on Resubmission. Selecting 'Yes' provides the approver with a dropdown for this purpose, while 'No' eliminates the dropdown option.
Notification Template

It determines the notification medium. Depending on the selected template, the corresponding Notification template for 'Refer Back' can be selected. 

Recipients are dynamically chosen based on the Current Approver's selected 'Refer-Back' level. 

For Example, if an L3 approver refers back to an L1 approver, the notification will be sent to L1 in the 'To' field and to L2 and L3 in the 'Cc' field.



Was this article helpful?

What's Next
Changing your password will log you out immediately. Use the new password to log back in.
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.