TranslationThere are obviously some scenarios where archiving an app should allow the use of the application, can login, can do actions and emails are sent. Could be used if we're building out a new base EASYCommerce and an old archived version has a feature I want to see how it works and do some tests to generate logs.
And I know we dont delete applications because they can be so large that if it is accidentally done it could be a huge loss.
But there are situations where we should be able to turn things off and currently there is no way to.
If we make EASYCommerce, but it is used to make a copy and now we have EASYCommerce2, I dont want users to accidentally get confused and work in EASYCommerce (original). Since it was a copy, it would look the same and have exact same functionality aside from the changes made to EASYCommerce 2 (new).
I'm thinking when archiving you can choose to also disable.
Disabling an app should:
- Stop all batch jobs
- Not send emails
- Show some default page kind of like what IIS does if you turn off a site
- Not process API requests.
- Show a banner or label in the IDE when in the app to show its Archived and Disabled