Components : Client side validation

The UI framework supports validating components before sending the metadata to Flow for more complex validation. This can be useful for reducing latency on mobile devices, bandwidth constrained clients, or if you want to implement custom validation e.g. an input that accepts a certain format.

Client side validation can be performed when the flow progresses forward via an outcome that has been configured to Save Changed Values. For example:

Currently, the client side validation rules will only check if required components have a selected value. For a component to be considered invalid, it will need to satisfy the following rules:

  1. isRequired is set to true
  2. contentValue is null or an empty string
  3. objectData is null or an empty array
You may also like: