This glossary defines BriteRules terms in the following categories:
- Rules UI
- Rule types
- Rule inputs
- Import and export
Rule Set (Project): A group of rules specific to the functionality of the category they’re placed in.
Package: The way the rules are structured within the project. Packages consist of three sections: models, framework, and decision actions.
Note: Packages aren’t used to create rules, but package information is used to create projects.
Validation rules: Validate the accuracy of quote values based on the current state of the quote.
Flow-based behavioral rules: Determine whether to show, hide, disable, or amend fields based on other fields.
Role-based behavioral rules: Determine whether to show, hide, disable, or amend fields based on the user’s role.
Underwriting rules: Trigger a decline or referral to a person, requiring either BriteCore (straight-through processing) or a user to make a decision.
Types of underwriting rules:
- Early decline
- Info/warning messages
- Referral to underwriter
Underwriting rules can:
- Run at any time.
- Run in the following ways: field-by-field, page-by-page, or at the very end.
- Include messages.
Failed rules can be displayed to the agent and underwriter.
Note: You can customize a rule’s information and message based on user role.
Straight Through Processing (STP): Provides the ability to accept a policy or claim or changes to a policy or claim without human review.
Models: The fields, actions, data that compose the requirements within a rule.
Value-sets: A group of things you want to put under one name or category. Value-sets are used to provide a dropdown list of options within a rule, which can be options listed in a dropdown list on a quote or policy.
Note: Value-sets are created based on the sync with lines.
Templates: Predefined rules with set arguments, which are configurable.
Arguments: Parameters defined within a template that determine the capabilities of the rule, such as a When-Then statement.
Trigger actions: Determine when a rule should fire.
Types of trigger actions:
- Form-inline-change: Changing between fields on a screen.
- Form submit: Submitting a form on a screen, such as saving a newly added driver on the Driver screen.
- Form load: Entering a form on a screen.
- Page submit: Selecting Continue to move from one screen to another.
- Quote Submit: Submitting a quote.
Conditions: Provide a context of filters and rule scopes that decide if and when a rule should and shouldn’t run.
Note: In BriteRules, conditions are called Namespaces.
Import and export
Import: An import allows you to bring a rule set from your local computer into any BriteCore site.
Export: A regular export that contains only the project you selected to export.
Full export: An export that contains the project you selected to export and the project’s dependent packages.