Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

Snap type:



This Snap provides the functionality to validate incoming data against a set of defined constraints.
Available constraints are:

  • Pattern
  • Minimum
  • Maximum
  • MinLength
  • MaxLength
  • Required
  • Type

An example of a pattern can be seen in the following image:

The pattern constraint in the screenshot above validates all incoming documents and their attributes a.c.b against the regular expression ^abc, expecting that all attribute values of a.c.b start with abc. If they do, the document is routed to the output view; otherwise, the document is routed to the error view.

  • Pattern is a regular expression, defined as a string value.
  • Minimum and Maximum can only be defined for number values. Allowed constraint values are numbers. 
  • MinLength and MaxLength can only be defined for string values. Allowed constraint values are integers. 
  • Required can be defined for any value and will verify that a value exists. The Constraint value field is ignored for the Required constraint.
  • Type can be defined for any source path. The default is object. Valid type definitions are: string, number, object, array, boolean, date, time, date-time, local-date-time, any.

The type constraint should be defined last in case there are multiple constraints defined for a source path.



Support and limitations:

Works in Ultra Task Pipelines.

The Data Validator Snap fails when using null/empty values for the Required option in the Constraints field. A possible workaround is to enter an arbitrary value, which the Snap does not use when executing the Pipelines.


This Snap does not use accounts.


InputThis Snap has exactly one document input view.
OutputThis Snap has exactly one document output view.
ErrorThis Snap has at most one document error view and produces zero or more documents in the view.



Required. The name for the Snap. You can modify it to be more specific, especially if you have more than one of the same Snap in your Pipeline.


Define constraints for one or more fields. If multiple constraints are defined for the same field using the same constraint, only the first definition is considered.

Available options are: 

  • Pattern
  • Minimum
  • Maximum
  • MinLength
  • MaxLength
  • Required
  • Type

Default value: N/A


 Source Path Constraint Constraint Value
 $numberCol Required True
 $numberCol Minimum  1
 $numberCol Maximum 5 

Validate full JSON path

Select this property to enable the Snap to verify if all parents in the JSON path exist, and produce an error if all parents do not exist.


When there is only one Constraint Required=true for a Source path=$a.c.b, but an input document is as follows:

Paste code macro
	"a": {
		"b": {
			"c": "xyz"

The Snap does not produce an error if this property is not selected, even if the JSON path $a.c.b has no values unless there is another Constraint Required=true for a Source path=$a.c.

If this property is selected, the Snap produces an error with a reason field. Example, Path not found: $.a.c, Source path: $.a.c.b, Constraint: Required=true.

Default value: Unselected

Standardize error output

If true, the Snap produces the error document in standard error format (error, reason, original, and stack trace). If false, the error document contains error and original.

Default value: False

Multiexcerpt include macro
nameSnap Execution
pageAnaplan Read

Multiexcerpt include macro
pageAnaplan Read


Multiexcerpt include macro

patterns*.slp, *.zip

Excerpt Include
Flow Snap Pack
Flow Snap Pack