- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi Team,
I am currently facing an issue related to a plugin upgrade and would appreciate your guidance.
In our Dev instance, I upgraded the Workflow Studio plugin. However, the update was accidentally captured in a custom application scope update set. Since the scopes are different, when the update set was migrated to the SIT instance, the plugin was upgraded successfully, but the dependent OOTB flows and related application artifacts were also moved to the custom application scope (Some subflows and flows specifically).
As a result, I am unable to uninstall or roll back the plugin changes. Could you please advise if there is a way to resolve this issue and restore the affected components to their correct scope?
Thank you very much for your assistance and response.
Regards,
Poorvi
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @pokulkarni ,
I tested this in my PDI and was able to roll back the Plugin installation successfully. When you click rollback could you please check if there is a checkbox called "Rollback App Installs" when performing the rollback?
If you select that option and proceed with the rollback, it should uninstall the plugin as well.
Thank you
Prajwal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @pokulkarni
We can't roll back or uninstall the plugins, as this is not something that ServiceNow (SN) recommends. please log a Now support case.
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/dratulgrover [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @Dr Atul G- LNG , Thanks for your response.
Will the Repair functionality on the plugins work in this case?
Or would it be preferable to validate that the dependent plugins were updated as part of the main plugin, and then recapture and promote those changes from the lower instance to the higher instance?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Repair you can try but i doubt i will work so better go for 2nd option -validate that the dependent plugins were updated as part of the main plugin
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/dratulgrover [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Okay, would you also happen to know what might have caused this issue?