Activate and Configure Plugin Best Practices

[tompham]

What is the general best practice for activating and configuring a plugin in ServiceNow.   I've read the following: https://community.servicenow.com/community/blogs/blog/2017/03/06/how-do-you-plug-in-a-plugin-the-ins....   However, it does not provide a high level best practice on the general process.  

For example, our organization has two environments (Prod and SubProd).   If we wanted to activate and configure a plugin such as Change Management or PPM.   What is the best practice for performing this operation.   Would we need to activate the plugins first in both instance, then perform configuration on subprod, then prod? What is the general best practice for this type of work?

Thank you.      

[Allen Andreas]

I haven't read through each and every word of what people have said but first and foremost...this needs to be the thought process...

Per my SN account manager who I just spoke to the other day about something close to this question...

He said that SN allows ALL plugins to be activated on the Dev instance (although I see them on the Prod too, so he may not be telling to full truth here - but the gist remains the same)...

So...even though they are there....IF you choose to activate them, and then somehow it carries over to your production instance where the agents/users/etc. COUNT against your contract... they will bill you.

So his best practice before activating any plugin that seems out of the ordinary for you, is to reach out to your SN account manager, explain what you're trying to do and what specific plugins (parent and child or dependency plugins) are needed. He/she can then check in to it and let you know for sure.

So before you activate anything, that would be the best guidance I can give.

THEN....it all depends if you're cloning dev to prob...or import setting etc....to the other instance.

Activate on Dev, configure, mess around (to an extent) and then see about replicating in prod.