These rules are used to define form field behavior, validations, and calculations, as well as form validations. Embedded rules allow to define logical conditions and arithmetic expressions, which are evaluated using forms and their related processes.
The definition is done using a wizard integrated into the corresponding modelers. This wizard can be found in the property definition panels of fields and containers, forms and flows if they were conditional.
Unlike the advanced rules, the embedded ones are not displayed into the grid of the modeler because they can only be used in the Deyel object where they are defined.
Types
A behavior rule is used to verify the fulfillment of a condition. A logical expression is evaluated and a "True" or "False" value is returned depending on whether the condition is met or not.
Embedded rules are modeled in form fields and containers, both in the form modeler and in the process modeler when modeling the activities and in the flows if they have conditions.
They are classified according to the purpose of their use.
•Visibility
The modeled condition defines whether a form field or section is visible to the user at the time of use.
•Editability
The modeled condition defines whether a form field is editable for the user at the time of use.
•Required
The modeled condition defines whether a field is required at the time of using the form.
The execution of these rules returns a logical value, "True" or "False".
A validation rule is used to ensure the proper information entry or to control incorrect situations. It can be set at field or form level.
This rule evaluates a condition and returns a message when it is met, indicating the wrong or invalid situation to the user. If no message returns, it means that the validation was successful.
Conditions involving one or multiple fields and the relations among them can be defined.
They define arithmetic expressions that allow to perform calculations to fill in field values when using the form. The rule is defined with a calculation algorithm for the target field that is populated with the resulting value. This value must be of the same type as the field that contains it.
Conditions can also be defined to determine when to execute the calculation rule.
Use
Embedded rules are modeled within the definition panels of Deyel objects properties.
•Rules in Container Properties
•Rules in Field Properties of Agile Forms
•Rules in Properties of Agile Forms
•Rules in Container Properties of Agile Forms
The table below summarizes where the different types of embedded rules can be modeled.
Rule Type |
Field |
Form |
Container |
Flow |
Activity |
|---|---|---|---|---|---|
Behaviour |
|
|
|
|
|
Validation |
|
|
|
|
|
Calculation |
|
|
|
|
|
Only visibility behavior rules can be modeled in a container.
