Keeping processes that generate new versions in one state
Article ID: 40151
Updated On:
Products
Issue/Introduction
There are processes that you can create within the states of your Harvest project that result in the creation of a new version of a folder or file. These are:
- check in
- checkout for update
- rename item
- rename path
- move item
- move path
- remove item
- remove path
- concurrent merge
- interactive merge
- cross-project merge
The rule for new versions in Harvest is that they are only visible and accessible in the states and data views where they were added and in the states and data views to which they have been promoted. For example,
Suppose our project has three states - Development, Test, and Production.
In our example scenario, the testing team has found a problem, checked out a file for update from the Test state, fixed the problem and checked it in. After this, someone from the development team tries to check out the same file and gets an error message that a later version exists, even though it is not visible or accessible from the Development state.
Environment
Harvest Software Change Manager all versions and platforms
Cause
Referring to the rule above, this has happened because the new version was created in the Test state and is not visible or accessible from the Development state.
Resolution
Strive to create the above-mentioned change management processes in a single state of your choice, preferably the first state. This will help to avoid the errors that result from having a higher version in a different state.
Additional Information
You can read more about how Harvest uses and manages versions here:
Feedback
