Curso GeneXus

Versión: Evolution 3
Curso online

Rules definition

There is a place in each transaction to specify rules to be triggered when the user interacts with the screen  (to insert, modify or delete information).


We see how to ensure that, in the Customer transaction:
  • no record is mace of a customer with empty name, empty surname, or a date in the system later than today (Error rule)
  • a warning message is shown when the phone remains empty (Msg rule)
  • the day’s data is automatically assigned to a Date attribute (Default rule)
  • the edition of an attribute is disabled (Noaccept rule)
We also see how to condition the triggering of a rule. Specifically, in relation to the operation that is to be carried out: Insert, Update or Delete.
We show what variables are and what they are used for, and how we define variables in objects, as well as their main difference compared to attributes.

Click here for a PDF transcript of the video. 
Related
Executing the first project
Declaration of rules
Business Components
Rules definition
Rules in Transactions - More Knowledge
Rules definition
Another example of database update using transactions without form
More about order of execution in transaction rules
Two level transaction used as Business Component, and error management
Themes and images
Moments for rule triggering in transactions
Variables to store data collections in memory
How to update data using transaction logic without screen
More rules for defining behaviors
More on order of execution for rules in transactions
Curso em processo de tradução

Content (20)