Validate a property
I am trying to validate the expected length of a property.
To do so, I navigated to the App Explorer > Case type > Data model > Property > myProperty >Advanced Tab > Expected length validation ; as shown in the picture below. But once I saved my work, It did not work as expected.
I went further and I noticed that any of the validation I could set in that tab does not take effect (column inclusion required, ...)
Here are my questions:
1. Why validations configurations are not working there?
2. Is there any other place(or way) where I can set an expected length for my property ; except an edit validate rule
***Edited by Moderator: Pallavi to update platform capability tags***
Thanks for your reply MarcLasserre_GCS,
How to navigate to there?
The SECTION is called pxUIGalleryTextInput
I do not think you answered to my question
I asked how to access to that page view in your screenshot from my environnement for the property I would like to apply an expected length to
Go to Configure --> User Interface --> Gallery --> UI Elements --> Text Input
Okay, I got there.
From there, I am able to configure a specific control instead of specific property right ?
Please fin the below screenshot for details about the Expected length in the Advanced tab of Property rule.
To give the minimum and maximumn lenth, you can configure Min characters and Max charaters in the presentation tab.
Please find the below screenshot for more details.
Thanks for your help kanap2,
I understand deeply the expected length setting.
What about the column inclusion setting?
It did not work as well, when I set it to required in order to make the field required.
Please fin the below screenshot for details about column inclusion.
You can configure the required option on the Cell properties in General Tab of the control.
May I ask how to access the to cell properties of a specific field.
I tried to do so through App Explorer > User Interface > Section
But I am only able to navigate up to the dynamic layout containing fields instead of those fields themselves
I did, it is okay
Can you check the one in the UI Gallery: