Removing unnecessary Application dependencies

jeremy_gardner
Tera Expert

‎04-14-2015 06:49 PM

While building my scoped application, I created some forms and fields on the cmdb_ci table, as well as some catalog items and workflow (all within my application scope).   I no longer needed them, and deleted them all, however the Application Dependencies still lists Configuration Management and Workflow Runtime Engine.

1.   Do these get removed automatically if I remove the items that created the dependency in the first place?

2.   If not, can I remove them manually?

3.   If I have a reference field to the CMDB on a scoped table, would it still require the Configuration Management dependency?   I wouldn't think so, I have reference fields to other system tables in my app and don't see anything listed for them.

Thanks!

Jeremy

0 Helpfuls
  • 1,068 Views
1 REPLY 1

BobbyNow
ServiceNow Employee
ServiceNow Employee

‎05-18-2015 09:46 AM

#1 We only add the dependencies, we do not remove them.



#2 You may manually remove them if you know you have removed all artifacts that would have caused the dependency.



#3 Yes, creating a field on a configuration table is a dependency on configuration.


0 Helpfuls