Ticket Application Examples
Case 1: Creating a Classification Approval Ticket to Control Resource Requests Based on User Departments
- 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.
Approval Process
A user submits a ticket to apply for access permissions for resources based on the department that the user belongs to.
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.
An account with permissions of the admin administrator can approve or reject any ticket on any node, and the result is the final result.
Case 2: Creating a Classification Approval Ticket to Control Resource Requests Based on Resource Departments
- 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.
Approval Process
A user submits a ticket to apply for access permissions for resources based on the department that the resource belongs to.
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.
An account with permissions of the admin administrator can approve or reject any ticket on any node, and the result is the final result.
Case 3: Creating a Ticket with Fixed Approval Process and Countersign Form
- 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.
Approval Process
A user submits a ticket to apply for access to resources of a department that the user does not belong to.
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.
An account with permissions of the admin administrator can approve or reject any ticket on any node, and the result is the final result.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
