In the past it was possible to enable inactive applications in IAM to be opened by admins. This allowed you as an admin to test a version during the deployment before enabling the version for all the end users.
It would be of great help to have such a feature again.
+23Hi Arjan,
Whilst it is understandable to view the application before releasing it to the public, the ability of viewing Inactive applications brings difficulties that were not present in the past. For example, we currently have System flows that do not run for inactive applications.
Some questions do arise. How should the authentication work inside this inactive application? Who, as in which role, should have access to this application? What should be done regarding System flows?
The alternative to this idea is to copy the old version of the application to the new one and removing all authentication, thereafter ensure that only selected users have access to the application. The application can be made active, but only the selected users have access. Would that suffice?
+23+14Hi Mark,
System flows should not run for inactive applications. And only users that are marked as root admin in IAM should be able to open inactive applications (perhaps you should be able to mark inactive applications as accessable.
The suggestion that you provided will not work. IAM does allow 2 active applications of the same project and database.
+23As long as the alias is not duplicated, it is possible to run multiple applications for the same model and database. I do think application managers should also have the option to open up this application too.
I'll open the idea for voting.
+23
+9Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.