Page History
| Section | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Info | ||||||
|---|---|---|---|---|---|---|
This validator was introduced in version 2.7.0 and replaced the A field is/isn't initialized or has/hasn't been modified (deprecated) validator which had a limited subset of features. |
Purpose
Using this validator you control that fields have certain values during a transition. The following options are available:
- A field is required
- A field must be empty
- A field must be changed on the transition screen
- A field must not be changed on the transition screen
| Info |
|---|
Required fields are marked with a red asterisk (*) next to the field.
|
Purpose
It's a validator for doing any of the following checks:
For cascading select fields both levels are required to be initialized.
Example: Check that field "My Date" hasn't been edited in transition screen
| Status | ||||
|---|---|---|---|---|
|
Since JWT version 2.5.0 it is possible to choose that all values in a multi-valued field have to be checked:
being considered.
Configuration Parameters
When adding a field, selecting the expected behaviour is required.
When adding a multi-value field, all options can be marked as required by checking the Additional options.
When adding multiple fields, all entries are visible (and editable) in the table below.
Usage Examples
| Incoming Links | ||
|---|---|---|
| ||
