Hello team,

Yes, this idea is very much needed. As sometimes we need to revert back the changes which are already deployed, but unable to revert the same using lifetime.

For example, if I have 3 servers and I am deploying modules from 2nd server to 3rd server. Later I realized there are some issues in 3rd server and it needs to revert back to older version.  In this case, this idea will help us. 

Hi Rajat, 

Thanks for your recognition, the team appreciates it!

Thanks for sharing the idea, I will rename it so that we can better understand the content.

Regards

Hi Joao,

Thank you for your reply. It's really needed by all developers.

Thanks,

Rajat Agrawal

Hi Joao,

This idea is really good and it will help all of us. Please can you implement this because my Team also facing this issue.

Thanks,

SA

This would be very useful, especially for change management. ie. if you deploy into production, and something goes wrong (perhaps because of a data issue you didn't expect in production), you can't easily rollback.

Right Nicolaas.. I agreed

it should be implemented ASAP, we are facing the same issue in the lifetime.

@Joao - Any update on this?

This idea is very good, infact will be very useful. I had faced an issue, once when i deployed to Prod and something went wrong with the current build, so I had published all the previous version espaces from Service center which is very time consuming . 

So if the above idea is implemented, then it will be really very helpful in terms of time and complexity.

Hi guys,

Thanks for your feedback, please keep doing it. It is very important for us to understand your reality on this so that we can better understand the investment here.

This is not on our roadmap, but we are keeping this on top of our radar so please let us know your feedback. 

Meanwhile, and in order to open the discussion, there is an article related to this from one of our MVPs and product documentation on how to Rollback to a Previous Version.

Please keep sharing your feedback.

Cheers, 

João Bento

Hi Joao,

This feature is very imp and needed by everyone. I saw documentation and that process is from service center. We are following that approach since Outsystems 9 but when Outsystems is growing so fast and demand is high then we also need to upgarde this features to fulfill everyone need. I really appreciate if you consider this feature in your list.

Thanks,

Rajat Agrawal

Normally (depending on the amount of dependencies), the easiest solution to rollback a deploy in LifeTime is just to redeploy a previous version, not needing to manually republish in Service Center the previous versions of the modules of the application.

Let's say you have a single application BackOffice.
In DEV you tag it with 1.0.0 and deploy it to TST.
Then you make some changes in DEV, tag it in DEV with 2.0.0 and deploy it to TST.
Soon after you realize that this version 2.0.0 has major problems and you need to revert to version 1.0.0. Just do a new deploy from DEV to TST and manually selecting version 1.0.0 for the version to be deployed.

At this point you will have version 2.0.0 in DEV and version 1.0.0 in TST. If you also want to revert the version in DEV to 1.0.0, the easiest solution is to do a deploy from TST to DEV and selecting version 1.0.0 for the deployment.

--Tiago Bernardo