---
title: Using the Expression Editor
slug: neurons-for-itsm/admin-user-help/enu/latest/using-the-expression-editor
createdAt: 2026-07-14T19:16:49.146Z
---

**Role**: Administrators

**Minimum Version**: Ivanti Neurons for ITSM 2023.4

- [About the Expression Editor](docId:-MnV7inwAQ168sHiadvI5)
- [Expression Editor Features](docId:-MnV7inwAQ168sHiadvI5)
- [Accessing the Expression Editor](docId:-MnV7inwAQ168sHiadvI5)
- [Using the Expression Editor](docId:-MnV7inwAQ168sHiadvI5)
- [Using the Simplified Expression Editor](docId\:AYcVgwQ-XAxop0oFPGL9H)
- [Using Comments in Expressions](docId:-MnV7inwAQ168sHiadvI5)

## About the Expression Editor

Use the **Expression Editor** to construct expressions, to create or edit rules (for example, an initialization, editing, calculation, read-only, required, or before-save rule), and as a tool in creating and editing quick actions.

*Expression Editor*

::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/8WSVTAJN9bTgDQMuEtDpj_expression-editor-new.png" size="40" isUploading="false" initialPath="../../Resources/Images/help-images/expression editor new.png" githubPath="Content/Resources/Images/help-images/expression editor new.png" width="917" height="532" showCaption="false" darkWidth="917" darkHeight="532"}

The **Expression Editor** has five parts: the , the left side where you enter syntax, the lower message area, and the right side where you select fields, functions, and time zones.

- **Header area**: Enter a field name, rule name, and rule description. You can also elect to simplify the expression.
- **Upper message area**: Watch for errors, warnings, or informational messages about your expression. It shows any of the following messages:
  - "Please correct the errors in your expression and try the save again."
  - "Your expression has warnings. If you click **Save** again, your expression will be saved but may not function correctly. We recommend that you address the warnings before saving."
  - "Your expression has no warnings or errors, but there are some informational messages that suggest how to check or improve or check your expression. If you click **Save** again, your expression will be saved and will function correctly."
- **Left side**: Enter syntax for the expression.
- **Lower message area**: Watch for errors, warnings, and informational messages about your expression.
- **Right side**: You can select fields, relationships, functions, time zones, and more. The available selections depend on the business object. To select an item, highlight it and double click. The application adds the correct syntax for that item to the left side.
- Make the **Expression Editor** larger by dragging the control on the bottom right corner or resize the left and right sides.

*Parts of the **Expression Editor***

::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/n5LeUfQeNHyzOjXgQxOXQ_expression-editor-new2.png" size="40" isUploading="false" initialPath="../../Resources/Images/help-images/expression editor new2.png" githubPath="Content/Resources/Images/help-images/expression editor new2.png" width="999" height="597" showCaption="false" darkWidth="999" darkHeight="597" position="flex-start"}

## Expression Editor Features

### Color Coding in the Expression Editor

The **Expression Editor** uses color coding help visualize the structure of your expression. These colors are fixed and cannot be customized.

| Construct   | Keywords                                                                                           | Current Color     |
| ----------- | -------------------------------------------------------------------------------------------------- | ----------------- |
| Operator    | \* - + / $ \| &                                                                                    | #C800A4 -- sample |
| Left paren  | ( )                                                                                                | black             |
| Keyword     | if, then, else, original, current, language, where, outer, object, fold, map, all, none, any, each | #C800A4 -- sample |
| Constant    | null                                                                                               | #C800A4 -- sample |
| Punctuation | . ,                                                                                                | black             |
| Numeric     | numbers                                                                                            | #3A00DC -- sample |
| String      | strings                                                                                            | #DF0002 -- sample |
| Function    | functions and fields from business objects                                                         | #450084 -- sample |
| Designator  | other object, validation list, matched object, this#form, top, parent, link, join                  | black             |
| Comment     | // /\* \*/                                                                                         | green             |

### Typing Ahead in the Expression Editor

When you enter an expression directly into the left side of the **Expression Editor**, the application provides hints based on what you enter. For example, if you know that you want to enter something about email, type email, and the application displays a list of all the field names, functions, and keywords that have email in them.

*Expression Editor Displaying Hints*

::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/vZPnvpTJhf2Hoy-NHX9Ab_expression-editor-type-ahead.png" size="40" isUploading="false" initialPath="../../Resources/Images/help-images/expression editor type ahead.png" githubPath="Content/Resources/Images/help-images/expression editor type ahead.png" width="823" height="395" showCaption="false" darkWidth="823" darkHeight="395" position="flex-start"}

### Showing Display Names

The application shows both the business object name and the display name for items on the right side of the Expression Editor, but only if the display name is different than the business object name. The display name is shown in parentheses. You can also search by both business object name and display name.

### Using Code Snippets

You can add predefined snippets to an expression. On the left side, start typing and the application displays a list of all the snippets, keywords, functions, and fields with the text that you entered.

*Adding a Snippet in the Expression Editor*

::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/LuX6f6iLVYoW9hTnngCb-_expression-editor-snippet.png" size="40" isUploading="false" initialPath="../../Resources/Images/help-images/expression editor snippet.png" githubPath="Content/Resources/Images/help-images/expression editor snippet.png" width="824" height="395" showCaption="false" darkWidth="824" darkHeight="395" position="flex-start"}

### Simplifying Expressions

### About Simplifying Expressions

You can simplify expressions. The simplify feature works for all expression types, such as Boolean, DateTime, text, integer, etc. It mostly handles Boolean expressions, replacing one expression by another that is equivalent, but simpler. The simplify feature also replaces some implicit conversion with explicit conversions, which can make the expression longer but makes it simpler.

### Boolean Simplification

In the following examples, **e** is a Boolean expression. If **e** is another type of expression that can be implicitly converted to **e**, then the result is the converted value, not the original **e**.

### Boolean Operations with Constants

$(e and true) => $(e)

$(e and false) => $(false)

### Removing "Not"

$(not not e) => $(e)

$(not true) => $(false)

### Equality and Inequality

$(true == e) => $(e)

$(e == false) => $(not e)

### DeMorgan's Rules

$(not (e1 and e2)) => $(not e1 or not e2)

$(not (e1 or e2)) => $(not e1 and not e2)

### Relational Inversion

In this section, **a** and **b** are two comparable values, not necessarily Booleans. However the result of comparing them via a relational value is always Boolean and therefore this section is included with the Boolean simplifications.

$(not (a \<= b)) => $(a > b)

$(not (a in (v1, v2,...)) => $(a not in (v1,v2,...))

### Conditional Simplification

In this section, **e** is a Boolean expression and **a** and **b** are two expressions of the same type.

$(if a > 0 then true else false) => $(a > 0)

$(if e then false else true) => $(not e)

If **e1** and **e2** are Boolean expressions, then:

$(if e1 then e2 else false) => $(e1 and e2)

### Inserting Conversion Operators

The simplify feature does not insert an explicit conversion of any type to text. However, using other conversion operators makes the intent clearer. For example:

$(if 5 then a else b) => $(if Boolean(5) then a else b)

$(true + 10) => $(Number(true) + 10)

### Using the Expression Validator

- [About the Expression Validator](docId:-MnV7inwAQ168sHiadvI5)
- [Expression Validator Error Messages](docId:-MnV7inwAQ168sHiadvI5)

### About the Expression Validator

The expression validator provides informational messages about the correctness of expressions. The expression validator is used everywhere to validate the expressions where ever they are used and is a part of the metadata validator, described in [Working with Metadata](docId\:HCyGo3Qn4VdSxxCUnJwgG).

The expression validator validates business rules, quick actions, data segregation, form expressions, and control expressions. It does not perform detailed validations for LDAP, request offerings, pick lists, or relationship expressions.

The expression validator checks the semantics of the expression, such as ensuring the following:

- Neurons for ITSM function names refer to functions that exist.
- The field names are correct and refer to existing fields.
- The types of expressions (such as Boolean, text, etc.) are correct.

The parser checks the syntax and figures out the structure of the expression, such as ensuring that:

- Parentheses match.
- All statements are correct, for example making sure that "if" statements have a "then" and "else".
- Operators are used properly.

### Expression Validator Error Messages

The expression validator provides informational messages and suggestions about expression semantics. For example, if you enter something incorrectly into the Expression Editor, (such as misspelling an expression name), the expression validator returns a warning or error message and provides a hint about the problem.

In the following example, the name of the built-in function FindAncestor is misspelled. The expression validator provides an informational error message and does not allow you to save the expression and may also give you a suggestion about which function to use.

*Expression Editor Validation Message Example 1*

::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/WZisB5PZnqRU0MyoXYLpz_validator1.jpg" size="40" isUploading="false" initialPath="../../Resources/Images/help-images/validator1.jpg" githubPath="Content/Resources/Images/help-images/validator1.jpg" width="988" height="589" showCaption="false" darkWidth="988" darkHeight="589" position="flex-start"}

In this example, the expression validator displays an error message:

*Expression Editor Validation Message Example 2*

::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/6plXbzXuCxYy1Vach2vee_validator2.jpg" size="40" isUploading="false" initialPath="../../Resources/Images/help-images/validator2.jpg" githubPath="Content/Resources/Images/help-images/validator2.jpg" width="991" height="590" showCaption="false" darkWidth="991" darkHeight="590" position="flex-start"}

The **Expression Editor** displays a superscript number next to an error if there are multiple errors, to make it easier to identify which error goes with which error message. The **Expression Editor** also provides information about misspelled validation list values, identifies keywords, and displays helper text that gives alternatives.

*Expression Editor Validation Message Example 3*

::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/yvl7VkKwhzqCTmSoE6OZ__expression-editor-new3.png" size="40" isUploading="false" initialPath="../../Resources/Images/help-images/expression editor new3.png" githubPath="Content/Resources/Images/help-images/expression editor new3.png" width="839" height="588" showCaption="false" darkWidth="839" darkHeight="588" position="flex-start"}

## Accessing the Expression Editor

You can access the **Expression Editor** in different ways, depending on the business object type.

- [Accessing the Expression Editor from the Configuration Console](docId:-MnV7inwAQ168sHiadvI5)
- [Accessing the Expression Editor from a Business Rule](docId:-MnV7inwAQ168sHiadvI5)
- [Accessing the Expression Editor from a Quick Action](docId:-MnV7inwAQ168sHiadvI5)
- [Accessing the Expression Editor from a Saved Search](docId:-MnV7inwAQ168sHiadvI5)

### Accessing the Expression Editor from the Configuration Console

There are several ways to access the **Expression Editor** in the Configuration Console.

- **Business Object** workspace > **Relationships** tab > open a relationship > **Relationship Details** section > **Condition** field
- **Business Object** workspace > **Forms** tab > open a form > **Control Properties** tab
- **Business Object** workspace > **Lists** tab > open a list > click **List Properties** > open **Style** drop-down list
- **Business Object** workspace > **Layouts** tab > open a layout > click **formView** > click **Hidden Expression**, **Link Button Filter**, **List Filter**, or **Initially Visible**
- **Business Object** workspace > **Workflows** tab > open a workflow > click the **edit** icon :inlineImage[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/yOwMLewyf7Jh4cJ7j1Crw_edit-old.png" alt caption size="10" width="16" height="16"}> **Insert Child Object**, **Insert Multi Child**, **Update** blocks
- **Pick Lists** workspace > open a pick list > add a constraint
- **Automation Tools > Object Matching Lists** workspace > open an object matching > click **Edit Filter** > **Condition** field
- **Automation Tools > Object Matching Lists** workspace > open an object matching > click **Edit Preview** > click **Edit Filter** > **Condition** field
- **Automation Tools > Watch Lists** workspace > open a watch list
- **Mobile Layouts** workspace > open a layout > click **Customize Detail View** > add or edit a field
- **User Interface Styles > Calendars** workspace > click **Change Calendar** > **Multi-Day Title Expression** or **Single-Day Title Expression** fields
- **Users and Permissions > Roles and Permissions** workspace > open a role > **Object Permissions** tab > select a business object > click **Edit** under **Access** > click **Add a new case...**.
- **Dashboards** workspace > open a dashboard > **Tree Parts** section > **Node Properties** section
- **Dashboards** workspace > open a dashboard > **Pivot Tables** section > **Filters** tab

### Accessing the Expression Editor from a Business Rule

1. In the Configuration Console, click **Build > Business Objects** to open the **Business Objects** workspace.
2. Open a business object.
3. Click the **Business Rules** tab.
4. To add a new business rule, expand the section for a business rule and click **Add \<*type of rule*> Rule**. For example, to add an initialization rule, click **Add Initialization Rule**. The application displays the **Add \<type of rule> Rule** dialog box, including the **Expression Editor**.
5. To edit an existing business rule, click the **edit** icon :inlineImage[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/yOwMLewyf7Jh4cJ7j1Crw_edit-old.png" alt caption size="10" width="16" height="16"}. The application displays the **Edit Business Rule** dialog box, including the **Expression Editor**.

### Accessing the Expression Editor from a Quick Action

1. Log into the Service Desk Console.
2. Click **Incident** to open the **Incident** workspace.
3. Click **Action Menu > Edit Actions**. The application displays the Action Designer.
4. Select any action that updates values.
5. Click **Edit**.
6. To edit a field value, click the **edit expression** icon :inlineImage[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/gBVrX-tsFJubsDxjfXHiz_function.png" alt caption size="10" width="16" height="16"}. The application displays the **Expression Editor**.

### Accessing the Expression Editor from a Saved Search

1. Log into the Service Desk Console.
2. Open a workspace.
3. Click the down arrow next to the word **All** to open the **Saved Searches** menu for that workspace.
4. Click the **edit** icon :inlineImage[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/yOwMLewyf7Jh4cJ7j1Crw_edit-old.png" alt caption size="10" width="16" height="16"} to edit a saved search.

## Using the Expression Editor

1. Access the **Expression Editor**. See [Accessing the Expression Editor](docId:-MnV7inwAQ168sHiadvI5).
2. In the **Expression Editor**, enter an expression or drag a function from the **Functions** drop-down list to the **Expression Editor**.
3. Click **Save**.

## Using Comments in Expressions

Add comments to your expression code, or comment out code in the **Expression Editor** and in the **Simplified Expression Editor**. The following rules appy to comments when entered into an expression:

- When characters '**//**' are entered into an expression, all expression syntax entered from that point to the end of the line is classed as a comment.
- When characters '**/\***' are entered into an expression, all expression syntax entered from that point to a closing '**\*/**' is classed as a comment. If no closing '**\*/**' is found, all expression syntax up to the end of the expression is classed as a comment.
- Comments are highlighted in green text.
- Multiple comments are permitted within an expression.
- If you select **Simplify Expression**, any comments added to your expression may be removed. This depends on whether the expression can be simplified or not.

:::hint{type="info"}
See [Using Multiple Lines and Tab Spaces in Expressions](docId\:Pf6GGQn8-_-79wX1mpBId) for information on adding multiple lines and tab spaces in your expressions.
:::