---
title: Introduction to Activate Expressions
slug: introduction-to-activate-expressions
createdAt: 2026-01-06T21:58:15.945Z
---

Activate Expressions are a built-in expression language used throughout Activate to dynamically evaluate values at runtime. They allow configuration to adapt based on context — such as the current user, job data, system state, or configuration values — without the need for custom code or scripting.

Expressions are used anywhere Activate needs to make a decision, transform data, or generate dynamic output. Common uses include conditional logic in web forms, controlling workflow behaviour, formatting values in notifications, and validating or comparing data during execution.

At their core, Activate Expressions:

- Read values from the Activate data model (for example, users, jobs, roles, or system properties) 
- Apply logic such as comparisons, conditions, and boolean checks 
- Transform or format data, including dates, strings, and lists 
- Return a value that Activate can use to control behaviour or display information 

## Expression syntax

All Activate Expressions start with an equals sign (=). This tells Activate to evaluate the value as an expression rather than treat it as a static string.

Depending on where an expression is used, you will often see it wrapped in percent signs (%). Wrapping an expression in % tells the interpreter to resolve the expression and substitute the result into the surrounding text.

For example:

:::BlockQuote
The user who is submitted this job is %=//Job/SubmitUser/DisplayName%
:::

This resolves the expression and inserts the display name of the user who submitted the current job.

Expressions can also be used without % when the entire value is expected to be an expression result, such as in boolean conditions or configuration parameters.

Expressions can reference data using paths, call built-in functions, or combine both to produce a result. They are evaluated at runtime within the context in which they are used, such as a web form, workflow, or notification.

For example:

:::BlockQuote
\=if(=/user/IsDisabled, "Disabled", "Active")
:::

This expression checks whether the current user is disabled and returns a corresponding value.

## Design principles

Activate Expressions are intentionally concise and declarative. They are designed to be readable, reusable, and safe to use within configuration, making them a powerful tool for extending Activate behaviour while keeping implementations consistent and maintainable.