The first processor of the Service Alberta Delivery Agent is the physical print job processor. This processor will run with a frequency of near-real time, which allows the processor to pick up document order items that have reached the “Ready to Delivery” status and prepare them for physical printing by applying an overlay of required elements to the PDF created by the Document Processor.
The Physical Print Job Processor provides a number of functions:
The following diagram describes the functions of the Physical Print Job Processor.
As part of the overlay, documents receive sequence numbers based on the destination address such that all documents that are destined for the same envelope receive the same sequence number. Documents can be sent to locations in Canada, United States or International and depending on the destination country, different postage will apply. For documents mailed by Service Alberta, a requirement exists for the print job’s provided documentation to identify the number of envelopes mailed by each of these three categories: Canada / United States / International. Service Alberta uses this information to submit the postage requirements to Canada Post.
Student Records and Service Alberta also use this information to assist in the reconciliation of shipping and financial billing.
Business Requirement Background:
Each printed document is overlaid with a sequence number. The sequence number given represents the envelope contents for a physical delivery. (ie. When multiple documents, such as multiple copies are destined for the same delivery address, and can physically fit in the same envelope, they are given the same sequence number). Therefore, the last sequence number represents the total number of envelopes expected for the print job.
For the purposes of determining which of the three groups an envelope is counted in, the system uses the following country names:
This information defines (names) the different types of paper that we can print to. This information is embedded in the application in a file called paperstock.xml. The definition includes the code and description. The following outlines the Description that should be used based on the paperstock code related to the document order item being printed.
|Paper Stock Code||Paper Stock Description|
A web configuration setting predetermines the number of documents to be included in a print job, to ensure that the job is not too large for transmission or would take too long to process at the printer prior to being actually printed. (Length of processing time is known as “RIP” time.)
Production and UAT environments currently set the number of documents in a print job to 1000 documents, which requires the Physical Print Job Processor to use a third party tool, PDF Toolkit (For more details see the technical documentation: [Printing Implementation-http://engage/pasi/team/Official Documents/Technical Documents/Printing Implementation.docx], and the following settings: Core.MaximumDocumentsPerPrintJob and Core.UsePdfToolboxForPrintJobs).
When the Physical Print Job Processor is ready to add the document to the print job, it will complete the following tasks:
This will allow the printing processes to segregate these order items, in a separate print job, from the “Automated Mail”, and Student Records will be tasked with manually stuffing that transcript into a different, larger envelope.
The stuffing limit is maintained in a configuration file along with other adjustable parameters for printing. The configuration technical document, Printing Implementation, is located http://engage/pasi/team/Official Documents/Technical Documents/Printing Implementation.docx.
Whenever a print job is created there is a check to see if the file system is up. This involves writing to a file called fsupcheck.txt in the root folder where print job folders reside. This file is created if it does not exist and overwritten if it does exist. The contents of the file are as follows:
2018-02-09 15-55-06 file system appears up from D-412210
The current date/time and machine name are written to the file. This file is updated whenever a new print job is created. If the file system is down at the time an exception would be thrown and the print job processor would bail and try again 15 minutes later (when it is scheduled)