As described in Creating and Managing Workflows on page 134, a workflow takes effect as soon as it is activated. You activate a workflow by defining one or more conditions an issue must meet in order to be subject to the workflow. Typically, a workflow condition is based on a specific issue type—defect, enhancement, and so on.There might be occasions in which you want to suspend the workflow—as the administrator, you might want to be able to manually update a field that your workflow has defined as read-only, for example. There are two ways to suspend a workflow:Tip: Consider creating an Admin group for this purpose if one does not exist already.See Activating a Workflow: Defining Workflow Conditions on page 135 if you need help with this step.
4. Click the Save button () to save your changes to the workflow.
1. Open the workflow and click the Conditions button on the Workflow Editor toolbar to display the Set Workflow Conditions dialog box.
3. Click the Save button () to save your changes to the workflow.
4. Click No to save the workflow without any conditions.Note: At this point, workflow rules are no longer in force in AccuRev.
5. Using the Stage Generator is the quickest way to set up basic validation actions that are keyed off the field you have chosen as the basis for your workflow stages. For example, if you are using the Status field for your workflow stages, AccuRev automatically sets the setFieldPermission validation action to auto for that field.You can manually specify other validation actions for individual stages in the Workflow Editor, but if you identify the need to define the same validation action for every stage in your workflow—making the Severity field required, for example—consider specifying that setting using the Validation tab in the Schema Editor in the AccuRev Java GUI.
Borland |