Visibility Condition

Source: This article refers to Visibility Condition

In a Nutshell

In a checklist, you can define certain elements as conditional elements. These are elements that appear depending on another value that the user entered/selected in the checklist. To define an element as a conditional element, you use the so-called Visibility Condition. This is a logical expression that refers to another value entered/selected in a previous template element. These are set in the Advanced Settings tab of checklist elements in the Checklist Designer app:




Trigger Elements

The following checklist elements can trigger conditional elements:

  • Checkbox
  • Number input
  • Calculation
  • Drop-down list
  • Status

Conditional Elements

Any checklist element or chapter can be defined as conditional elements. When you define the visibility condition for a conditional element, you need to refer to the ID of the trigger element.


Operators

The visibility condition is defined as a logical expression. You can use the following operators:

Operator Description Example
IS EQUAL Checks if the values of two operands are equal or not, if yes then condition becomes true. (A == B) is not true.
IS NOT EQUAL Checks if the values of two operands are equal or not, if values are not equal then condition becomes true. (A != B) is true.
GREATER THAN Checks if the value of left operand is greater than the value of right operand, if yes then condition becomes true. (A > B) is not true.
GREATER THAN OR EQUAL Checks if the value of left operand is greater than or equal to the value of right operand, if yes then condition becomes true. (A >= B) is not true.
LESS THAN Checks if the value of left operand is less than the value of right operand, if yes then condition becomes true. (A < B) is true.
LESS THAN OR EQUAL TO Checks if the value of left operand is less than or equal to the value of right operand, if yes then condition becomes true. (A <= B) is true.
ISBLANK A commonly-used excel function. Will return true if empty/blank. =ISBLANK (A)
Result: True
NOT ISBLANK The inverse of the ISBLANK function. Commonly used to reverse the behavior of another function. =NOT(ISBLANK(A1))

Conditions

Please take note of the following conditions:

Element Type Description Example
Drop-down lists If a visibility condition refers to an option in a drop-down list, the comparison value is the index of the drop-down option. Index 0 refers to the first non-empty option of the drop-down list, index 1 to the second, etc. For example, if the trigger should be the second option in a drop-down list with the ID DropDown1, you enter the visibility condition DropDown1 = 1.
Series When you define visibility conditions in series, the trigger elements also need to be in that same series.
Tables You can define entire tables as conditional elements. A conditional element can only be applied to an entire table, and not an individual column.
Statuses If you refer to a status, you must put it in quotes, i.e. State1 = “OK” (State1 = OK will not work). As an example, let’s assume the technician needs to carry out a measurement on a machine. If the value measured is higher than 10, you want the technician to enter a comment that explains why the value is so high. To do this, you first define a number element where the technician will enter the value he measured. This element has the title “Measurement result” and the ID “Measurement1”: visibility condition1

You then define a text element where the technician will enter the explanation for the high value. This is a text element with the Title “Comment”. On that element, you use the visibility condition to define the Comment text element as a conditional element. This element is then only triggered if the technician enters a measurement value that is greater than 10. To do so, you enter Measurement1 10 in the visibility condition of the Comment text field.
Checkboxes Referring to a value entered for a checkbox element. Valid values for comparison are true and false. You could use a condition like the following:
  • CheckBox1 = true
  • or CheckBox1 = false
  • orISBLANK(CheckBox1)
Here, Checkbox1 is the ID of the checkbox element that triggers the conditional element.
Number input Referring to a value entered for a number input element. You could use a condition like the following:
  • Number1 = 10
  • or Number1 10 AND Number2 < 90
  • or Number1 < 0
Here, Number1 and Number2 are the IDs of the number elements that trigger the conditional element.
Calculation Referring to a value entered for a calculation element. Valid conditions could be:
  • Calculation1 = 10
  • or Calculation1 10 AND Calculation2 < 90
  • or Calculation1 < 0
Here, Calculation1 is the ID of the calculation element that triggers the conditional element.
Drop-down Referring to a value entered for a drop-down list element. Valid values for comparison are the indexes of the drop down options (where 0 is the first non-empty option). Valid conditions could be:
  • DropDown1 = 0
  • or DropDown1 < 1
  • or NOT ISBLANK(DropDown1)
Here, DropDown1 is the ID of the drop-down element that triggers the conditional element.
Status Element Referring to a value entered for a status element. Valid conditions could be:
  • Status1 = "OK"
  • or Status1 = "OK"
  • or Status1 = "Not Checked"
Here, Status1 is the ID of the status element that triggers the conditional element.

Predefined Values for Checklist Elements

Predefined Checklist Values enables the application to pull data from Business Partner, Service Call, and Equipment records related to an assigned activity and populate the relevant fields of the associated checklist with the relevant information.

This means that when you create a checklist instance from the mobile application on asignment that is linked to a service call, you will automatically see applicable service call, business partner, and/or equipment data associated with the activitiy filled out in the checklist.

The following Checklist elements support predefined values:

  • Text Input
  • Number Input
  • Date/Time
  • Picker
  • Any of the supported element types inside a table

Rules for Predefined Values

Predefined values from Service Call

Service Call If the Checklist Instance is based on a Service Call, then the information for the predefined values are taken from that Service Call.
Activity If the Checklist Instance is based on an Activity, which has an assigned Service Call, then the information for the predefined values are taken from this Service Call.
Other Object In all other cases (Checklist on Business Partner, Equipment, Opportunity, Sales Order, Quotation) the predefined values of a Service Call is not supported, that means the fields will be empty.

Predefined values from Business Partner

Business Partner If the Checklist is based on a Business Partner, then the information for the predefined values are taken from that Business Partner
Other Object If the Checklist is based on a Service Call, Activity, Opportunity, Sales Order, Quotation or Equipment, then the information for the predefined values are taken from the Business Partner of this object.
Activity If the Checklist is based on an Activity we have to go one step deeper and identify the BP, which is linked to the object where the activity is linked to at the end we should always have a business partner.

Predefined values from Equipment

Equipment If the Checklist is based on an Equipment, then the information for the predefined values are taken from that Equipment.
Service Call If the Checklist is based on a Service Call, then the information for the predefined values are taken from the Equipment(s) assigned to Service Call.
Multiple Equipment Records If the Service Call has more than one Equipment assigned, the information is concatenated.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

0 comments

Article is closed for comments.