RaaS: Pre-Execution Rules

Have more questions? Submit a request

 

Pre-execution rules can be used to set specific conditions that a quote must meet, prior to a rating event taking place. If these conditions are not met, then the rating event will fail and the quote will be declined. 

To establish pre-execution rules, navigate to the Events and Actions section of your product. You must first have a ‘Quote Requested’ rating event set up using the RaaS rating action. Rules can be edited under the ‘Actions’ section, shown in the screenshot below.

Click on ‘Edit rules’ followed by the ‘Create Rule’ button. A box will expand allowing you to set your conditions, the instruction for when that condition is met, and any message you would like to show upon declination of the quote. Please note, that in order for this tool to function properly, it is important to keep the toggle filtered on ‘Do not run this action.’

The editor for qualifying rules consists of three sets of fields. The first and last set are the condition groups and the middle set is the operator group. 

Condition Group

The condition group consists of two fields: a dropdown list and a text box. The dropdown list represents the data source. This source may come from the product, client information, renewal data, or be a manual entry (such as an exact value or specific date). The text box will then adjust based on your selected source. For example, if policy renewal is the selected source then the text box will change to a dropdown list with renewal data fields, or if date and time is selected then the text box will change to a date entry field, etc.

Operator Group

The operator group also consists of two fields. The first dropdown contains a list of data types while the second dropdown contains the applicable operators. 

In the following example, we established a rule that all buildings must include an automatic sprinkler system in order to be eligible for coverage. If the automatic sprinkler system question is answered “No” during intake, then the quote will be declined and the “Automatic Sprinkler System is Required” message will appear in the UI.

Close up of rule: 

In the first condition group, we selected our product (Angelina Test w forms - AR BOP 2023.6.1.1) as the source and the ‘Automatic Sprinkler System’ question from the drop down list. Please note that the toggle can be used to flip between using QID’s or the drop down list to populate this field.

Since the automatic sprinkler system question applies at the building level, we select ‘Loop’ as the operator. Therefore, it will run through every iteration in the building schedule to confirm that every building added to the policy includes an automatic sprinkler system. 

Finally, the last condition group is set with an exact value of ‘No.’ This final step establishes that if any building in the building schedule answers ‘No’ to the sprinkler system, the quote will be declined and the “Automatic Sprinkler System is Required” message will appear in the UI. Please note, these fields are case sensitive and will cause errors if not entered correctly.

Once you have set up your rules, you can test them by running a quote. When you run a quote that violates the condition you created, you’ll see a declined quote with error message in your quoting window: 

Closeup of quotes:

Articles in this section

Was this article helpful?
0 out of 0 found this helpful