Learn how to use operators to build powerful, custom logic for your automation rules.
In Arive, the formula feature in Automation Rules allows you to define the precise logical expression that determines when a rule should trigger. A formula is built by combining three core components: a System Formula, an Operator, and an Information Tag. Together, these elements define what data to evaluate, how to compare it, and what value it must meet. If the formula's logic returns "true," the automation runs. This article focuses on operators, which are the engine of your formula's logic.
Formulas are also supported for use with the Set Value action, to write a calculated value to certain supported field.
Note: You must have privileges to create or edit Automation Rules. If you do not have access, please reach out to your account administrator.
Key Benefits and Use Cases
- Automate Complex Calculations: Perform mathematical operations on the fly using information tags to derive new values within your rules.
- Create Precise Triggers: Move beyond simple triggers by defining exact, multi-faceted conditions. For example, trigger a rule only when a loan amount is above a certain threshold and the appraisal has been ordered.
- Improve Workflow Efficiency: Reduce manual checks and balances by building rules that automatically evaluate dates, values, and other loan criteria.
Understanding Formula Components
A formula is structured as a logical statement. Let's break down the three parts:
- System Formula: This is the starting point of your expression. It's the data field you want to evaluate. In the example below, "Funding Date" is the System Formula.
- Operator: The operator is the action word that defines the comparison or calculation. In the example, "is less than" is the operator.
- Information Tag: This is a token that represents a dynamic value from the loan file. You use it as the value to compare against. `{{ClosingDate}}` is the Information Tag in the example.
Resulting Formula: {{loanKeyDates.expectedFundingDate}} is less than {{ClosingDate}}
Available Operators and Examples
Operators define how values interact within a formula. They tell the system what type of logical or mathematical calculation to perform. They can be grouped into two main categories: Comparison and Mathematical.
Comparison Operators
These operators are used to compare one value to another. The result will be either true or false.
- is greater than:Checks if the first value is larger than the second.Use Case: Alert a manager if a loan amount exceeds $1,000,000.
Formula: {{scenario.baseLoanAmount}} is greater than 1000000 - is greater or equal:Checks if the first value is larger than or equal to the second.Use Case: Trigger a review if the interest rate is 5% or higher.
Formula: {{scenario.rate}} is greater or equal 5.0 - is less than:Checks if the first value is smaller than the second.Use Case: Send a notification if the down payment is less than 20%.
Formula: {{scenario.downPaymentPercentage}} is less than 0.20 - is less or equal:Checks if the first value is smaller than or equal to the second.Use Case: Escalate if an appraisal is ordered on or before the application intake date.
Formula: {{loanKeyDates.appraisalOrderedDate}} is less or equal {{milestoneDates.appIntakeLoan}} - is equals:Checks if two values are exactly the same.Use Case: Start a specific workflow for all loans in the "broker" channel.
Formula: {{scenario.loanChannel}} is equals "broker" - is not equals:Checks if two values are different.Use Case: Create a task for all loans that are clear to close on a date different then the estimated closing date.
Formula: {{milestoneDates.clearToClose}} is not equals {{loanKeyDates.estimatedClosingDate}}
Mathematical Operators
These operators are used to perform arithmetic calculations.
- Addition (+):Used to add two or more numeric values.Use Case: Calculate the total loan amount including broker compensation.
Formula: {{TotalLoanAmount}} + {{BrokerCompensation}} - Subtraction (-):Used to subtract one value from another.Use Case: Determine the net loan amount after subtracting broker fees.
Formula: {{TotalLoanAmount}} - {{BrokerCompensation}} - Multiplication (*):Used to multiply two values.Use Case: Calculate a custom value to fill in a custom field.
Formula: {{productAndPricing.loanAmount}} * 0.06 - Division (/):Used to divide one value by another.Use Case: Determine if Compensation is within a specified threshold.
Formula: {{BrokerCompensation}} / {{TotalLoanAmount}} is greater then 0.2
Troubleshooting and Best Practices
Best Practices
- Always double-check that the data types in your comparison are compatible (e.g., compare a date with a date, a number with a number).
- Use Information Tags whenever possible to make your rules dynamic and adaptable to each loan file.
- Regularly review your automation rules to ensure they are still aligned with your current workflow and business needs.
Troubleshooting
If you encounter an error or your rule does not trigger as expected:
- Verify that the information tags you are using are correct and contain the data you expect.
- Break down the formula into its parts. Manually check the value of the System Formula and the Information Tag in a sample loan to see if the logic holds true.
- Ensure there are no typos in any manually entered values (like "Retail" or a specific date).
FAQs
What is the difference between a System Formula and an Information Tag?
A System Formula is the field that initiates the logical check—it's what you are evaluating. An Information Tag is a placeholder for a dynamic value that you are comparing against. Typically, the System Formula is the first element in the expression, and the Information Tag is the last.
Can I combine multiple operators in one formula?
A single formula expression is designed to evaluate one condition. To build more complex logic involving multiple conditions (e.g., Amount is greater than X AND Rate is less than Y), you can chain multiple conditions in the Automation Rule setup, with each condition having its own formula.