Branching copies an item (file/folder) from one location to another. After branching, the item and its counterparts will be independent, and changes made to the item will not be reflected elsewhere. You can use Merge to merge the branches back.
SCM Anywhere supports file branch and folder branch.
The SCM Anywhere Branch command makes an item able to be part of separate projects. Here are two common scenarios in which you need Branch :
1. Suppose that after releasing Version 3.0, the R&D team starts working toward the next major release, the 4.0 version with some new features and functions. In this case, you can branch all files in the project $/Project3 into a new project $/Project4. If the users of Version 3.0 find bugs or need minor features implemented, you may need to work out a minor version, say, Version 3.1. Here is what you may try: Create a new project named $/PATCH to store the 3.1 version, and branch all the files in $/Project3 to $/PATCH. Some developers can fix bugs and implement minor features in the PATCH project while the other team members stay on the 4.0 version development.
(Branch scenario 1)
2. Suppose that you are working on two projects which are virtually identical for two clients. You just need to tailor program behavior in one or two files. You can create a project $/CLIENT1 and branch the whole project to a new project $/CLIENT2 recursively. Now, when you modify these specific files in $/CLIENT2, the changes do not propagate to $/CLIENT1.
How to Branch
Branch command allows you to branch the latest version or any history version of an item. Check the online manual on how to branch:
How to Track Different Branches
You can track the different branches of an item by right-clicking on either of the branches, and then clicking Properties -> Branches tab.
After the file branches are modified in different projects separately, you can bring them back together using the Merge command. To learn more details, please refer to another article File Merge.
SCM Anywhere also supports Folder Merge.