Ticket Application Examples

Case 1: Creating a Classification Approval Ticket to Control Resource Requests Based on User Departments

Prerequisites

You have configured required parameters, including departments, users, roles, and resources. For more details, see Department, User, and Resource.

The ticket approval process is configured as shown in Table 1. For more details about ticket approval process, see Configuring the Ticket Approval Process.

**Table 1** Parameters for configuring a ticket approval process
Parameter	Value
Approval process type	Classification
Approval form	Multiplayer
Approval node	User department – Department Manager
Approval series	3

Approval Process

A user submits a ticket to apply for resources access permissions based on the department that the user belongs to. The following figure shows the ticket approval process.

Both user A and user B (lower-level administrators) have the approval right. If either one of them approves, the ticket is approved. If either one of them rejects, the ticket is rejected. After one of the lower-level administrators approves the ticket, the workflow goes to the next stage for user C (middle-level administrator) to review. The rest can be deduced by analogy. After user D (higher-level administrator) approves the ticket, the user obtains the requested permissions. If the ticket is rejected at any stage during the approval, it fails to be approved and the user cannot obtain the permissions.

Figure 1 Ticket Approval Processes

Case 2: Creating a Classification Approval Ticket to Control Resource Requests Based on Resource Departments

Prerequisites

You have configured required parameters, including departments, users, roles, and resources. For more details, see Department, User, and Resource.

The ticket approval process is configured as shown in Table 2. For more details about ticket approval process, see Configuring the Ticket Approval Process.

**Table 2** Parameters for configuring a ticket approval process
Parameter	Value
Approval process type	Classification
Approval form	Multiplayer
Approval node	User department – Department Manager
Approval series	3

Approval Process

A user submits a ticket to apply for resources access permissions based on the department that the resources belong to. Figure 2 shows the ticket approval process.

If user D (lower-level administrator) approves the ticket, the workflow goes to the next stage for user E (middle-level administrator) to review. If user D rejects the ticket, the ticket is rejected. The rest can be deduced by analogy. After user F (higher-level administrator) approves the ticket, the user obtains the requested permissions. If the ticket is rejected at any stage during the approval, it fails to be approved and the user cannot obtain the permissions.

Figure 2 Approval process type

Case 3: Creating a Ticket with Fixed Approval Process and Countersign Form

Prerequisites

You have configured required parameters, including departments, users, roles, and resources. For more details, see Department, User, and Resource.

The ticket approval process is configured as shown in Table 3. For more details about ticket approval process, see Configuring the Ticket Approval Process.

**Table 3** Parameters for configuring a ticket approval process
Parameter	Value
Approval process type	Regular
Approval form	Countersign
Approval node	3

Approval Process

A user submits a ticket to apply for access to resources of another department. Figure 3 shows the ticket approval process.

Both user B and user C have the approval right. If both of them approve, the ticket is approved. If either one of them rejects, the ticket is rejected. After the engineering department administrators approve the ticket, the workflow goes to the next stage for user D (finance department administrator) to review. The rest can be deduced by analogy. After user E (finance department administrator) approves the ticket, the user obtains the requested permissions. If the ticket is rejected at any stage during the approval, it fails to be approved and the user cannot obtain the permissions.

Figure 3 Countersigning and approval process