Entitled ServiceNow App - Management

[Andy Newman]

Hello,

I'm curious to know if there is a smart way of managing the updates to the Entitled ServiceNow Apps, of which there often seem to be high volumes of.

1. How do we all manage them?

2. Do we put them through the normal channels of testing, raise change records etc? 

3. What happens if we ignore them, will ServiceNow automatically update them at some point?

4. Is there a way to bulk update them, or do we do them one at a time?

5. After doing the updates, is there a way of identifying what changes were made?

To find what I'm looking at (using Next experience UI),  choose the the 'Admin' menu at the top. Inside there is the 'Admin Home' option - select this and scroll down to the 'Entitled ServiceNow apps'. Attached screenshot should help.

I realise the obvious answer to this is dependant on the type of organisation and appetite for risk etc - and I am all for best practice, of course.... but I'm looking for general consensus of how you all do this.

Look forward to your valuable input.

Thanks

Andy

[garyhouston]

Not sure if this is what you're looking for or not. We're on Utah so I don't think this is possible. I have the exact same question(s)! 

https://docs.servicenow.com/bundle/washingtondc-application-development/page/administer/integrationh...

[Andy Newman]

Hi garyhouston

thanks for posting - what I have been using is the Admin portal (next to 'Workspaces' on the Next experience menu), and using the 'Application Manager' in that to update the apps. 

However, we were thinking there should be some kind of control around the updates. What happens in reality is that we do updates for say 50 apps in our DEV instance, then we run a bunch of ATFs and if ok we go to update apps in UAT only to find that by this point there might now be 62 apps to update instead of the 50 we updated in DEV. I'm sure you see the problem.

For now we will just go forwards updating the apps and hope for the best.