References between Application and Custom Widgets

Exported archives of analytic applications, by default, contain all referenced custom widgets.

If you use a custom widget in an application, and the application is transported between different SAP Analytics Cloud systems, the application archive automatically includes the referenced custom widgets (like it works for models as well). This way only one archive needs to be imported in the target system to get the application up and running.

Knowing the dependencies between an application and used custom widgets makes it possible to show you which applications are actively using a custom widget when you try to delete it from an SAP Analytics Cloud system. The Delete Custom Widgets dialog lists all referencing applications, and displays a warning that deleting the custom widget will break those applications.

Example

In the following example, the first custom widget is used by one application named Ticker Test, the second custom widget is not used, and the third one is used in two applications for which the user has no authorization.

Note

If you choose to ignore the warning and delete the custom widget despite of active usages, and you later realize that this was a mistake and re-upload the custom widget, the references between applications and this custom widget will stay lost.

This means that the export and the display of the active usages in the dialog will not work anymore. In this case, a warning will be displayed when you open an affected application:

Simply saving the application will repair the dependencies and the warning will no longer be displayed.