Exclude Dependencies

By default, applications indicated as dependencies are automatically added to deployment processes. You also have the option to prevent dependencies from being added, which may be helpful if a specific dependency is known to cause issues when updating applications with RCT Patching. For example, see Issues Updating Adobe Acrobat Products.

NOTE: Make sure you manage any excluded dependencies manually to ensure that applications continue to work correctly. 

Exclude Dependencies for an Application

Recast recommends configuring dependency exclusions using application settings rather than deployment process settings.

To exclude dependencies for a specific application:

1. On the Applications page, click the Settings cog to the right of an application.

patching-applications-catalog-w-settings-badge.png

2. In the side panel, open the Advanced tab and scroll down to the Dependencies section.

3. Toggle Exclude Dependencies to 'Yes'.

4. Click Save & Close.

Exclude Dependencies from a Deployment Process

To exclude dependencies from individual or all deployment processes:

1. Navigate to the Dependencies section in your deployment process settings or global settings, depending on whether you are excluding dependencies from one deployment process or all deployment processes.

For an individual deployment process: From the Deployment Processes page, click the ellipsis (...) to the right of the deployment process and select Manage Settings. In the Deployment process settings side panel, open the Advanced tab.

Patching Settings page with cog highlighted next to environment

All deployment processes: From the Settings page, click the Settings cog to the right of the environment. On the Environment Settings page, click Deployment Processes > Advanced.

Patching Settings page with cog highlighted next to environment

2. In the Dependencies section, toggle the Exclude Dependencies setting to 'Yes'.

3. Click Save & Close.