Creators must have specific role permissions in either Environment Role RBAC (role-based access control) or WSRBAC (Workspaces Role-Based Access Control) to access the Application Dependencies Dashboard tool.
Module dependencies may include scenarios like the following:
One module executes a remote call to another module.
A module retrieving submission data from a schema module.
A Creator importing one module into the Panel component of another module.
Access Requirements
Access to the Application Dependencies Dashboard tool requires holding specific role permissions in either Environment Role RBAC (Role-Based Access Control) or WSRBAC (Workspaces Role-Based Access Control).
If using Environment Roles (not using WSRBAC), Creators with the appropriate role can view all data available in the dashboard.
If using WSRBAC:
Creators can view data related to modules and workflows in workspaces where they have access.
If a Creator cannot view certain data, it typically indicates that they do not have access to the workspace containing the relevant module.
To access the Application Dependencies Dashboard tool, navigate to your environment, click Resources, and select UDLC Toolkit:

Under the Plan and Design section of the UDLC Toolkit, locate the Application Dependencies tool and click the Use this tool button:

The Application Dependencies tool displays the dependencies between all modules in your environment.

To view dependent modules, open the Application Dependencies Dashboard tool in your environment. Search for a single module ID or filter across multiple workspaces.
Modules configured using best practices display on the dashboard. The first two columns display the module ID and title of the non-dependent module. The next two columns display the module ID and title of the dependent module. The far right column displays the relationship type between the two modules.
Relationship types include:
Execute: When a module performs a remote execute using another module.
Import: When a module imports another module.
By default, the table displays the first 10 dependencies. Use the pagination buttons below the table to view more entries.
Your environment may contain many application modules. The dashboard includes built-in filters to help you locate specific ones. Use some or all the filters at the same time, depending on how narrow you want the results. Filter by either module in the dependency relationship, for modules that import another module, or for modules performing a remote execute with another module. As you enter text into the fields, matches display automatically.
Let's examine the dashboard's filters:
Filter | Description |
|---|---|
Module ID | Filter by the module ID of the module dependent on the other. |
Module Title | Filter by the module title of the module dependent on the other. |
Dependency ID | Filter by the module ID of a module that another module depends on.
|
Dependency Title | Filter by the module title of a module that another module depends on.
|
Type | Filter by the dependency between the two modules. Select either Execute or Import. |