How do OutSystems applications handle versioning?

OutSystems applications manage versioning primarily through the use of LifeTime, which is an essential feature in the OutSystems platform. LifeTime allows developers to maintain multiple versions of applications, enabling an organized management of changes, updates, and deployments. This capability is particularly valuable for enterprise-level applications where maintaining stability while progressing with new features is critical.

When a new version of an application is created, the old versions are not simply deleted. Instead, they are kept in LifeTime, allowing developers to roll back to a previous version if necessary. This historical context ensures a reliable environment where updates can be tested in isolation before being made available to users, promoting a more controlled deployment process.

The other choices do not reflect the standard versioning practices of OutSystems. While creating backups of the database is a good practice for data recovery, it does not pertain to the version management of applications themselves. Utilizing Git can support version control for code, but OutSystems has its built-in capabilities for managing application versions through LifeTime, rendering external version control systems redundant for application versioning. Lastly, simply deleting outdated versions would not provide the flexibility and safety necessary in application development, particularly in environments needing rigorous change management. Thus, LifeTime’s approach to managing multiple versions provides