# Expression language for defining conditions (conditions with getValue)

#### Condition writing editor <a href="#jezykwyrazendefiniowaniawarunkow-warunkizgetvalue-edytorpisaniawarunkow" id="jezykwyrazendefiniowaniawarunkow-warunkizgetvalue-edytorpisaniawarunkow"></a>

[Advanced condition editor](/documentation/documentation-en/budowanie-aplikacji/logika-biznesowa/jezyk-wyrazen-definiowania-warunkow-warunki-z-getvalue/zaawansowany-edytor-warunkow.md)

#### Conditions in JavaScript format <a href="#jezykwyrazendefiniowaniawarunkow-warunkizgetvalue-warunkiwformaciejavascript" id="jezykwyrazendefiniowaniawarunkow-warunkizgetvalue-warunkiwformaciejavascript"></a>

{% hint style="warning" %}
Conditions within composite components

For conditions written in composite components, variable/field identifiers should be prefixed with the character **@** e.g. @GesCombobox1.
{% endhint %}

It is possible to describe all conditions defined in the application template using language expressions **JavaScript**.

JS conditions provide the methods:

* *getValue("COMPONENT\_ID")* - the recommended way to return the value of a component (any other may cause performance issues)
* *getData*(*"COMPONENT\_ID","COMPONENT\_ATTRIBUTE"*) - returns the value of the specified component attribute; available attributes can be found here [Component attributes](/documentation/documentation-en/budowanie-aplikacji/logika-biznesowa/jezyk-wyrazen-definiowania-warunkow-warunki-z-getvalue/atrybuty-komponentow.md)
* *isVisible("COMPONENT\_ID")* - a way to check whether a component is visible (listening is required; it is not possible to retrieve the visibility of a radio button or the visibility of elements inside a repeating section from outside the repeating section)
* *getStatementValue("COMPONENT\_ID", "STATEMENT\_ID") -* allows returning the value of the selected statement for the Statements component.

All field values available during condition evaluation are text values; therefore, for operations on numbers or boolean types, a proper conversion must be performed.

Examples of conditions in format **JavaScript**:

```javascript
// integer comparison of a TextField field
parseInt(getValue("GesTextField3"))>5
  
// floating-point comparison of a TextField field
parseFloat(getValue("GesTextField5"))<200.001
  
// comparison of a logical value (equal) of a CheckBox field
getValue("GesCheckbox1")=="true"
 
// comparison of a logical value (different) of a CheckBox field
getValue("GesCheckbox1")!="true"
 
// comparison of a text value of a RadioGroup field
getValue("GesRadioGroup1")=="audi"
  
// check whether a value, e.g. a session variable, is not empty
!!getValue("nazwiskoZew")
  
// check whether a value, e.g. a session variable, is empty
!getValue("nazwiskoZew")
  
// check whether the statement with MID oswiadczenie1 in the component with id GesStatementPopup1 has been accepted
getStatementItem("GesStatementPopup1","oswiadczenie1") == "true"
  
// check whether the statement with MID zdrowotne in the component with id GesStatementFlat5 (located in a composite component) has been accepted
getStatementItem("@GesStatementFlat5","zdrowotne")=="false"
 
 
// required condition for a field, if others are empty
!!!(getValue("@GesTextField13")||getValue("@GesTextField8"))
 
 
// checking combobox values
getValue("@GesCombobox1")!=2&&getValue("@GesCombobox1")>0
 
 
// check whether the TextField is visible
isVisible("@GesTextField1")=="true"
 
 
// check whether the number of characters in the TextField is 10
getValue("GesTextField5").length==10
```

In conditions, identifiers (**id**) of all fields available in the application template can be used.

The syntax allows defining:

* negation of an expression using the "!" operator at the beginning of the expression
* conjunction of expressions with the "&&" operator, e.g. getValue("@GesCombobox1")==1&\&getValue("@GesCombobox1")==2
* alternative of expressions with the "||" operator, e.g. getValue("@GesCombobox1")==1||getValue("@GesCombobox1")==2

The following types can be used in expressions:

* constant values
  * text
  * numeric
  * binary - true and false
* component identifiers, e.g. GesTextField1
* application variable identifiers, e.g. partner.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/logika-biznesowa/jezyk-wyrazen-definiowania-warunkow-warunki-z-getvalue.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.