Why are plugin dependencies different between my instances?

Joshua Berger
Tera Expert

I am trying to activate com.snc.knowledge_advanced.installer plugin, to have the article version and template features.  I have tested this in one instance without issue. When I try to activate it in another instance the dependencies are different. Now it will not let me activate without the com.glide.localization_framework pluggin, translation features I don't want. I have confirmed in the first instance com.snc.knowledge_advanced.installer is active and the article version and template features function, and the com.glide.localization_framework plugin is inactive. 

 

Is there a way to install and ignore plugin decencies? Why can I do this in one instance and not the other? 

2 ACCEPTED SOLUTIONS

I think this warrants opening up a support case with ServiceNow.

View solution in original post

Update for anyone else running into this problem: 

We just activated the plugin through the 'automation store' on the Now Support page. The unwanted plugin dependency was not activated, and the plugin I wanted activated successfully. 

View solution in original post

5 REPLIES 5

Nice, thanks for the update.