Hi all,

We wanted to disable an application in production. There's a "disable" button in service center:


When pressing this button, service center gives the notification that the application is now disabled and all modules show a warning as well which seems to be the expected result.
The problem is that when we try to access the application, it is still accessible as before. Nothing changed.

Anyone know how to really disable an application?

We tried this in development, test and production environment [cloud] and it was all the same.  

Thanks in advance,

Wietse

Solution

Hi Wietse. You can publish the application, and it will become disabled.

Publishing should not be necessary, but I believe there was a recent bug that is now requiring a publish for the disable to take effect. Hopefully this will get fixed soon :)

Solution

leonardo.fernandes wrote:

Hi Wietse. You can publish the application, and it will become disabled.

Publishing should not be necessary, but I believe there was a recent bug that is now requiring a publish for the disable to take effect. Hopefully this will get fixed soon :)

Hi Leonardo,

That did the trick. Thank you!


Hey Leonardo!

I've stumble upon this issue. I need to disable an aplication in runtime(it's a webapp to do migrations and i need to disable the source and destination app before doing the migration), so i've used the system table ossys_aplication to disable it and i've faced the same problem has mentioned here, but the option to publish is not possible in my scenario. 

Basically i need to disable the application and do an IIS reset. Any ideia how to?

Hi Nuno. That's a different scenario than what this thread talks about.

You can try executing the EspaceInvalidateCache system action for all eSpaces inside the application.