Handling asset-to-asset dependencies in Studio
This feature is currently available as a Private Preview only
During a Private Preview, only customers who have agreed to our Private Preview usage agreements can access this feature. Additionally, the features documented here are subject to change and / or cancellation, so they may not be available to all users in future.
For more information about our Private Preview releases, including the level of Support offered with them, see: Feature release types.
Studio packages often include multiple assets that are connected and rely on each other. Because of these dependencies, actions made to one asset, such as publishing, copying, or deleting it, can have a direct impact on other assets that reference it. For instance, deleting a Knowledge Model could break the Views that rely on it.
To help you manage these relationships, Studio offers features that allow you to:
View dependencies between assets so you can see which items are linked.
Highlight potential impacts before you make changes, reducing the risk of unintended errors.
Maintain a clear view of your package structure.
These features are currently available with the following asset types: Views, View Modules, Legacy Views, Analysis, AI Annotation Builder, Process Copilot, Insights Explorer, Forms, Endpoints, and Digital Process.
Viewing asset dependencies
When viewing a Studio package, you can see asset dependencies and usage by clicking Options - Dependencies:
You can then use this menu to open the linked assets:
Managing existing assets
When managing an existing asset with a dependency, you're prompted in the following ways:
Copying an asset: The asset you’re copying may have dependencies. You can choose to copy them along with the asset or skip them. This helps prevent broken references in the new package.
Deleting an asset: Deleting an asset that other assets rely on can cause problems. Before moving an asset to the Trash, a warning lists all dependent assets, allowing you to review the dependencies and assess the risk before confirming deletion.
Publishing an asset with dependencies
When publishing content, it is critical that an asset's dependencies are also published if they have been changed. For instance, if a View is published with a new KPI, but the Knowledge Model containing that KPI is not also published, the View will be broken for app users.
To prevent this, when selecting a specific asset for publication, the system automatically identifies and guides you to include all of its necessary dependencies. This ensures that interdependent assets are published together, preventing critical errors in your applications.
