How to keep up with Plugin maintenance

Matthew Hinton
Tera Contributor

We have quite a few plug-ins (~175) in our Washington, DC instance.  There's not a sort plugin by update available in application manager.  It can be time-consuming keeping them all up-to-date.   This even scheduling the installation.  How is everyone keeping up with updating their plugins? 

1 ACCEPTED SOLUTION

Dr Atul G- LNG
Tera Patron
Tera Patron

Hi @Matthew Hinton 

 

 

https://www.servicenow.com/community/developer-forum/best-practice-for-updating-plugins/m-p/3143381/...

 

 

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************

View solution in original post

10 REPLIES 10

No problem at all, I'll try my best as it's been a while...it's a pretty crude approach now that I'm thinking about it.  

 

Main Table

  • Each instance is represented as a dictionary 
  • Reference dictionary for the Store Application table
  • Styles are used for the color-coating (modern cell coloring is enabled, but it can be disabled to have the color coating more pronounced)

Product Table

  • Multiple reference dictionaries to the sys_user table to represent various contacts (PM, Tech Lead, Architect, ...)
  • Choice-list dictionary to specify the category (ITSM, ITAM, ITOM, ...)
  • List dictionary to serve as a watch-list for users who are interested in receiving updates (ITSM user who may be interested in ITOM apps)

When records are inserted to the Main table, business rules are triggered to execute REST calls to get the installed version on each instance.  This allows you to view versioning information from one UI (for all configured instances) instead of having to login to each and check manually.  

 

Scheduled job runs daily to update each record.  Our user base is aware the information displayed is up-to-date as of the start of their working day. 

 

Weekly scheduled job runs to send notifications to those designated by the associated with Product record.  This allows only those who are interested to be notified of updates for applications within their workstream.

 

One of the drawbacks is where the information is queried.  Only the Store Application is queried at the moment and I would like to also query plugins as well, something on my to-do list as time becomes available.  

 

I hope that provides some insight.  I am always welcoming feedback along with any suggestions/new ideas others may have to improve on the functionality.