Topics on this page

BritePolicies screen flow overview

The BritePolicies screen flow is a YAML or JSON configuration that lets clients customize the policy information tabs and content. The screen flow reduces the need for scrolling and is designed to present information in a clean, read-only view. To edit any information within the BritePolicies screen flow, you must create an endorsement.

BritePolicies screen flow data model

Refer to View policy Overview screen for information about the key components of the screen.

You can customize the tabs and content on the policy information page. BritePolicies displays the policy header, Overview tab, and Policy History tab by default. These tabs can’t be customized. A screen flow is used to add custom tabs to a policy screen

Refer to our BritePolicies screen flow overview for more details.

Figure 1 illustrates the BritePolicies screen flow data model.

Figure 1: BritePolicies screen flow data model.

A screen flow consists of multiple risk tabs that are divided into risk types.

The screen flow assumes a one-to-one mapping to BriteLines risk types. If you already created a tab referencing a risk type, you can’t create a second tab that references the same risk type. The screen flow will simply display a duplicate of the first tab that references the risk type. 

Note: If an optional field is left blank during quoting, it will display as blank in the screen flow.

Policy screen flow key components

Figure 2 illustrates the policy screen flow components on the UI.

Figure 2: Policy screen flow components

  1. Risks: Risk tabs are the tabs that make up the BritePolicies screen flow and display data associated with the risk(s) on a given policy. The risk type names come from the line of business (LOB). The risk type is the kind of risk associated with a policy. In a personal auto policy, examples of risks are the driver(s) and the vehicle(s). Within each risk tab, you can customize how you want to display information. You can display information with fields, in tables, on subtabs, or a combination of the three.
  2. Sections: Sections represent multiple fields that are logically related on each risk tab.
  3. Fields: Risk types that are formatted as fields must be divided into Sections that display multiple fields.
  4. Additional tabs: Risk types can be formatted into tabs and additional sub-tabs.
  5. Sub-tabs: Risk types that are formatted as tabs can be divided into subtabs. 
    1. Sub-tabs have their own format type, so subtabs can be formatted as fields or tables. 
    2. Sub-tabs that are formatted as fields can then be divided into sections. 
    3. Sub-tabs can’t be nested in subtabs.
  6. Columns: Labelled columns for each table.
  7. Rows: Customizable rows representing data points for each table.
  8. Table: Risk types that are formatted as tables render a table. You can customize the columns and rows of the table.