Integrations

Integrations

MassPrinting

MassPrinting is a leading provider of document output solutions to the insurance industry. MassPrinting works closely with your internal team to provide a personalized outsourcing solution for the printing and mailing of your policyholder communications. This leads to increased internal efficiencies and cost savings for your company.

Implement MassPrinting

MassPrinting integrations take an average of one to three months, based on the complexity of the implementation and other variables. Implementation can be conducted remotely with no impact on the implementation timeframe.

Step 1: Contact MassPrinting

  1. Contact Bill Crowley at MassPrinting.
  2. MassPrinting will provide an overview of the integration process, develop a cost savings template, and discuss a pricing schedule.
  3. Review and sign a contract and statement of work (SOW).
  4. MassPrinting must integrate with BriteCore’s printing API. Provide and grant access to BriteCore’s Printing API document.

Once your contact is signed, BriteCore will generate an API key for MassPrinting. MassPrinting will have access to all API functions that appear on the api.britecore.com site with the API key. Your written agreement should indicate MassPrinting will handle your data in a secure way and only with your permission. Also, the agreement should specify that MassPrinting will only use API calls that you approve during the development phase, which are listed in the Printing API document.

Step 2: MassPrinting will integrate with BriteCore

In conjunction with the Printing API document, MassPrinting should notate the following during implementation and the initial phase of testing:

  • Within BriteCore, printing occurs after automatic nightly processing. Nightly processing does not complete at the same time each evening, so MassPrinting should retrieve the documents when {“processing”: “done”} is true within the getToBePrinted API call. Otherwise, the vendor might attempt to retrieve documents while BriteCore is still generating them.
  • When testing getToBePrinted, the result will most likely be empty. An empty result will be due to timing. Printing occurs automatically overnight and, as a result, deliverables update to a state of Printed. This means when the test is run, all deliverables will have printed for the day. To continue testing, a manageable set of results is needed. A manageable set of results can be returned by:
    • Passing the ignore_state parameter with a value of true. This ignores the fact that the deliverables printed
    • Scanning for one date rather than a full year. Scanning an entire year while ignoring the print state of deliverables would result in too many results

Step 3: Test the integration

  1. Ensure there are stock and custom deliverables scheduled to print.
  2. In Titanium Blizzard, disable Auto-print.
    Note:
    You can manually print the deliverables from Titanium Blizzard at the end of the testing process.
  3. MassPrinting should remove ignore_state from the API call, thereby scanning back a full year to pick up all unprinted deliverables. Deliverables should be retrieved when {“processing”: “done”} is true.
  4. MassPrinting will print the deliverables.
  5. Manually print deliverables from Titanium Blizzard. Titanium Blizzard will update the deliverables to Printed, so the vendor does not need to call markAsPrinted during this test.
  6. Compare the two print jobs.

Once you are done testing the integration, you can stop using Titanium Blizzard.

Note: To continue receiving the an email report containing print job information, MassPrinting will need to make the following API call:

curl -d ‘{“api_key”: “YOUR_API_KEY”, “date”: “2016-08-31”}’ https://yoursitename.britecorepro.com/api/v1/printing/sendPrintHawkEmail

Use MassPrinting

MassPrinting will retrieve and print BriteCore deliverables automatically during nightly processing. If the vendor experiences an issue and can’t print the documents, you can print the documents manually using Titanium Blizzard.