Harvest SCM Best Practice: When defining your SCM project lifecycle, you should only create processes that will generate a new version of an item or path (Check In, Check Out, etc) within one state in the project
Article ID: 40151
Updated On:
Products
Issue/Introduction
Summary:
Harvest Administrators should only create change management processes that generate new versions of items within a single change management state. This is a best practice to follow to prevent Harvest users from running into errors with checking out items because a later versions exists somewhere in the project.
Background:
Many customers have reported that they have created processes within more than one state in their project that can result in new versions of files and folders This is problematic because a check out for update will result in an error if a higher version of the file exists in another state. The best practice is to create processes that generate new versions only within the first state of your project, for example the Development state. This will prevent Harvest users from running into errors with checking out items because a later version is available.
Environment:
All supported Harvest environments
Instructions:
Avoid creating the following change management processes in any state besides a single state of your choice. The best practice is to create these processes within the first state:
"check in", "checkout for update", "rename item", "rename path", "move item", "move path", "remove item", and "remove path", "concurrent merge", "interactive merge", "cross-project merge"
If you are a Harvest Administrator and have already created these processes in states other than the single state (i.e Development) according to this best practice, then we advise that you delete these processes from all states except for the first state. You may need to create these processes and set the execute permission for the appropriate Developer users in case these do not already exist in the first state.
Environment
Component:
Feedback
