Project versions
- Kairi Rosen
Overview
It is possible to save the current status of the project.
To work with the project, user needs to be in the Working version and to view historical information of the project user needs to look at previously saved versions. This can be seen followingly.
User is in the “Working version”:
User is in the confirmed version of 05.2024:
To see all versions press:
Creating a project version
To create a saved version user needs to be in “Working version” and press button “Confirm version”:
A popup opens where the user needs to select to which month he/she wishes to save the version (it is recceomended to save versions at least once per month). If the user wishes he/she can also add a comment about the saved version:
2 level project versioning
It is also possible to use 2 level project versioning. This means that it is possible for another role to review or approve the version that was saved by the first person.
By default the system works with 1 level project versioning. 2 level project versioning needs to be switched on by the company admin user from the admin menu.
Project versioning permissions
Following permissions can be added to different roles in the system. From these the “Review and approve budget versions in projects” is the permission for 2 level project version confirmation.
NB! The screenshot below is from the 2024 Rights manager. If your company has not received 2024 rights update please contact support@bauwise.com.
Overall logic
If the user views the project saved version then it is not possible to edit any data. Versions are used for saving historical data.
It is possible to save several different versions to one month.
It is possible to save a version to the month that was last saved or to later months. It is not possible to save a version to a month which is earlier than the latest saved version. Eg if there is a saved version in 05.2024 then it is not possible to save a version to 04.2024 or earlier month.