Comparison Rules allow users to construct business rules by comparing one Workflow Attribute against another attribute or a static value. They are widely used through the system to govern things such as:
- Workflow access controls
- Field visibility rules
- Data entry validation rules
- etc
Different comparison operators are supported for different data types:
= Supported / = Not supported
= Data type is optimized for bulk operations
Empty/ Not Empty | Equals/ Not Equal | True/ False | <, <=, >, >= | Between | Contains Substring | Contains Item | ||
---|---|---|---|---|---|---|---|---|
Activity Container | ||||||||
Activity Lookup | ||||||||
Assessment Definition | ||||||||
Assessment Instance | ||||||||
Autonumber | ||||||||
Boolean | ||||||||
Competency Classification | ||||||||
Date | ||||||||
Date Stamp | ||||||||
Date Time | ||||||||
Discussion | ||||||||
Entity Image | ||||||||
Entity List | ||||||||
Image | ||||||||
Long Text | ||||||||
Member | ||||||||
Multi-select | ||||||||
Numeric | ||||||||
Payment | ||||||||
PD In Focus | ||||||||
Picklist | ||||||||
QR Code | ||||||||
Rating | ||||||||
Rich Text | ||||||||
Short Text | ||||||||
Supervisor |
Tag List |
Upload |
Vimeo |
Template |
Tenant Multi-Select |
...
TODO: Document "extended properties"
TODO: Why does Container support Equal/Not Equal but not Empty/Not Empty?
TODO: Document performance optimizations