Hi,
Instead of handling all validations in a single microflow, consider breaking down the logic into smaller, reusable sub-microflows. Each sub-microflow could handle validation for one or a group of related fields Add rules for the valid strin,email,telephone,integer,date and time
(e.g., one for email validation, another for name validation). This modular approach helps keep the main microflow simpler.
Hi Pushpendra,
https://docs.mendix.com/refguide/setting-up-data-validation/--------go through the link for clear validation proccess.
Default Set for rules for possible possible:You’re setting default values or handling for data types like String, Decimal, Email, and Phone number.
Validation Flow:The second image you mentioned likely shows a flow to validate entities (perhaps how data integrity or correctness is checked within the model).
Subflow Creation for Validation:To create a validation subflow:
Start by creating a variable (True/False).Apply a condition to check the attribute. If the condition is True, continue to the next step. If False, merge the validation feedback.After checking all the conditions, the variable is evaluated to see whether the validation passes or fails.
a
3.Image show the rule setup for the microflow---------->