Conditions

Conditions are optional. They restrict a rule so it only runs in specific cases. Each condition compares a field with an operator and — for most operators — a value.

You can add several conditions. All of them must be true for the rule to run (logical AND).

For how to add conditions in the editor, see Creating a rule.

Operators

The same operators are available in every area. Whether a value input appears depends on the operator.

Operator	Meaning	Needs a value?
Equals	The field exactly matches the value.	Yes
Not equals	The field does not match the value.	Yes
Is one of	The field matches one of several values.	Yes
Is none of	The field matches none of the values.	Yes
Contains	The field contains the value.	Yes
Does not contain	The field does not contain the value.	Yes
Is empty	The field has no value.	No
Is not empty	The field has any value.	No
Greater than	The field is greater than the value.	Yes
Less than	The field is less than the value.	Yes
Starts with	The field begins with the value.	Yes
Ends with	The field ends with the value.	Yes

Set operators

Is one of and Is none of compare a field with a set of values instead of a single value. One condition then covers several cases — a rule can run when the task status is Open, In Progress, or Blocked, which would otherwise take three separate rules.

• Available for: text fields, the task status, and custom fields of the types List and Multi-Select. The two operators are not offered for numbers, dates, yes/no fields, contacts, or projects, and not as before-change operators.
• Entering the values: The value field of a set condition takes several entries. It offers the statuses of the current status catalog for the task status, and the entries configured in the field for a List or Multi-Select custom field. You can type your own entries in text fields, and in list fields that allow additional entries.
• How the comparison works: A text field or a List field matches when its value equals one of the entries; for person-name fields the comparison ignores capitalization. A Multi-Select field matches when it contains at least one of the entries. Fields that hold several entries as one text, such as Team or Categories, are compared as a whole — use Contains for them. Is none of is the exact opposite: the rule runs when the field matches none of the entries.
• Switching operators: A single-value operator such as Equals stores one value, a set operator stores several. If you switch between the two kinds, the value field is cleared.

The summary of the rule names every entry of the set, for example Task status is one of Open, In Progress.

Before-change and change operators

These operators compare a field's value as it was before the change that triggered the rule, or test whether the value changed at all. They let you react to how a value changed — for example, only run when the status changed away from a specific value, or only when a specific field was actually modified.

Operator	Meaning	Needs a value?
Before change equals	The previous value exactly matched the value.	Yes
Before change not equals	The previous value did not match the value.	Yes
Before change contains	The previous value contained the value.	Yes
Before change does not contain	The previous value did not contain the value.	Yes
Before change is empty	The field had no value before the change.	No
Before change is not empty	The field had any value before the change.	No
Has changed	The value differs from the value before the change.	No
Has not changed	The value is the same as it was before the change.	No

Only available with the "…updated" trigger

These operators appear in the operator list only when the rule's trigger is the …updated trigger of its area (for example Task item updated or Project updated). They are not available for …status changed, …marked as done, or any other trigger.

Has changed and Has not changed are offered for every field type, custom fields included, and need no value. A field that was never filled in and a field that was cleared both read as empty, so only an actual difference between the two values counts as a change.

Date values

A condition on a date field takes a fixed date or a relative date that InLoox evaluates again every time the rule runs. Choose the kind in the dropdown in the value cell:

Selection	Date used when the rule runs
Fixed date	The date you picked in the date picker.
Today	Today's date.
In	A number of Days, Weeks, Months, or Years after today.
Ago	A number of Days, Weeks, Months, or Years before today.

For In and Ago, enter the number in the field next to the dropdown and pick the unit.

A relative date keeps a rule current without maintenance. For example, the condition Due Date Less than Ago 2 Weeks matches every record whose due date is more than two weeks in the past — on the day you save the rule and on every day after it.

How a relative date is compared

Equals and Not equals compare the calendar day only. Greater than and Less than compare the exact point in time. InLoox evaluates relative dates in UTC, so Today is midnight UTC of the day the rule runs.

Fixed dates and tokens keep working in date fields exactly as before.

Condition fields

The fields you can check depend on the area. The Type determines the value editor (text, number, date, yes/no, or a selection) and which operators the field offers — the set operators Is one of and Is none of only appear for text and list fields.

Person and list fields

Person fields such as Created by, Changed by, Performed by, Manager, or Customer are compared as display names, not as email addresses or IDs. Fields that can hold several entries — Team, Categories, Contributors — contain all entries as one text. Use Contains (or Is empty / Is not empty) for these instead of Equals. For person-name fields, text comparisons are case-insensitive. For example, max mustermann and Max Mustermann match.

Custom fields of the entity

Every area also lists the custom fields of its entity, after the standard fields of that entity: a rule for tasks can check the task's custom fields, a rule for projects the project's custom fields, and so on. Changing a custom field counts as an update, so the …updated trigger fires for it and the before-change and change operators work on custom fields as well.

Formula custom fields are not offered, because their value is calculated and is never stored on the record.

The type of the custom field determines the value editor:

Custom field type	Value editor
String	Text input
Integer, Decimal, Currency, Range	Number input
Datetime	Date picker
Boolean	Yes/No checkbox
Person	Contact picker
List, Multi-Select	Picker with the configured entries of the field

A Multi-Select field holds all its selected entries as one text, so use Contains instead of Equals. If a list field is configured to allow additional entries, you can also enter a value that is not in the list.

Tasks

Field	Type
Task	Text
Description (Task)	Text
Task Status (Name)	Selection or text (typed status name)
Assigned to (Name)	Selection
Project name	Text
Division name	Text
Effort (Task) Hours	Number
Booked time (hours)	Number
Task Completed	Yes/No
Start	Date
Due Date	Date
Contributors	Text
Created by	Text
Changed by	Text
Created on	Date

Projects

Field	Type
Project name	Text
Project number	Text
Project status	Text
Division	Text
Start date	Date
End date	Date
Is archived	Yes/No
Is request	Yes/No
Risk score	Number
Size score	Number
Value score	Number
Customer	Text
Manager	Text
Team	Text
Categories	Text

Budgets

Field	Type
Budget name	Text
Budget type	Selection
Budget date	Date
Amount	Number
Consecutive number	Number

Documents

Field	Type
File name	Text
File type	Text
Folder path	Text
State	Text
Created by	Text
Changed by	Text
Created on	Date
Modified on	Date

Time entries

Field	Type
Name	Text
Description	Text
Start	Date
End	Date
Duration in minutes	Number
Billable	Yes/No
Billed	Yes/No
Performed by	Text
Created by	Text
Changed by	Text
Project name	Text

Planning

Field	Type
Name	Text
WBS code	Text
Progress	Number
Start	Date
End	Date
Is milestone	Yes/No
Is grouping	Yes/No
Duration in hours	Number
Work amount in hours	Number

Line items

Field	Type
Description	Text
Quantity	Number
Unit	Text
Price per unit	Number
Amount	Number
Is billed	Yes/No
Is billable	Yes/No
Group	Text

Risks

Field	Type
Name	Text
Description	Text
Likelihood	Number
Impact	Number
Score	Number

People

Field	Type
Name	Text
First name	Text
Last name	Text
Display name	Text
Company	Text
Email	Text
Phone	Text
Mobile	Text
Position	Text
Department	Text
Street	Text
ZIP code	Text
City	Text
Country	Text

Organizations

Field	Type
Name	Text
Customer number	Text
Street	Text
ZIP code	Text
City	Text
State	Text
Country	Text
Domain	Text

Custom entity types

For a custom-entity rule, conditions are always scoped to the selected custom entity type.

• The available fields include the type's base fields (Name, Description, Owner), and Project for types that can contain project rows.
• The generic Type name field is not shown for type-bound rules.
• Custom fields are limited to the selected type. Formula custom fields are excluded.

Field	Value editor and comparison
Owner	Contact picker
Project	Project picker

See also Triggers and Actions.