A nice improvement on site properties would have the capability to configure the default value for each environment before we actually deploy them. It would be nice this be configurated on Lifetime.

Hi Franco,

Thank you for posting your idea!

Is your idea some like related to this one? 

https://www.outsystems.com/ideas/5032/LifeTime+-+Defining+Configuration+during+Deployment+Planning

Cheers

In LifeTime:

It would be nice to see a reminder (warning message) to fill/change a newly deployed site property value, after a deployment. So this would be the first time that site property gets deployed to a new environment. 

This would be especially important when the site property is getting deployed to Production for the first time.

Agree. Maybe even an email notification to some group. I had this problem so many times, when we forgot to change a site property or integration effective url. 

Yes Roman. I’ve also had this problem a lot of times.

As mather of fact, just last week we deployed a fairly large application to production for a client and we forgot to set a couple of site property values which caused a lot of unnecessary problems.

I think LT having this feature would have saved us the headaches!

Maybe these settings should be part of the deployment plan; now you can create a note for changing webservices, rest endpoints, site-properties and timers. 

Would be useful to add suggested values for all these settings for the next environment; that could be overwritten by the Operator that performs the publish.

I like the idea of Matthias,  a warning is nice, but what really is needed is the option to configured all this in your deployment plan, and that during deployment LifeTime will configure the settings in the target environment.

This makes even more sense if your organisation uses for example Jenkins for kicking of deployments in OutSystems.

Hi all,

I can understand the question but then more in general that the property needs to be changed, not because of the default value.

I teach everybody that when you'll create an site property it's default value needs to be the value on production so you'll never have an issue with it.

Adding it to the notes is fine, but if a timer is depending on it which is running on publish you're still to late to adjust it...

Kind regards,
Evert

Allow to change the effective value of new site properties, endpoints and timers during staging proces.

Often these values are different per environment. It would be helpful to have the same kind of warning for configuration as with a new database connection. So it has the correct value when the application is online and it is not forgotten during the staging process.

Hello Community,

I want to suggest that during the creation of the deployment plan in Lifetime, we should be able to configure the APIs consumed and exposed in an approach similar to the Site Properties.

Pros of this idea, if implemented:

• We removed an extra step in the post-deployment configurations;
• We do not need to open Module by Module in the Service Center to make this change at run time;
• If the Production Environment is managed by a different team, we will remove an external dependency;

I would like to receive some comments from you to improve the idea.

You could use Properties Manager for this? We worked on additional functionality to download a set of Properties from one environment and upload to another environment.

Hello Mathias,

In my current client, we can only install forge components that are trusted and/or OutSystems Supported.

From my point of view, this should be something integrated in Lifetime instead of exporting and importing in a different environment since, this way we always need to execute this step after deploy not during.

Thank you for your feedback and I will validate this component for other use cases.