Automated qualifiers are files that you create to add conditional expressions to TeamConnect rules and conditions. Automated actions are files that you create to add actions to rules and wizards.
Automated qualifiers and actions display in one of the following two states:
•Current Object State—Object data displayed on the screen at the time when the user attempts a specified operation. In existing records, this data may include previously saved values from the database, as well as the values entered by the user before updating the record.
In new records that are being created, this data includes only the values entered by the user and automatically populated by the system. All rule types, except security, typically use the current object data. Post commit rules only use the current object state.
•Old Object State—Object data stored in the database at the time when the user attempts a specified operation. This applies only to existing records and excludes the values that the user may have entered before saving the record.
Security rules are the only rule type that uses exclusively the old object state. However, sometimes, other rule types may use the old object state to check if any changes have been made to the current object.
Rule Types and Execution Order
The following table indicates which rules may have custom or automated qualifiers and actions.
Rule Type |
Can Have Automated: |
Execution Order |
|
Qualifier |
Action |
||
Security |
x |
|
1 |
Pre-population |
x |
x |
2 |
Validation |
x |
|
3 |
Approval |
x |
|
4 |
Custom Action |
x |
x |
5 |
Scheduled Action |
x |
x |
6 |
Audit |
x |
x |
7 |
Post Commit |
x |
x |
8 |
When a user attempts an operation in TeamConnect, multiple rules may trigger. If rules of different types apply to that operation, the rules execute according to the predefined order indicated in the Rule Types table. You cannot modify the predefined order in which multiple rules execute.
If several rules of the same type trigger, they execute according to the order number of the rule in the user interface (for example, see the General Tab on Rule Screens image). You can change this order.
Parameters
Parameters are arguments passed to the rule through fields in the user interface. The Java file defines how parameters appear as fields in the user interface. The user specifies parameter values in the rule interface rather than in the file. As a result, you can maintain the rule components without modifying the actual code.
