Set up printing options

You have several different options for setting up printing:

  • Print by Policy Number.
  • Print by Policy Number, setting the order of deliverables for each policy.
  • Print by Deliverable Type.
  • Print by defined batches using deliverables grouped by Policy Number and Recipient.

Print by Policy Number

By default, deliverables in BriteCore print alphanumerically by policy number via the sort_by_policy option. Computers sort numbers differently than people.

Example: Since a computer compares 1 to 2 rather than 123 to 2, 10-2015-123 would appear before 10-2015-2.

To print by Policy Number:

  • Run #UPDATE settings SET value=1 WHERE option= ‘sort_by_policy’

Ex:

Policy listPrint order
10-2015-210-2015-1
10-2016-110-2015-123
10-2015-110-2015-2
FO12310-2016-1
HO123FO123
FO124FO124
10-2015-123HO123

Print by Policy Number and explicitly set the order of deliverables for each policy

When printing by policy number (the above option), the order of deliverables can be explicitly defined via the order option.

To print by Policy Number and explicitly set the order of deliverables for each policy:

  1. Set the order of deliverables.
  2. Run:

UPDATE settings SET value='[ \”Declaration\”, \n \”Declaration – New Policy\”, \”Declaration – Renewal\”, \”Declaration – Endorsement\”, \”Amended Billing Statement\”,\n \”Combined Billing Statement\”, \”Initial Billing Statement\”, \”Installment Billing Statement\”, \”Renewal Billing Statement\”,\n \”Notice of Reinstatement\”, \”Notice of Cancellation Non-Payment of Premium\”, \”Pre-Authorized Payment Schedule\”]’ WHERE option = ‘order’;

Notes:

  • Initial (new business) and renewal billing statements print with their respective Declarations. For that reason, they are not explicitly set in the setting.
  • Document types are matched against types in the list. For example, a custom deliverable called Cancellation Notice will match, by name, to the Notice of Cancellation Non-Payment of Premium. If a match can’t be found, the deliverable will print alphabetically by document type after deliverables found in the list have printed.

Print by Deliverable Type

Using a different combination of the above two settings, deliverables can print by type first then by policy number. In this case, new business Declarations and invoices can print for all policies in policy number order, followed by renewal Declarations and invoices for all policies in policy number order.

To print by Deliverable Type:

  1. To disable the sort_by_policy option, run:#UPDATE settings SET value=0 WHERE option=’sort_by_policy’
  2. Set the order of deliverables, and then run:
    UPDATE settings SET value='[ \”Declaration\”, \n \”Declaration – New Policy\”, \”Declaration – Renewal\”, \”Declaration – Endorsement\”, \”Amended Billing Statement\”,\n \”Combined Billing Statement\”, \”Initial Billing Statement\”, \”Installment Billing Statement\”, \”Renewal Billing Statement\”,\n \”Notice of Reinstatement\”, \”Notice of Cancellation Non-Payment of Premium\”, \”Pre-Authorized Payment Schedule\”]’ WHERE option = ‘order’;

Print by defined batches using deliverables grouped by Policy Number and Recipient

Deliverables for a given contact on a policy are merged together into one PDF file. Merged files are then printed in defined batches using classifiers. Batch classifiers currently include:

  • page_range(x,y): batches where x and y are inclusive start and endpoints for the range.

    Example: page_range(1,4) will include mailings between 1 and 4 pages.

  • certified_mail: Batches based upon whether This document must be sent by certified mail is selected for a deliverable in Settings > Deliverables.
  • return_premium: Batches based upon the existence of the Return Premium Notice.
  • new_business: Batches based upon whether or not the mailing contains a new business Declaration or invoice.
  • billing: Batches based upon whether the mailing contains a billing statement.

Conditions are evaluated in Python. Given this, classifiers can be combined using logical operations that follow this order of operation: parenthesis, not, and, then or. For example, a batch setup of billing and page_range(1,2) would print mailings that are 1-2 pages and contain a bill, but not new business.

Initial Setup

To configure the setup:

  1. Enable the sort_by_policy setting by running #UPDATE settings SET value=1 WHERE option=’sort_by_policy’
  2. Set the order of deliverables, which defines the order of deliverables in the merged PDF, and then run
    UPDATE settings SET value='[ \”Declaration\”, \n \”Declaration – New Policy\”, \”Declaration – Renewal\”, \”Declaration – Endorsement\”, \”Amended Billing Statement\”,\n \”Combined Billing Statement\”, \”Initial Billing Statement\”, \”Installment Billing Statement\”, \”Renewal Billing Statement\”,\n \”Notice of Reinstatement\”, \”Notice of Cancellation Non-Payment of Premium\”, \”Pre-Authorized Payment Schedule\”]’ WHERE option = ‘order’;
  3. Enable the merge_docs_by_recipient_and_pol by running#UPDATE settings SET value=1 WHERE option=’merge_docs_by_recipient_and_pol’
  4. Set the batches using the available classifiers, and then run
    Info: When updating batches, use a JSON parser.#UPDATE settings SET value = [ {
    “name”: “New Policies”,
    “condition”: “new_business”,
    “comment”: “Mailings with new business declarations.”
    },
    {
    “name”: “Bills w/ 1 page”,
    “condition”: “billing and page_range(1,1)”,
    “comment”: “Mailings that are 1 page long and contain a bill, but not a new business dec.”
    },
    {
    “name”: “2-5 page bills, standard mail”,
    “condition”: “billing and page_range(2, 5) and not certified_mail”,
    “comment”: “Mailings that are 2-5 pages containing a bill, but not documents which must be sent via certified mail, or a new business declaration.”
    },
    {
    “name”: “2-5 page bills, certified mail”,
    “condition”: “billing and page_range(2, 5) and certified_mail”,
    “comment”: “Mailings that are 2-5 pages containing a bill, documents which must be sent via certified mail, but not a new business declaration.”
    },
    {
    “name”: “Contrived Example”,
    “condition”: “not billing and (page_range(6) or return_premium())”, “comment”: “Mailings that do not contain a bill and are either 6 pages or more in length or contain a return premium notice, but do not contain a new business declaration.”
    }
    ] WHERE option=’batches’

Important information

General notes:

  • Forms are included in the merged PDF file but only for the primary named insured
  • Along with being merged, each individual document will be forced to have an even page count. This is to prevent forms from being printed on the back of other forms if duplexed printing is used
  • The agency print hawk report will contain the individual policy documents as pictured above and not the combined mailing deliverable

Attachments tab of the policy:

  • Each merged PDF file will appear in a new Mailings folder within the policy’s Attachments tab
  • The Mailings folder is locked by default (files.private=1), which means agents can neither see the folder nor its contents
  • Individual deliverables follow the print state of the merged document to ensure agency print hawk emails and InsVista notifications continue to function
  • Any documents that can’t be merged will print as an individual file and its print state will update accordingly