> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/logika-biznesowa/jezyk-wyrazen-definiowania-warunkow-warunki-z-getvalue/zaawansowany-edytor-warunkow.md).

# Advanced condition editor

{% hint style="info" %}
The editor does not require entering the prefix "**js:"** and it will not display it in conditions. The prefix will be automatically added in the source when saving changes.
{% endhint %}

## Introduction

The advanced condition editor is a special editor designed to improve the work of the form designer. It has been equipped with the following features:

* syntax highlighting,
* displaying variable and field name hints while editing conditions,
* displaying eximee API hints while editing conditions.

<figure><img src="/files/3587494caa82a3fcb060380fbda85bb165f5bbf9" alt=""><figcaption><p><em><strong>Figure 1.</strong> Example conditions in the component properties palette</em></p></figcaption></figure>

## Occurrence locations <a href="#zaawansowanyedytorwarunkow-miejscawystapienia" id="zaawansowanyedytorwarunkow-miejscawystapienia"></a>

Three component attributes in Eximee Designer use this editor. These are:

* visibility condition,
* activity condition,
* required condition.

<figure><img src="/files/45bd570abdc1c122b79740a69e2b4237782cf85e" alt=""><figcaption><p><em><strong>Figure 2.</strong> Advanced condition editor - editing the visibility condition</em></p></figcaption></figure>

## Syntax hints <a href="#zaawansowanyedytorwarunkow-podpowiadanieskladni" id="zaawansowanyedytorwarunkow-podpowiadanieskladni"></a>

The editor suggests eximee API elements and commonly used JS methods to the user. Editor hints can be seen by clicking the Ctrl + Space key combination. This will expand a list of elements, among which you can see the following:

Standard JS methods and fields:

* parseInt()
* parseFloat()
* .length
* size
* empty

API provided by eximee:

* getValue()
* getData()
* isVisible()
* getStatementValue()

<figure><img src="/files/47690305dcf9adfd6de25ee033e37c1873a87217" alt=""><figcaption><p><em><strong>Figure 3.</strong> Advanced condition editor - expanded list with syntax hints</em></p></figcaption></figure>

\
Additionally, component MIDs (with their ID in parentheses) and the names of session variables present in the application will appear in the hints.

<figure><img src="/files/4c5019d79a40152a1647b24bfa1cd4016eca3165" alt=""><figcaption><p><em><strong>Figure 4.</strong> Advanced condition editor - view of hints for components located in the artifact</em></p></figcaption></figure>

<figure><img src="/files/f9de7e14f180fe148e92644db6cdb17fc62260ea" alt=""><figcaption><p><em><strong>Figure 5.</strong> Advanced condition editor - view of hints for filtered components</em></p></figcaption></figure>

## Condition examples <a href="#zaawansowanyedytorwarunkow-przykladywarunkow" id="zaawansowanyedytorwarunkow-przykladywarunkow"></a>

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

```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.