You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We just started to create new field types and found the "Is this a required field?" flag on the EDIT VALIDATION RULE page somewhat misleading.
Based on our test, this flag is really controlling the behavior of the server-side RSV validation engine on this rule. If set to Yes, the server-side validation engine will skip this rule. This is needed if this rule is based on a client-side JS function code, the server-side has no code to perform the validation.
However, this flag is labeled as "Is this a required field?" with the following description: "If this is set to yes, any time this validation rule is applied to a field, an asterix will appear next to it, to indicate the field must be entered." This seems to be misleading.
Hope someone can clarify our understanding.
Thanks.
Herong
The text was updated successfully, but these errors were encountered:
We just started to create new field types and found the "Is this a required field?" flag on the EDIT VALIDATION RULE page somewhat misleading.
Based on our test, this flag is really controlling the behavior of the server-side RSV validation engine on this rule. If set to Yes, the server-side validation engine will skip this rule. This is needed if this rule is based on a client-side JS function code, the server-side has no code to perform the validation.
However, this flag is labeled as "Is this a required field?" with the following description: "If this is set to yes, any time this validation rule is applied to a field, an asterix will appear next to it, to indicate the field must be entered." This seems to be misleading.
Hope someone can clarify our understanding.
Thanks.
Herong
The text was updated successfully, but these errors were encountered: