Conditions

About a Step Condition

When a device user is executing the steps along a route, and if the reading value that is taken for a Step indicates that further investigation is needed, you may want the device user to see additional Steps on the device and record reading values for those additional steps. To accomplish this, you can add conditions to the Steps on the route. A condition allows you to add logic to the route to specify that when a particular reading value is recorded for a Step, additional Steps must be displayed to the device user.

A condition defines:

The Primary Step whose reading value should activate a subsequent Step.
The particular reading value or the reading value within a specified range recorded for the Primary Step, which should activate another Step.
The conditional operator that determines if the reading value recorded for the primary Step meets the condition.
The subsequent Step or Steps that should be activated by that reading value.

A single Step condition can be linked as a successor to only one Primary Step. A Step, however, can be linked to multiple successor Step conditions. Similarly, a Step condition can be linked to multiple successor Steps.

Note: If you add a nested Conditional Step to a Step that is already specified as a Conditional Step on a Primary Step, then the nested Conditional Step will not be available when the Primary Step is included on a Route.

Access a Step Condition

Procedure

In the Rounds Designer page, Access a Step of a route instance, for which you want to access a Step condition.
In the Step Details page, expand the CONDITIONAL STEPS section.
The conditions that are available for the Step appear in the list.

Create a Step Condition

Procedure

In the Rounds Designer page, Access a Step of a route instance, in which you want to create a step condition.

Note: Ensure that the primary step is saved before you add a conditional step.
In the CONDITIONAL STEPS section of the workspace that appears, select Add Conditional Steps.
A row appears, displaying the Primary Step name and the option to set the condition to activate the next step.
Note: If no conditions exist, then Conditional Steps have not been created message appears in the section.
As needed, enter values in the available fields.
Note:
- You can only add the Steps that exist under the asset where the Primary Step exists.
- To add more Conditional Steps, select Add Conditional Steps. Additional rows appear displaying the step name and the option to set the conditions for the subsequent steps to be performed. You can add up to 50 conditional Steps to a single Primary Step.
Select .
The Step condition is saved to the APM database.

Results

The Conditional Steps are displayed below the Primary Step. A Conditional Step uses the value of a predecessor Step to determine the task that needs to be performed after that Step.

In the APM database, a condition is represented by:

One Step that identifies the Primary Step.
One operator that determines if the values entered for the Primary Step meets the condition set.
One Step condition that identifies the specific reading value.
One or multiple Steps that identify the subsequent Steps.

Delete a Step Condition

Procedure

In the Rounds Designer page, Access a Step of a route instance, from which you want to remove a Step condition.
In the CONDITIONAL STEPS section of the workspace that appears, select the Conditional Step, which you want to delete, and then select .

A confirmation dialog box appears, indicating that if you delete the selected Conditional Step other dependent Conditional Steps will also be deleted. The message prompts you to confirm if you want to proceed to delete the selected Conditional Step.
Select Yes.
The selected Conditional Step is deleted from the section.
Select .

Results

The Conditional Step is removed from the APM database. Any other conditions that were dependent on the deleted Conditional Step are also removed from the database.