OpsLogic Rule Builder Explained | OpsAnalitica University

This article will explain how you use the Rule Builder to create rules.

Field	Required/Not Required	Explanation
Name	Required	Make it very easy to understand what the rule is doing. Organizations with lots of complicated checklists and rules can have lots of rules. Use a naming convention and make it clear.
Inheritable	Not Required	Allows the rule to be used by your descendant organizations. You do not have to make a rule Inheritable to have it be used in a checklist by a descendant.
Description	Not Required	This will allow you to describe the rule for people who are building checklists.
Rule Box	Required	This is where you type your rule text.
Associated Resources	N/A	This will show you each question that this rule is being used on. If there is nothing there, then the rule is not being used and could be deleted.

The OpsLogic Rule Builder uses IntelliSense in its code editor. This is a self-documenting system that limits your ability to only use variables and code operators that will work for the type of rule you are working on. Plus each variable has an offset on there that will define the variable's data type and what you can do with it from a coding perspective. If you have a scripting background, this will be very welcoming and familiar.

The period after This. is what triggers the variables you can select in the first box. When you select a Variable there will be a little arrow on the right margin. If you click that arrow it will expose the explanation text.

The rule builder does have error handling and will not let you create or save a rule that doesn't meet the code standard.
You would have to fix the script to clear the error and use the rule.

Next Section