Template versioning enables the monitoring and continuation of contracts and contract data over time. It is safe and versatile, preserving older data while facilitating changes and planned rollouts.
When versioning is applied to a template, changes to building blocks and questions are tracked from version to version. This permits contracts based on older versions of a template to be updated to the newest version with just a few clicks, while alerting the user to any questions that may need answering again (and ignoring any that remain unchanged). At the same time, if a user decides not to update an existing contract, it will not be affected in any way. Previously generated documents will not be affected, either.
All versions are collected under and managed from the same template, so there’s no proliferation of separate templates to account for each iteration. Whenever a new version is initially created, however, it will appear as a separate template to users who have been granted testing rights in Weagree. They will be able to try it out while it is still under construction. It will not be accessible in any way for other users. Once the new version is ready for production, the admin can publish it. Older versions are kept in the database intact, but it will only be possible to create new contracts with the latest published version.
