Patching Processes

Patching Processes serve as the primary method for deploying patches to Business Units or adding Patches to a Deployment Channel. As with Patching Strategies, OneSite Patch includes prepopulated Patching Process templates that address most processing scenarios.

Patching processes define the Patching Strategy logic based on Patching Strategy settings, such as the following:

• Approval processes for patches.

• User notifications.

• Prestaging content.

• Deploying to test labs before production.

• Routing patches to appropriate deployment channels, or directly routing them to business units for deployment.

Creating Patching Processes

If you want to create your own Patching Processes, enter a support ticket and request help from Adaptiva Customer Support.

Patching Process Templates

Immediate Deployment, No Phasing, Initial Patch Manager Approval

Each of these processes requires an approval step before deploying updates.

• Immediate Deployment- Initial Patch Manager Approval

Approval required prior to deployment, then deploys at once.

Immediate Deployment, No Approvals Needed

Except for the Default Patching Process, each of these strategies requires no approval before deploying updates.

• Default Patching Process

• Phased Deployment No Approval

  • No approval needed prior to deployment. Deploys in phases

• Immediate Deployment No Approval

  • No approval needed prior to deployment. Deploys at once.

• Immediate Phased Deployment No Approval

  • No approval needed prior to deployment. Deploys in phases.

Phased Deployment Processes, Approval Required

• Immediate Phased Deployment - Initial Patch Manager Approval

  • Approval required prior to deployment. Deploys in phases.

• Phased Deployment - Initial Patch Manager Approval

  • Approval needed prior to deployment. Deploys in phases.

• Phased Deployment - Phase Patch Manager Approval

  • Approval needed prior to deployment. Deploys in phases.