Skip to main content

FieldLogs

Step Condition

When you create a Step, you can add a condition to the Step. This enables you to change the behaviour of the current Step based on the result of another Step.

To set a condition to the current Step, you need to identify:

  1. Behavior: The behavior(s) of the current Step that need(s) to be changed, and

  2. Condition: The other Step(s) in the Template whose result(s) decide(s) the behavior of the current Step.

To apply conditions to a Step:

  1. Select the Step to which the condition needs to be applied.

  2. Click the Condition Editor webStepCondition_button.png.

The Condition Editor opens.

stepcon1.png

The Condition Editor is divided into three sections to highlight the three possible behavioral changes a Step undergoes.

Based on the conditions, the behavior of a Step can be changed in three ways.

  1. Step Activated: Based on the specified conditions, a Step can be activated or deactivated. If the Step is activated, the user can answer it. Otherwise, it cannot be answered and will appear greyed out.

    This option can be used when the field employee needs to answer a Step only if some conditions are met.

  2. Step Visibility: Based on the specified conditions, a Step can be made visible or invisible to the user.

    This option can be used to display relevant steps to field employees based on user roles and evaluation results of the condition.

  3. Step Locked: Based on the specified conditions, a Step can be locked or unlocked. If a Step is locked, it is still visible, but the user cannot change the value of the Step.

    This option can be used if a Step value is calculated through a script and the value must not be changed by the user.

The table below lists the behaviors that can be controlled based on the Step type.

Table 1. Current Step Type and the corresponding behaviors available in the Condition Editor.

Current Step Type

Step Activated

Step Visibility

Step Locked

Free

greentick.png

greentick.png

greentick.png

Yes/No

greentick.png

greentick.png

greentick.png

Multi-choice

greentick.png

greentick.png

greentick.png

Multi-check

greentick.png

greentick.png

greentick.png

Check

greentick.png

greentick.png

greentick.png

Date / Time

greentick.png

greentick.png

greentick.png

Numeric

greentick.png

greentick.png

greentick.png

Drawing

greentick.png

greentick.png

redcross.png

Signature

greentick.png

greentick.png

redcross.png

Master Data Selector

greentick.png

greentick.png

greentick.png

Go To

greentick.png

greentick.png

redcross.png

Label

greentick.png

greentick.png

redcross.png

Form

greentick.png

greentick.png

redcross.png

Table

greentick.png

greentick.png

redcross.png

Task

greentick.png

greentick.png

redcross.png

Loop

greentick.png

greentick.png

redcross.png

Component

greentick.png

greentick.png

redcross.png

Media

redcross.png

greentick.png

redcross.png



There is an Accelerator dropdown list corresponding to every Step behavior available to the current Step.

StepConditionsAccelerator.png

The Accelerator dropdown list has a list of pre-defined conditions.

Accelerator.png

Note

The Step Value of Type "Validated Signatures" can be applied on any Step. The Condition Accelerator for the Step Value of Type "Validated Signatures" will list only the Signoff Steps that are available for Task and Form Steps.

You can select one of the pre-defined conditions to be applied on the current Step.

To set a condition :

  1. Select a condition from the Accelerator dropdown list.

    Here, the member has chosen to conditionally activate the current Step. Hence, the Accelerator dropdown list under the Step Activated section is used.

    Set_a_condition.png

    The Condition Accelerator dialog opens.

    stepConditionDialog.png
  2. Choose the Step whose result determines the condition. Based on the value of this selected Step, a condition is applied on the current Step.

    Here, the member has chosen to use the result of the Step 1.1 of the template, which is a Check Step.

    stepConditiondeciding.png
  3. Set up the condition by choosing an operator and a value.

    stepConditiondeciding2.png

    Here, the member has chosen to build the condition:

    If{ the step 1.1 of the template is checked }ThenMake Current Step Active

  4. Click Submit.

    stepConditiondecideSubmit.png

The condition is created. The script editor is populated with the script to execute the condition.

stepconPopulateScriptEditor.png