The Application Dependencies Dashboard tool provides a visual overview of how application modules depend on one another. This tool is particularly valuable for new contributors on a project, as it illustrates the relationships and interactions between modules in an application.
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 on Resources, and select UDLC Toolkit:
Under the Plan and Design section of the UDLC Toolkit, locate the Application Dependencies tool and click on the Use this tool button:
In the Application Dependencies tool, you can view the dependencies between all modules in your environment.
To view modules dependent on each other, you'll open the Application Dependencies Dashboard tool in your current environment. You can search for a single module ID or multiple workspaces.
If you've configured your modules using best practices, you'll see them 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 for the dependent module. In the far right column, you can view 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. Using the pagination buttons below the table, you can view more entries.
You can have many application modules in your environment, so the dashboard has built-in filters to help locate specific ones. You can use some or all the filters at the same time, depending on how specific you want to be. The dashboard lets you filter by either module of the dependency relationship. You can also filter for modules that import another module. Or, filter those that are 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. You can only filter by Execute or Import |