Embedded Rules
Embedded rules are used to define the behavior of application objects, such as entities, pages, processes and forms, without the need for programming.
These rules are defined using a simple syntax, similar to that used in spreadsheets, with the help of a wizard , if necessary. This wizard is integrated into the corresponding object modelers, within the property definition panels of fields, containers, forms and conditional flows, as well as page and entity elements.
Through the use of embedded rules it is possible to define calculations, validations and conditions that modify the behavior of application objects. In entities, pages, forms and process activities, it is possible to define requirement, visibility and editability rules, as well as calculation and validation rules at field or element level. Furthermore, in the case of processes, gateway conditions can also be modeled using embedded rules.
Unlike the advanced rules, embedded rules are not displayed into the modeler's grid, as 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 the fields and containers of entities and forms, either from their respective modelers or from the process modeler when modeling their activities. They can also be defined in entity and page elements, as well as in process gateways when conditions are required.
They are classified according to the purpose of their use.
•Visibility
The modeled condition defines whether a field, a page or entity element or a form section is visible to the user at the time of use.
•Editability
The modeled condition defines whether an element of a page or entity or a form field are editable by the user at the moment of using them.
•Required
The modeled condition defines if a field or an element of a page or entity are required when using them.
A validation rule is used to ensure the proper information entry or to verify incorrect status. It can be set at the field level for entities, pages and forms.
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.
To define arithmetic expressions that allow to perform calculations to fill in field values when using the entity, the page or 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 that contain them.
Forms Modeler
•Rules in Container Properties
Processes Modeler
Pages Modeler
Entities Modeler
