Configuration of a Workflow
In aqua you can create a workflow for your specific project. To configure the workflow for the status, open the Workflow configuration.
As the Workflow Designer is now open, click on the Defects tab in order to specify the workflow for defects. Activate a workflow by clicking on Use Workflow button in Workflow panel in the ribbon bar.
When creating a new defect, we want it to have the initial status New. This is the transition between the nodes <Create> and New.
When, for example, a programmer starts fixing the cause of the defect, the only next possible status for the defect should be In Progress. In order to configure this dependency you need to create the transition between the nodes New and In Progress. To do this, slide the mouse over the middle of the New node, when the mouse cursor changes to a hand and the box is getting highlighted, press and hold the left mouse button, drag the arrow to the In Progress node and release the mouse button.
1. Activate a workflow by clicking on the Use Workflow button in the ribbon bar.
2. Initiate the transition between the nodes <Create> and New for the default status value.
3. Create a transition between the two nodes.
Configure all transitions between the status nodes. This is how the complete workflow for defects can look like:
The following types of limitations are possible: Global Limitations, which are defined for the whole workflow, Action Limitations for the transitions between the status nodes, and last but not least Status Limitations for a particular status.
To create a Global Limitation, make sure that no vertices are selected which is the case if there is written Selection: none (global) and click Add. A dialogue will open where you can define your limitation.
After clicking OK, the new limitation is added in the table of the area Global for the global scope. The table has the following five columns: Scope, Field Name, Condition, Attribute and Details.
|
Scope:
|
Describes the extent of the area for the limitation.
|
|
Field:
|
Specifies the field for which the limitation is applied.
|
|
Condition:
|
Defines a particular user role for which the limitation should apply.
|
|
Attribute:
|
Determines a property for the field for which the limitation should apply.
· Hidden - the field cannot be seen.
· Editable - the field can be edited.
· Default Value - sets a default value for the field.
· Highlight - highlights the field as outstanding and sets its background color to yellow.
· Required - makes the field compulsory and sets its background color to red.
· Value – differs depending on the type of the selected field in column Field.
|
|
Details:
|
Depends on the type of the selected field in the column Field and the selected value in the column Attribute.
|
Note: No limitations are possible for fields of type Text, as this is a type for rich texts.
Next, we want to configure the newly created Global Limitation for a particular use. We want to achieve that the field Name is required when creating a defect, for example. Click in the limitations table on Modify.
Click in the field dropdown and choose Name from the list of existing fields. To make the Name field required select Required from the Attribute dropdown. Select the Is True checkbox and For any role.
To create an Action Limitation for a particular conjunction, click on the transition arrow. We want that the field Assigned to, automatically resets its value to the user, which changes the Status of the defect to Closed. In order to do so, click on the arrow between the nodes Solved and Closed and press the Add button. The new limitation is added in the Limitations table under Action: Solved to Closed.
Click in the field dropdown and choose Assigned to from the list of the existing fields. To set the value of the field, select Value on the Attribute dropdown. In this case we want to setup the user who will change the value of status, so check Current user.
