Chat now with support
Chat with Support

GPOADmin 5.13.5 - User Guide

Introducing Quest GPOADmin Configuring GPOADmin Using GPOADmin
Connecting to the Version Control system Navigating the GPOADmin console Search folders Accessing the GPMC extension Configuring user preferences Working with the live environment Working with controlled objects (version control root) Checking compliance Editing objects Synchronizing GPOs Exporting and importing
Creating Reports Working with the GPOADmin Dashboard Appendix: Windows PowerShell Commands Appendix: GPOADmin Event Log Appendix: GPOADmin Backup and Recovery Procedures Appendix: Customizing your workflow Appendix: GPOADmin Silent Installation Commands About Us

Enhanced workflow approval

You have the option of implementing a further safeguard by designating and modifying multi-level approvers. With this option, the required approvals at all levels must be granted before an object becomes available for deployment in the live environment.

Not everyone in a named group has to approve, just the required number. For example there may be 10 members in Group B but we may require only 3 approvals from that group to satisfy our requirements.

When you create a role within GPOADmin, you now have the option of empowering that role with the Modify Approval Workflow permission.

2
Open the Roles tab and select Add New Role.
4
Scroll down the list of permissions and select the Modify Approval Workflow check box.
5
NOTE: You can view an existing role’s rights by selecting the role, selecting View Role, opening the Rights tab, and noting the permissions that have been grated.

Use caution granting this permission. A user with this permission can add, modify or delete the approval workflow a requested change must follow before it modifies the live environment.

Changing the approval workflow

By default, approvals are processed in the order listed on the Approvals tab in the Container or Item Properties. Optionally, approvals can be performed base on count where the any approver can approve at any time. In this case, the item status will change to Pending Deployment once the total number of received approvals equals the total sum of the required approvals.

NOTE: You can select the Override inherited work flow check box if you want the approvals process for a container to be different from its top level container.
2
Open the Approvals tab and select the workflow type you want to manage.
1
Click Add to select a user or group.
1
Click the "-" button to the right of the level of approval you do not want.

Withdrawing approval

Before the final approval has been made and the changes have been deployed, any approver has the right to withdraw their approval. When any approval is withdrawn, the process begins again from the start.

Approving and rejecting edits

Once an object has been checked in and the Approver has been notified that the offline changes are ready for approval, the changes are either approved or rejected.

1
Expand the Version Control Root node, and the required container.
1
If this option has been configured by the administrator (see Configuring the Version Control server ), approvers will receive an email with the subject line “Approval Request Notification”.
2
Click to Approve or Reject and enter a comment as the body of the new email message to perform the selected action for the requested changes.
1
Expand the Version Control Root node, and the required container.
Related Documents