The State Editor is used to control what actions should be taken if an operation or transition is started, or in the event of entering or leaving a state.
The State Editor is divided into three re-sizable columns:
At any time, you can click "Cancel" to discard your changes.
A State denotes the status of a specification.
Each specification flow must have the following:
A Running State indicates that the user forms will be loaded into the specification window or browser for the users to enter data onto.
A Paused State indicates the specification is held in a queue, available for selection from the specification explorer.
An Automatic State indicates the specification is controlled by DriveWorks Autopilot.
When a task is selected, its properties are shown in the property grid.
Each one has a green or a gray orb next to the property name. A gray orb means that the property has a static value, and a green orb means that the property's value is based on a rule. To switch a property between static or rules-based, double click the orb next to the property name.
To build a static value, type the value into the box next to the property name in the property grid.
To build a rule, click the property name in the property grid, and then click the ellipsis "..." button that appears to launch the rule builder.
A task can have conditions assigned to it. If any of the conditions fails, then the task won't be run.
To launch the Condition Editor, right click the task and click "Edit Conditions".
Operations and Transitions can have conditions assigned to them. A condition that fails can either hide or disable the associated operation or transition.
To launch the Condition Editor, right click the Operation or Transition and click "Edit Conditions".
Operations and Transitions can have team permissions assigned to them so that only certain teams can use them.
To launch the Teams Editor, right click the Operation or Transition and click "Edit Teams".