Approval lifecycle overview - Adaptive Applications - BlueCat Gateway - 25.1.1

Quick Service Administration Guide
ft:locale
en-US
Product name
BlueCat Gateway
Version
25.1.1

Quick Service v25.1.0 introduces the approval lifecycle feature. With this feature, administrators can designate specific zones, networks, and their child objects to require approval for changes (addition, modification, and deletion). As a result, an approval request is created every time users make changes to such zones, networks, and their child objects. In addition, this feature enables administrators to set specific users as approvers, allowing them to approve or decline approval requests.

Objects that require approval for changes are referred to as approval-managed objects.
Note: Existing child objects of approval-managed parent objects will not automatically inherit this approval requirement. However, this requirement is inherited when creating new child objects for approval-managed parent objects.

  • Adminstrators can use the Approval managed objects tab to view and manage these objects. For details, refer to Approval managed objects tab.

  • Adminstrators can use the Manage Approvers tab to view and manage approvers. For details, refer to Manage Approvers tab.

The following table provides details on the approval permissions configured for each user role:

User Role Approval Permissions
Administrator Can make changes to approval-managed objects without requiring approval, and can approve changes made by approvers and regular users.
Approver For own changes made to approval-managed objects, requires approval from either the administrator or an approver. Can approve changes made by regular users.
Note:

  • Approvers cannot approve their own requests.

  • To be assigned approver permissions, users must be part of a user group that has Read-Write permissions.

Regular user Requires approval from either the administrator or an approver for changes made to approval-managed objects.

Approval lifecycle

This section provides a high-level overview of the approval lifecycle for a change made to an approval-managed object. For additional details, refer to Approval lifecycle page.

  1. A non-admin user makes a change to an approval-managed object (zone or network).

  2. The user clicks the Request change button to enable the creation of an approval request for that specific action (create, edit, or delete).
    Note: The standard Submit button in the Create/Edit/Delete forms is replaced by the Request change button for approval-managed objects.
  3. If an open approval request for the same operation on the selected object does not already exist, the request is successfully created. The Approval lifecycle page displays this request with the status Pending.
    Note: At this stage, the user (creator of the request) can choose to cancel the approval request if required, by clicking the vertical ellipsis icon in the Actions column for the object, then selecting Cancel). As a result, the status of the request is updated to Cancelled.
  4. An administrator or approver reviews the approval request. One of the following occurs:
    • If the request is approved, the status of the request is updated to Approved, and the change is applied to the object.
    • If the request is declined, the status of the request is updated to Declined, and the change is not applied to the object.
    • If the request approval fails due to an error, the status of the request is updated to Failed.