For the complete documentation index, see llms.txt. This page is also available as Markdown.

Conditions

Conditions on the General tab of a migration plan decide which cases the plan migrates. A case is migrated only when all conditions hold. Cases that do not match are left to other plans.

Leave the conditions empty to apply the plan to every case on the source version.


Configuring a condition

1

Open the plan editor and go to the General tab

2

Under Conditions, add a condition and fill in its field, operator, and value

Conditions and operators

A condition consists of a Field (a value on the case, such as its status or a field in its data), an Operator, and a Value. A case whose value cannot be read does not match.

The Field column has a Dropdown / Manual toggle. Leave it on Dropdown to pick a field from the case's data model, or switch to Manual to type a path the dropdown does not offer, such as case:sequence.

Operator
Matches when

==, !=

The field is (not) equal to the value

>, >=, <, <=

The field is greater or smaller than the value. Numbers are compared as numbers, anything else alphabetically

in

The field equals one of several values. Enter the values separated by commas, for example in-behandeling,wacht-op-klant

contains

The field contains the value: one of the entries when the field holds a list, part of the text when it holds a single value

exists

The field has a value at all. Leave the value empty, or enter false to match only cases where the field is empty or missing


Combining conditions with groups

Conditions listed one after another must all hold. To express an either/or, add a group. Each group has a The group holds when selector, set to either Any of these hold (OR) or All of these hold (AND). A group can contain other groups, so conditions can be combined to any shape.

1

Under Conditions, click Add group

2

Set The group holds when to Any of these hold or All of these hold

3

Add conditions, or further groups, inside it

Nested condition groups

A group must contain at least one condition, and groups may be nested up to ten levels deep.

Example: a nested combination in the plan JSON

The combination "status is in-behandeling, and either the case is marked urgent or (the amount is at least 1000 and a file number is present)" reads as follows in the JSON editor tab:

Building block migration plans have no conditions. They apply to every building block instance the case migration brings onto the plan's version. See Building blocks.

Last updated