---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/r/application-development

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Dependencies for custom applications

# Dependencies for custom applications {#ariaid-title1}

* Release version: Australia
* 
* Updated June 2, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Every custom application record includes a related list identifying its dependencies on other applications. Dependencies are references from your custom application to functionality provided by other applications or plugins
installed on the instance.

The ServiceNow AI Platform tracks dependencies automatically so that when your application is installed on another instance, the platform can:

* Verify that required components are present.
* Prompt the administrator to install missing components before installation proceeds.

Without accurate dependency information, your application may fail on instances where those supporting components are missing.

The platform determines dependencies based on the components your application references outside its own scope. Common examples include:

* A business rule that calls a script include from another application.
* A flow that uses an action provided by an installed spoke.
* Any application metadata that explicitly references components outside the application scope.

To remove a dependency, navigate to the application record and locate the Dependencies related list. Before deleting a dependency record, confirm that the application no longer references any components from that application or
plugin. Removing a required dependency causes errors on instances where the supporting component is not installed.