Home > Lines >

Use shell tools

Shell tools are for BriteCore use only and can be accessed in the lines section of the BriteCore shell.

Copy_Line_Items

Copy line items from one policyType to another.

Note: The rateChainRefs aren’t copied.

To copy line items from one policy type to another, use the following command:

Pick an effective date to copy from:

Pick a business location to copy from:

Pick a policy type to copy from:

Pick an effective date to copy to:

Pick a business location to copy to:

Copy Line Items from:

Copy_Policy_Type

Copy a policy type to a new effective date or another state. Be sure to create the line of business for the new effective date or state before using this command.

Note: Enter the dates in the YYYY-MM-DD format.

To copy a policy type, use the following command:

Policy Type Name:

Effective Date to Copy From:

Current Business Location State Abbv.:

Effective Date to Copy To:

Business Location State Abbv. to Copy To:

(Y/N) Are you sure you wish to do this?

Copy_Underwriting_Rules

Copy underwriting rules from one business location to another.

Note: The underwriting_rules_effects.target_ids and underwriting_rules_triggers.policy_type_item_ids may be inferred based on the script matching names in the origin and destination policy types or the user manually choosing it.

To copy underwriting rules, use the following command:

Pick an effective date to copy from:

Pick a business location to copy from:

Pick a policy type to copy from:

Pick an effective date to copy to:

Pick a business location to copy to:

Create_Builderdiff_Mapping

Creates a Builderdiff_Mapping to supply Persistent Builder with an explicit change.

BriteCore uses several different types of mappings:

  • category
    • Used when a category’s name changes.
  • category_option
    • Used when a coverage’s option(s) changes, such as when 1 Family and 2 Family becomes 1-2 Family.
  • coverage
    • Used when a coverage’s name changes, such as when Total Premium Credit becomes Premium Range Credit.
  • input_type
    • Used when a supplemental question changes its input type, such as when a single line question becomes a multi-line question.
  • policy_type
    • Used when policy type’s name changes, such as when Homeowner’s – Form 2 becomes Homeowners.
  • sub_line
    • Used when subline’s name changes, such as when Homeowner’s – Form 2 becomes Homeowners.
  • supp_question
    • Used when a supplemental question’s name changes, such as when Describe location becomes Address/Legal Description of Location.
  • deductible_removed
    • Used when the deductible’s rate object is dropped from an item’s rate chain.

Delete_Item

Hard-deletes a policy type item.

To delete a policy type item, use the following command:

Line Item Id:

Delete_Lob

Hard-deletes a line of business and everything related to it (policy type items, sublines, etc.).

To delete a line of business, use the following command:

Line Name:

Effective Date (YYYY-MM-DD or “all”):

Business Location State Abbv.(MO or “all”):

Export_Line

Exports a line that can be imported into a different BriteCore site. This is a good tool to use to build demo sites or templates.

To export a line, use the following command:

Policy Type Name:

Effective Date to Copy From: (YYYY-MM-DD)

Current Business Location State Abbr.:

Email to mail the export to: (optional)

(Y/N) Are you sure you wish to do this?

Import_Implementation_Notes

This tool was designed to assist with implementation by importing client notes into BriteCore for each policy. The tool allows clients to import information from an Excel spreadsheet into Policy Notes.

BriteCore staff can access the support tool:
policies >> help import_implementation_notes.

Clients can provide the following columns of information:
[COLUMNS] = [Date Converted | Policy Number | Note Title | Note Content]

Import_Line

Imports a line from a JSON export file.

JSON object import/export structure:

  • policy_types
    • policy_type
    • sub_lines
    • line_item_groups
    • policy_type_items
      • pt_item
      • item_question_groups
      • item_questions
      • x_line_item_groups_items
      • rate_chain_refs
  • lines
  • system_tags
    • underwriting_rules
      • underwriting_rule
      • underwriting_rules_effects
      • underwriting_rules_triggers
    • files
      • x_policy_type_items_docs
      • X_policy_types_docs

To import a line, use the following command:

Filepath to export document:

Effective Date to Copy Line Into: (YYYY-MM-DD)

Current Business Location State Abbv.:

(Y/N) Are you sure you wish to do this?

Remove_Builderdiff_Mapping

Deletes a user-chosen Builderdiff_Mapping.

To remove BuilderDiffMapping, use the following command:

Mapping Type: (see help for options and examples)

The name of the object in the current eff date:

The name of the new object:

(Y/N) Are you sure you wish to do this?

Replace_Unicode

Replaces Unicode in the chosen table/column.

To replace Unicode, use the following command:

Table to Clean Up (use model): ex: PolicyTypeItem

Column to Clean Up : ex: name

(Y/N) Are you sure you wish to do this?

Show_Broken_Underwriting Rules

Returns a list of rules with either broken triggers or effects.

To show broken underwriting rules, use the following command:

Policy Type ID (None for all policy types):

(N) Just show rules that are broken due to triggers on items that allow multiples? (Y/N):

Export and import a line of business

Content analysts (CAs), developers, and other staff at BriteCore can export lines of business from a client site and import the data to a test site. Staff can also use shell tools to export and import a line of business.