Application Dependencies

When one versioned application uses modules from another versioned application, the second application must be set as a dependency of the first. Dependencies ensure that both applications use compatible, versioned states of each other.

What Defines a Dependency

The following module relationships create a dependency between applications:

• Imported modules (direct and nested)
• Module executions
• Workflow hand-offs
• Submission references
• Dynamic Refresh configurations
• Header and footer modules
• Login and logout modules
• Transforms

When versioning is enabled on an application that already has these relationships, the platform detects and adds the dependencies automatically.

What Is Not Included

The following elements are excluded from versioning and do not create dependencies:

• Data Collections: The data stored in each environment is not versioned — only the structure and logic are versioned.
• Managed Assets: These include PDFs, images, and CSS files.
• Environment Configurations: These include integrations, RBAC policies, and SSO settings.
• External Services: References to external APIs are versioned, but the external services themselves are not.

Open the Manage Dependencies Dialog

To open the Manage Dependencies dialog:

1. In the module toolbar, click the checkout pill.

   

2. Select Manage Dependencies.

Important: Manage Dependencies is only available for versioned applications and requires update permission. The dialog is read-only when viewing a published version. Switch to a branch to make changes.

Manage Dependencies Dialog

The dialog lists all applications that the current application depends on. Use the search field to filter by name. Each row shows the application name and the version currently set as the dependency. Click the (ellipsis) on a row to access Change version and Remove.

Add a Dependency

To add a new dependency:

1. In the Manage Dependencies dialog, click Add dependency in the dialog header.
2. In the search field, type the name of the application to add.
3. Select the application from the results list. Applications with versioning enabled display a Versioned badge.
4. In the version picker, select the version to use as the dependency.
5. Click Add dependency.

The dependency displays in the list. If the application does not appear in results, it might not be published or might not have versioning enabled.

Change a Dependency Version

To change the version of an existing dependency:

1. In the Manage Dependencies dialog, click the (ellipsis) on the dependency row.
2. Select Change version.
3. In the version picker, select the new version.
4. Confirm the selection.

A confirmation message displays.

Remove a Dependency

To remove a dependency:

1. In the Manage Dependencies dialog, click the (ellipsis) on the dependency row.
2. Select Remove.
3. In the confirmation dialog, click Remove to confirm.

The dependency is removed immediately. If the removal fails, an error message displays with details.