Requiredness Monthly Modeling Highlight follow-up

Hi,

We demonstrated as number of different things in the last Monthly Modeling Highlight including:

  1. How Validation Rules can work together and lead to mandatory Fields
  2. How mandatory Fields can habe a Star in their Label*
  3. How Partial Validation works and when Error Messages can be shown.

Whilst demonstrating how Partial Validation works, I said something that wasn’t 100% true and I want to correct myself.

I was showing you how a Computed Helper Field can be used in Partial Validation to ensure that an Error Message is shown. I showed you that we can either:

  • set this field to be Global or
  • add this Computed Helper Field to the Screen where the Partial Validation is taking place

to ensure that the Computed Helper Field is Relevant for the Partial Validation. I also said that the Field Label* has a Star. This wasn’t true based on the models that I demonstrated but is possible.

A Star is added to the Label as we model a Mandatory Group in Rule 1:

NoGroupFilled(../Repeatable*)

and then reference this Mandatory group in Rule 2:

FieldNotFilled(Field) And AtLeastOneGroupFilled(Repeatable*)

When adapting the Rules to reference the Computed Helper Field, you need to reference the Mandatory Group so that the Field Label* gets a Star and also the Helper Field so that the Rule can be triggered by Partial Validation. This means that Rule 4 in the Models and Explanation should be:

FieldNotFilled(Field) And (FieldFilled(HelperField) Or AtLeastOneGroupFilled(../Repeatable*))

I hope you enjoyed the Monthly Modeling Highlight and we’ll see you again next month.
Happy Modeling :slight_smile:

1 Like