You are here:
State Transition Rule Examples
There are many ways to use expressions to reference base object and linked object fields in State Transition Rules.
An expression in a State Transition Rule:
-
Can include any operators and functions in the Function Reference.
-
Must evaluate to true or false
-
Is usually based on field values in the base object and/or linked objects
A base object and a linked object can be related in two ways:
-
The base object has a lookup field that references the linked object directly, such as ContactId.
-
One or more base object field values match one or more linked object field values. For example, an Application__c object and a ProviderContactLicense__c object both have fields that reference a Contact Id.
In either case, the linked object must be configured for use in the rules. For details, see Workflow for Creating State Transition Rules.
The rule expressions in this topic use the namespace vlocity_ins for
custom objects and fields. If your org has a different namespace,
vlocity_cmt or vlocity_ps, use that instead.
The following table lists examples of ways to reference base object and linked object fields in State Transition Rules.
Referenced Fields | Example |
|---|---|
Base object field |
|
Base object direct lookup of linked object field |
|
Linked object field with no base object lookup |
|
Linked object field with no base object lookup, but linked object lookup |
|
Combination of base object field and linked object field with no base object lookup |
|
Combination of base object field, direct lookup, linked object field, and linked object lookup |
|

