Defining Rules and Rule Criteria – Squivr

Introduction

This article will document key terminology as well as outline the steps required for defining a new Rule and Rule Criteria

Field	Definition
Name	The name should be something that will help admin users know which rule they are dealing with.
Label	This will be displayed if the Requirement Level is not 'Not Required' and a record has not met the Rule Criteria. (Specific to Group Configurations)
Rule Logic	This determines how the rule criteria is evaluated for if a record is added to the group. If the field is left empty, it will evaluate if everything is true (AND) otherwise logic will need to be defined (1 AND 2) OR (3 AND 4).
Requirement Level	The available options are 'Not Required', 'Nice to Have', or 'Must Have'. If no record meets the criteria and the Requirement Level is not 'Not Required', a placeholder card will be created with the defined Rule Label to guide the end user on who is needed in the Group. (Specific to Group Configurations)
Parent Rule	The parent rule to determine how a Hierarchy should be built. (Specific to Object Rule Configurations)
Active	Set to true if the Rule is ready to be evaluated to create Grouped Records

Field	Definition
Field Logic Number	This is auto generated and should be used in the Rule Logic
Use Related Object Reference	Set to true if you want to use a related object to determine the criteria for the rule (Specific to Group Configurations)
Related Object Reference	The related object to evaluate for the Rule. This will only be available if Use Related Object Reference is set to true (Specific to Group Configurations)
Field	The field to be evaluated in the Rule Logic
Operator	The comparison value to evaluate if the Field against the defined Field Value
Field Value	The value that should evaluated agains the Field in the Rule Logic

Navigate to the Parent Group Configuration you want to create a Rule for
Group Configuration Create Criteria is auto generated. This will determine when the Parent Groups should be added to the Parent object based on the selected Org Chart Configuration.
Create Rule Criteria records
Define Rule Logic for the create criteria
Set the Rule to Active if there are parameters for when the parent Group should be created

Navigate to the Child Group Configuration you want to create a Rule for
Provide a Name that will help admins select the correct rule when editing rules
Provide a Label that will help end users know what is missing if the Requirement Level is not 'Not Required' and a record has not met the Rule Criteria.
Select a Requirement Level.If no record meets the criteria and the Requirement Level is not 'Not Required', a placeholder card will be created with the defined Rule Label to guide the end user on who is needed in the Group.
Create Rule Criteria records
Define Rule Logic for the criteria
Select Active when you are ready to have grouped records created based on the Rule Logic evaluating to true

Navigate to the Object Rule Configuration you want to create a Rule for
Provide a Name that will help admins select the correct rule when editing rules
Provide a Parent Rule if creating a Rule Hierarchy and it is not the top level Rule.
Create Rule Criteria records
Define Rule Logic for the criteria
Select Active to have the rule evaluated.

NOTE: You will be limited to one rule if you are not creating a Rule Hierarchy.

Navigate to the Rule you want to create Rule Criteria for
Select Use Related Object Reference if you want to use a related object to evaluate (Specific to Group Configurations)
Select a Related Object to evaluate if Use Related Object Reference is true (Specific to Group Configurations)
Select the Field to be evaluated
Select the Operator that should determine how to evaluate the Field against the Field Value
Select or enter the Field Value that should be evaluated