Scoped application dependencies | When does a scoped application create dependency - Support and Troubleshooting

Scoped application dependencies | When does a scoped application create dependency Issue  Overview This article will help you to understand dependencies created within a scoped application and when are they created

Subject When developing a scoped app sometimes records get added to the Dependency tab (sys_package_dependency_m2m). A dependency is captured when

A table in another scope is extended from the custom scoped application A field is added to a table in another scope A section is added/modified for a table in another scope. Calling a script from the global scope should not create a dependency, but it should create an Application Cross-Scope Access record. Essentially, if you modify a table in another scope, it will create dependency Example Navigate to your scoped application. Create a table that extends 'cmdb_ci' Go back to your application from System Applications > Applications Scroll to the bottom, look for a related list for "Dependencies", You will see a dependency listed. Additional Information Dependencies for custom applications