This condition ensures that one or multiple fields either have a value or are empty in order to execute a transition.
For cascading select list fields, both levels are considered and need to have/not have a value.
Configuration
If you want to use this functionality in a validator instead, have a look at the following condition: Fields required or changed
Use cases and examples
| Use case | JWT feature | Workflow function | Use case description | Complexity |
|---|---|---|---|---|
| Check for at least one component |
| Require a at least one component. This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator. | BEGINNER | |
| Make the assignee required |
| Require a non empty assignee. This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator. | BEGINNER | |
| Resolution must be empty |
| Not allow a resolution to be set. This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator. | BEGINNER |
If you still have questions, feel free to refer to our support team.
