Content Comparison

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	Greater / Less Than	Between	Contains Substring	Contains Item	Extended Properties / Special behaviors
Activity Container									Total activity count Total completed successfully Total completed unsuccessfully Total incomplete
Activity Lookup
Assessment Definition
Assessment Instance									Assessment Status Pass / Fail
Autonumber
Boolean
Competency Classification
Date									Comparison to date offset
Date Stamp									Comparison to date offset
Date Time									Comparison to date offset
Discussion
Email
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

Anchor
BulkOperations BulkOperations

Bulk Operation Support 

As of LearningBuilder 9.1, certain Comparison Rules can be evaluated directly in the database to dramatically improve performance of bulk operations. 

In order for this optimization to occur, the Comparison Rule must:

1. Target an Extrinsic attribute of a supported data type (see table above) or a supported Intrinsic attribute  
2. Be used in a feature that supports bulk optimization

As of 9.1, the features supporting bulk optimization are:

1. Scheduled Workflow Behaviors

Anchor
ExtendedProperties ExtendedProperties

Extended Properties

Certain data types expose more than one value that can be targeted by a Comparison Rule. This is commonly seen in data types representing complex interactions or in "container" type attributes.

 NOTE: Unless specially noted, rules targeting extended properties are NOT optimized for bulk operations, regardless of the data type.

TODO: Why does Container support Equal/Not Equal but not Empty/Not Empty?

Related articles