Process rules provide more control over files that are added or checked into StarTeam. Administrators can ensure that every file is linked to a process item (a change request, requirement, or task). The idea is that the process item provides information about why this file needs a place in your project or needs to be changed.
In StarTeam, you can use process rules even when they are not enforced at the project level. However, if you want the Integration to request the selection of a process item when you place files under version control, process rules must be enforced for the project.
Using process items enables users to clearly distinguish the file revisions that meet or complete a specific change request, requirement, or task. Having this information makes checking the files out for a build much easier.
No process rules are set by default before you create a project from your development application. If you want to use process rules, you must decide whether to add the files from the development application’s workspace or project before or after setting process rules. If you add files:
If you are adding a workspace or project to an existing project, process rules may already be enforced. In this case, you need to create the appropriate process items before you add files or turn off the process rules until the files are added.
If others are working on files already in the project, turning off the rules, even momentarily, may be impossible. In this situation, make sure you have added at least one appropriate change request, requirement, or task to the StarTeam project. For example, you might create a change request with Add workspace to StarTeam as its synopsis.