You need to coordinate updates and deployment for managed solutions containing completed work without disrupting...

Box 1: Deploy a patch with the changes made from the current solution.

Scenario:

The Onsite Visit managed solution has a table that is not in the Verification Process Automation managed solution. This table must be upgraded prior to the go-live date without the other shared components.

Box 2: Deploy a full copy of the original solution using the upgrade option. Then, deploy the new solution by using the update option.

Scenario: All components required for the verification process must be included in a new solution.

Corporate security requires that deployments to non-development environments must be automated using service accounts.

Managed solutions are used to move customizations from the development environment to other higher-level environments. These solutions are created and maintained by the power users and provided to internal IT for deployment when they are ready.

Note:

Upgrade This is the default option and upgrades your solution to the latest version and rolls up all previous patches in one step. Any components associated to the previous solution version that are not in the newer solution version will be deleted. This is the recommended option as it will ensure that your resulting configuration state is consistent with the importing solution including removal of components that are no longer part of the solution.

Update This option replaces your solution with this version. Components that are not in the newer solution won't be deleted and will remain in the system. This option is not recommended as your destination environment will differ in configuration from your source environment and could cause issues that are difficult to reproduce and diagnose.