Skip to main content


Managing the Applications Lifecycle



Early Access - Configure Application Settings During Deployment

Read how early access to OutSystems features works. We encourage you to try these features out and to send us your feedback.

This early access feature adds a new step during the deployment plan to define application settings in the target environment. With this feature disabled, when you deploy an application with a setting that must be different in the target environment, you need to use the Service Center console to update it in the target environment after deployment.

To use this feature, make sure that:

  • LifeTime is Release Jul.2019 or later and both the source and target environments for the deployment are running Platform Server 11 Release Jul.2019 CP1 or later.
  • The feature is enabled in LifeTime.
  • The user executing the deployment has the "Change & Deploy Applications" permission for all applications in the deployment plan.
  • For applications using extensions to integrate with external databases, you created the extensions while connected to an environment running Platform Server 11 Release Jul.2019 CP1 or later. Otherwise, republish the extension in Integration Studio while connected to an environment running Platform Server 11 Release Jul.2019 CP1 or later.

After activating the early access feature Configure Site Properties and Entities from external databases during deployment, a new deployment plan wizard will be used when deploying applications in LifeTime. This wizard has four steps:

  1. Add the applications to deploy
  2. Configure application settings
  3. Review deployment plan
  4. Execute deployment plan

While you are already familiar with the other steps, during the step Configure application settings you can now configure the settings in the target environment of the applications being deployed, as described below.

Configure application settings

After adding the applications to your deployment plan, you now have a new step to configure the settings of the applications being deployed. For now, it is possible to configure the following settings:

  • The Site Properties of the application modules

  • The Entities from external databases

  • The Deployment Zone for the applications being deployed, when the target environment has more than one Deployment Zone

The deployment plan wizard includes this step when there are new settings to configure:

  • There are application modules in the plan with new settings that were never defined in the target environment. In this step, you can define the effective value for those settings in the target environment.

  • There are application modules using Deployment Zones, and the corresponding applications will be deployed to the target environment for the first time. In this step, you can choose the deployment zone to which your application will be deployed.

Select an application from the list of applications to review to define the settings for that application.

You can also review and change the existing settings of the applications to deploy. Click the button All settings to see the existing settings.

If your deployment plan contains applications with no changes, you will not be able to change the settings for those applications.

There are some situations when this step is skipped or disabled:

  • The step will be skipped when there are no new settings to configure. However, if you need to change any existing setting, you can manually go back to Configure application settings by clicking the step in the wizard.

  • The step will be disabled when there aren't any settings to configure or the user executing the deployment does not have the required permissions.

Since the Site Properties of the applications to deploy are set in the target environment only after the applications are published, beware of Timers running When Published because the value of the Site Properties they may use will not be updated yet.

This feature does not apply to multi-tenant Site Properties.

  • Was this article helpful?