Uninstalling Applications

colint
Kilo Contributor

Hi Guys,

 

I am not having much luck with uninstalling a custom application.

 

Background:

I created a custom application and published it to an update set. I than installed it on another instance by applying the update set.

 

To uninstall the application I attempted backing out the update set, however I got the error message Data Policy Exception: Name is mandatory.

 

The update set has been marked as backed out however the tables etc are still present in the test instance.

 

Questions:

Is this the right way to 'uninstall' an application?

 

I would have expected that backing out an update set would result in the system being returned to its previous state.

 

Experimented:

So being the curious person I am I tried deleting all the stuff which should have been deleted manually via the tables table etc however the update set now has issues when I try to apply it again. Something about duplicate tables. But I already deleted it.......

 

Any thoughts?

 

Thanks in advance,

Colin

1 ACCEPTED SOLUTION

robpickering
ServiceNow Employee
ServiceNow Employee

I would probably add:


  • If you need to make changes, make a new update set to apply those changes.
  • If you wish to re-publish an Application, you can, you just need to go to System Applications > Custom Applications, open your custom application on your development system, click "Publish to Update Set", then promote that update set to your Production Instance

View solution in original post

9 REPLIES 9

Bhavesh Jain1
Giga Guru

Did you try deleting the Application by clicking on Delete button on the Application form?


So deleting does get rid of the application, this is good.



Unfortunately the update set is still present which means that if we decide we do want the application after all we will not be able to reapply it... and we can't really undelete an application....


robpickering
ServiceNow Employee
ServiceNow Employee

As a "Best Practice" you shouldn't back Update Sets out, due to these types of conflicts that may happen later.   You should just create a new update set in your Development instance that corrects the issues you experienced, and then apply that one to Production.


adding to above note.



In my experience, I did not have much luck in reversing the "update set". As Rob suggested above; the best strategy may be to fix the issue in development such as disable/delete business rules, applications and etc and move the update set.



That is how I have handled it previously.



Hope it helps, thanks, Faisal