|
|
|
When defining custom properties, the path to resolve these properties can traverse through a MTM or OTM relation in one or more portions of its path. The syntax to defines these constraints is:
relation1(SQL_constraint):relation2(SQL_constraint):field
where the SQL_constraint describes some attribute of the field that uniquely identifies that object.
For example, a traversal from contact to site must go through the contact_role table.
A contact can have many contact roles, so a constraint can be used to uniquely define which role is to be used.
To define the Sys Admin role:
contact2contact_role(role_name='Sys Admin'):contact_role2site:site_name
To define the Primary Role:
contact2contact_role(primary_site=1):contact_role2site:site_name
RuleManager supports the use of constraints; however, the following operators within a constraint are NOT supported:
See Also |
Next |