DriveWorks Pro 15: State Editor [send feedback...]

State Editor

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:

  • The State Items column shows the events, operations, and transitions that belong to the state.
  • The Task Sequence column shows the tasks that have been setup for the selected event, operation, or transition.
  • The Toolbox column shows a searchable list of tasks that can be added to the task sequence for the selected event, operation, or transition. The properties for the currently selected task are shown below the toolbox.

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:

  • At least one Running State
  • At least one Paused state
  • One state that is the Initial state.
State TypeExampleNotes
Running

A Running State indicates that the user forms will be loaded into the specification window or browser for the users to enter data onto.

Paused

A Paused State indicates the specification is held in a queue, available for selection from the specification explorer.

Automatic

An Automatic State indicates the specification is controlled by DriveWorks Autopilot.

To Add a Task to a Task Sequence

  1. Select the event, operation, or transition to which to add the task.
  2. Drag the task to add from the toolbox to the task sequence.
  3. Configure the task's properties in the property grid.

To Reorder a Task in a Task Sequence

  1. Select the task to reorder.
  2. Click the "Move Up"/"Move Down" buttons to move the task up or down.

To Remove a Task from a Task Sequence

  1. Select the task to remove.
  2. Click the "Remove Task".

To Edit Properties for a Task

When a task is selected, its properties are shown in the property grid.

All tasks have a "Title" property which can be used to give the task a descriptive name. Depending on the type of task, there may be extra properties.

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.

If you build a rule for property, then DriveWorks needs to have the project open to calculate it, which means even if the specification is going from one Paused state to another, DriveWorks will open the project and then close it again which may affect the performance of the project, particularly with Excel Projects.

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.

For help with a specific condition, see the Toolbox help topic.

To Edit Conditions for a Task

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".

To Edit Conditions for an Operation or Transition

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".

To Edit Teams for an Operation or Transition

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".

Table of Contents