- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
23m ago
We are currently considering using a third-party ServiceNow plugin from Device42. There has been some concern that an older plugin might stop working if ServiceNow is upgraded to a version that the plugin does not yet officially support.
Is that actually the case? It doesn’t seem entirely logical to me.
For example, our environment is currently running ServiceNow Australia Patch 2, and it was previously on the Zurich release. The Device42 plugin was installed when we were on Zurich, but it has not yet been officially updated to support Australia. (I see that Device42 plugin does support Australia, but that's not my question here)
Wouldn’t the plugin still function even without official support for Australia, assuming there are no breaking changes?
Plugin: Device42 - ServiceNow Store
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
16m ago
Everything should still work with upgrading, unless it is depending on ServiceNow functionality that is removed. But that rarely happens.
If the app wasn't Australia supported yet, you couldn't install it on an Australia version, but once you have it, it will work.
There is one big thing to realize: it could be that newly added config causes issues and you need to update stuff in the app. If it's all secure, you may not be able to do so, and need the supplier for that. ServiceNow updated Flow Designer to v2 a couple of versions back. If the app runs on v1 and has some actions/scripts that return nothing because of stricter handling of v2, the workaround would be moving your instance back to v1, until the vendor updates the app. If they stopped development (so no new versions), your app will stop working, unless you keep your instance on v1 and I don't recommend that.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
16m ago
Everything should still work with upgrading, unless it is depending on ServiceNow functionality that is removed. But that rarely happens.
If the app wasn't Australia supported yet, you couldn't install it on an Australia version, but once you have it, it will work.
There is one big thing to realize: it could be that newly added config causes issues and you need to update stuff in the app. If it's all secure, you may not be able to do so, and need the supplier for that. ServiceNow updated Flow Designer to v2 a couple of versions back. If the app runs on v1 and has some actions/scripts that return nothing because of stricter handling of v2, the workaround would be moving your instance back to v1, until the vendor updates the app. If they stopped development (so no new versions), your app will stop working, unless you keep your instance on v1 and I don't recommend that.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
7m ago
Hi Mark and thanks for posting back on a short notice!
Basically you say what I was assuming - the Plugin will still run. This plugin is used for CMDB and since those tables have been around for a long time, I don't see that it will cause any major issues. Not to say that it can, but yeah...
