Hi,


We have made a version of our and deployeed it to TestFlight successfully. Then tagged the app in Outsystems with a new version nr, to continue making changes. But we then noticed that the changes we are making are still affecting the app that was already deployeed to testflight (old version). How is this possible? We cannot proceed with development if we cannot isolate one version of the app and continue to the next. Documentation mantions using Quality Assurance, we cannot find this anywhere.

What is the best practice managing app versions with the Personal Environment?

Hi Eric,

You built a version and tagged it.That's fine, but are you building or updating the app on same environment (you did mention personal environment).

The stable version should go to another (staging/production) environment and further development must happen on development environment. 

If one has only one environment, then you can not segregate the releases. OutSystesm works on concept of Continuous Deployment.

Personal Environment comes with environment for building non-production apps. Every single push will overwrite the last deployed release

Read more about Personal Environments.

https://success.outsystems.com/Support/Personal_Environment/What's_an_OutSystems_personal_environment%3F

 "Personal environments are configured for you to learn, experiment, or prototype apps at your own pace". Not for production!


Solution

I don't have great news for you. If you are developing in Personal Environment, you can't expect the full experience of OS best practices. This is a free space for single developers to try functionalities but has a lot of limitations. It is not for teams to manage projects.

In Personal Environment you have a single server. The only way of having an isolated deployment is if you do it to Personal Area (web applications). And even those still share database so are not ideal.

That version number is for your guidance. Without Lifetime, there is no way to control versions. A possible trick is to clone the app and work in two separate modules, but then the DB is different...

Solution

As i suspected 

Thank you both for your answers!