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

Condition Editor

The Condition Editor can be used to control whether specific tasks in a task sequence are executed, or whether a specification flow operation or transition is hidden or disabled.

The Condition Editor is divided into two re-sizable columns:

  • The Conditions column shows the conditions that have been setup for the task, operation, or transition.
  • The  Toolbox column shows a searchable list of toolbox items that can be added to the condition column to become a condition in a condition sequence. The properties for the currently selected condition are shown below the toolbox.

At any time, you can click "Cancel" to discard your changes.

To Add a Condition to a Condition Sequence

  1. Drag the toolbox item to add from the toolbox to the condition column.
  2. Configure the condition's properties in the property grid.

To Reorder a Condition in a Condition Sequence

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

To Remove a Condition from a Condition Sequence

  1. Select the condition to remove.
  2. Click the "Remove Condition".

To Edit Properties for a Task

When a condition is selected, its properties are shown in the Properties window.

All conditions have a "Title" property which can be used to give the condition a descriptive name.

In addition, all conditions have a "Negated" property which can be used to reverse the meaning of the condition. e.g. instead of checking if a setting is true, checking if a setting is NOT true.

Depending on the type of condition, there may be extra properties.

Each property 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.

DriveWorks Tech Tips Portal

Closed Child Specification

A way of completing a Child Specification, pulling data inputted in the Parent Specification, without needing to open the Child.

View all Tech Tips

Import Specifications

Using either the .tab file or a .xml file provided in the drivepkg, generate multiple specifications at once using Autopilot.

View all Tech Tips

DriveWorks Tech Tips Portal is available to DriveWorks Pro customers with an active subscription and support contract.

Tech Tips provide cut down projects that highlight specific functionality for faster and more effective learning.

To access the portal:

  1. Go to https://hub.driveworks.co.uk/tech-tips/
  2. Login with your DriveWorks Pro account credentials, if asked
  3. Click the Visit Tech Tips Portal button for access

The portal provides a search facility, start typing the name of the Tech Tip (as indicated above) to display the Tip you require.

Table of Contents