Service Studio Delete button is too permanent
255
Views
6
Comments
New
Service Studio

Service Studio Delete button is too permanent

 

Is there a way to restrict the use of the Delete key in Service Studio?.  We are finding that if we accidentally click on the Delete key, there is no way to undo the delete, and therefore no way to recover the app. We would prefer if the delete key would mark the app as 'removed' like the recycle bin - then the developer can recover the app if necessary.

 

This is the original issue as reported to us.

 

 This is the screenshot of other application (this button is the same for all applications as I can see). Regarding the app I removed yesterday, I cannot remember the name and the version of it. I think it was something like "test_app_please_remove_it". But it certainly contained word "remove".  So, if you plan to try to restore it then you can search it by this word. And the funniest thing about this button is that I expected that when I press this button then I get alerting popup like that: "Are you sure that you want to remove this app. Yes. No. Cancel". But this button removes an app immediately. So, one misclick can turn several years of our work into nothing 

Here is the screenshot of the button:

Afaik, 

this only deletes without further warning if there are no modules inside the application.  

So not much work other than choosing a name is lost.

Dorine

Thanks. Im still thinking a soft delete would be a safe option (if there are modules).

If you delete the app with modules (after you confirmed you really wanted to delete it!) then still you can recover any version of each module from the systems tables. You can use this Forge component for it: https://www.outsystems.com/forge/component-overview/8187/recovery-modules

Outsystems also needs to improve how applications are automatically deleted and who has access to delete them.  We have had an ongoing issue for some time where Outsystems is randomly deleting an application that shouldn't be deleted.  Then we go through an extensive restore process and another support case to try an get it fixed.

Note: We tried the recovery-modules forge component to restore it but it really didn't help us much.

Hi Rebecca, for the problem you mention I think you should create a support case, your comment here will not get a lot of tracking to get it fixed.