With the advanced policy, manual patching happens at a policy set level instead of at a patch level (as is the case with hierarchical or group-based).
Manual patching in advanced policy
1. Go to Modules > Patches and click on one of the patch views that are organized by status.
2. You can see the list of associated assets for this patch in the Associated Assets column (scroll to the left to see it).
3. Select the patch(es) you want to work with and click on on one of the three available actions at the right top.
4. From the drop-down, select the policy set(s) to which the asset(s) belong and hit approve/reject/install. You can select multiple policy sets here.
5. You can perform manual patching at an asset level as well from the associated assets pop-up individually or in bulk.
Order of precedence
A patch override can be done at multiple levels. Here's what the order of precedence for a patch looks like in the advanced policy:
Manual override > Policy set override > Global override > Automatic Approval Configuration
Manual override: This is when you manually approve a particular patch (at a policy set level or an individual asset level)
Policy set override: This is when you specify a particular patch's KB or key to approve/reject it at a policy level.
Global override: This is when you specify a particular patch's KB or key to approve/reject it globally.
Automatic Approval Configuration: This is the approval matrix that you configure at a policy level, which will apply if no overrides are in place. This means that the patch configuration you have made for your policy set applies directly, without overrides at any level.