Skip to Content (Press Enter)
Back to Ideas
23
Like
Follow Idea
Configure and Application as Not For Production
457Views
13Comments
New
Lifetime

Some application are built specifically for development purposes (SQL Sandbox, impersonate pages etc..) and It would be useful to have a setting which could designate an application as Not For Production to avoid having them deployed into a production environment.

This could be a configured on the application level.

16 Feb 2021
Copy link to comment
17 Feb 2021
Copy link to comment

Yes, it can also be done with a UI flow as well where all the screens under that flow should be avoided when making a publishing to other environment..

17 Feb 2021
Copy link to comment

Hi Deepti, Sorry I fail to understand your comments, in relation to the link I shared.

17 Feb 2021
Copy link to comment
Merged this idea with 'Prevent deployment of certain apps to production environment' (created on 02 Mar 2021 14:53:24 by Bas de Jong)
03 Mar 2021
Copy link to comment

Hi,


It would be useful to mark certain applications to make it unable to deploy them to production for anyone, for example separate TEST applications of OutSystems UI Templates, Architecture Dashboard probes etcetera.



This comment was:
- originally posted on idea 'Prevent deployment of certain apps to production environment' (created on 02 Mar 2021 by Bas de Jong)
- merged to idea 'Configure and Application as Not For Production' on 03 Mar 2021 08:10:27 by Daniël Kuhlmann
02 Mar 2021
Copy link to comment

Good idea, but it already exits, so I merge it.



This comment was:
- originally posted on idea 'Prevent deployment of certain apps to production environment' (created on 02 Mar 2021 by Bas de Jong)
- merged to idea 'Configure and Application as Not For Production' on 03 Mar 2021 08:10:27 by Daniël Kuhlmann
03 Mar 2021
Copy link to comment
Changed the category to
Lifetime
10 Jun 2021
Copy link to comment

Applications can be grouped into Teams in LifeTime.

You can define a Team in LifeTime for applications that should only exist in DEV and control the permissions of the Users of that Team so that they cannot deploy it to other environments.

This could be a way to achieve the intended goal of the idea with already existing tools/features.

--Tiago Bernardo

24 Oct 2022
Copy link to comment

I think the same as this older idea (19 Jan 2021):

https://www.outsystems.com/ideas/10102/lock-an-application-to-prevent-it-from-deployment/

--Tiago Bernardo

24 Oct 2022
Copy link to comment
Merged this idea with 'Mark application as testing App which should not be deployed to Prod' (created on 25 Nov 2022 04:54:57 by Mostafa Othman)
27 Nov 2022
Copy link to comment

I would like to suggest to have an option while creating a new application on service studio to mark this application as testing application which I do not want to deploy it to higher environments (for example do not want to deploy it to production).

While I am creating a deployment plan in Lifetime I can see these application marked for testing grouped together under one expandable tab and not mixed with other applications that existing into my environment.

I see this may be helpful especially for environments which contains high number of applications and many developers to save time while creating deployment plan and decrease opportunity of deploying unwanted or testing applications by mistake to higher environments.

25 Nov 2022
Copy link to comment
Merged this idea with 'Set an application as "Not deployable to other environments using Lifetime"' (created on 13 Dec 2022 10:11:35 by Pedro Ramalho)
15 Dec 2022
Copy link to comment

When are we preparing a deploy and we have access to all applications, there are always applications that we don't want to deploy to other environments but they always show in the list available to be deploy. 

It would help a lot if by application, and in Service Center, we had the option "Not deployable to other environments using Lifetime" available.

If I set that option to True, then it would not appear in the applications available to be deployed to other environments.

13 Dec 2022
Copy link to comment

That would be ideal for our developer backoffice and test backoffice (on test)

14 Dec 2022
Copy link to comment