Mass Printing setup

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.

Set up MassPrinting

To set up the MassPrinting integration, three need to happen:

  1. You will contact MassPrinting.
  2. MassPrinting will integrate with BriteCore.
  3. You will test the integration.

Contact MassPrinting to set up the integration

To contact MassPrinting to set up the integration:

  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. Provide and grant access to BriteCore’s Printing API document, so MassPrinting can integrate with BriteCore’s printing API.

Once you sign your contract, 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.

Allow MassPrinting to 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 doesn’t 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 is 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, you need a manageable set of results.
    A manageable set of results can be returned by:

    • Passing the ignore_state parameter with a value of true.

      Note: This ignores the fact the deliverables printed

    • Scanning for one date rather than a full year.

      Note: Scanning an entire year while ignoring the print state of deliverables would result in too many results.

Test the integration

To test the integration with MassPrinting:

  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.

    Note: 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’re finished 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