NOT_EMPTY
NOT_EMPTY:
arg: { arg } # required
Description
The NOT_EMPTY operation is the inverse of IS_EMPTY. It checks if the provided argument arg is not considered empty based on the provided type (see Type System). This operation returns a Boolean value: true if the argument is not empty, and false if it is empty.
Parameters
arg(Operation<Any>, required):- Specifies the value to be checked for non-emptiness.
- This can be any operation that resolves to a supported Compliance Engine type (Text, Bytes, Number, DateTime, Collection, etc.).
Return Type
Examples
-
Checking if a text field is not empty:
NOT_EMPTY:
arg:
FIELD:
path: CA10__instanceName__cThis example checks if the value of the
CA10__instanceName__cfield is not empty. -
Checking if a collection is not empty:
NOT_EMPTY:
arg:
COLLECTION:
- "item1"
- "item2"This example checks if the constant collection containing "item1" and "item2" is not empty, which will always be true.
-
Using
NOT_EMPTYin a condition:- status: COMPLIANT
currentStateMessage: "Instance name is provided"
check:
NOT_EMPTY:
arg:
FIELD:
path: CA10__instanceName__cThis condition will be met if the
CA10__instanceName__cfield is not empty, setting the status toCOMPLIANT.
See more details in:
- Unit Tests for
NOT_EMPTYoperation onTexttype - Unit Tests for
NOT_EMPTYoperation onBytestype - Unit Tests for
NOT_EMPTYoperation onBooleantype - Unit Tests for
NOT_EMPTYoperation onNumbertype - Unit Tests for
NOT_EMPTYoperation onDateTimetype - Unit Tests for
NOT_EMPTYoperation onSettype