Transaction rules

Official Content
This documentation is valid for:

Rules play a very important role in transaction objects, as they allow you to program their behavior (for example: assigning default values, defining controls over the data, etc.).
They are written in a declarative way, which means the order in which they are written is not necessarily the order in which they will be executed.
They may involve the attributes included in the transaction's structure (all transaction rules can involve attributes of the base tables associated to the transaction, and most rules
can also involve attributes of the extended tables of such base tables -but they must be included in the transaction's structure-) as well as variables defined within the object, constants and functions.
They are only valid within the transaction in which they are defined, that is to say, they are local.

Some valid rules for transactions are:

Conditional Rules Unconditional Rules
Msg Default
Error Accept
NoAccept Parm
Assignment Serial
Add NoPrompt
Subtract Prompt
Color RefCall 
Call method or rule RefMsg
Submit Equal



Start Video Rules definitions

Was this page helpful?
What Is This?
Your feedback about this content is important. Let us know what you think.