# Change Log

These change log entries are specific to changes made to DocPrep for the 2016.4 release.
The effective date for all products within the scope of this document for this release is March 10th for the UAT environment and March 17th for the Production environment.

## Image Changes

- Issue: Logos/images supported on documents
- Reference: PBI 366180
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.

Summary: This enhancement allows DocPrep customers to have personalized logos or images placed within their documents, for personalizing the documents to their institution.

These enhancements are exclusive to image updates (glyph files) representing logo images or visual indicators (arrows, text shading) requested to support branding and other design requirements.

- Added one image: Wolters Kluwer Financial Services received a request from an institution to add a new image.

## New API created for use with SDX sendPackageTRID Web Service Method

- Reference: PBI 366953
- Compliance Impacts: This new feature is not a compliance or regulatory issue.
- Documentation: DocPrep sendPackageTRID Integration Guide

A new DocPrep sendPackageTRID web service method has been implemented for use with SDX; this new method is TRID-compliant. Users can now submit TRID packages to SDX, which will calculate the expiration date/time.
Note: The sendPackageEx3 web service method will continue to be supported.

See DocPrep sendPackageTRID Integration Guide above for detailed integration information.

These change log entries are specific to changes made to DocPrep for the 2016.3 release.
The effective date for all products within the scope of this document for this release is February 4th for the UAT environment and March 1 for the Production environment.

## Transaction issues addressed

- Reference: PBI 364436
- Compliance Impacts: This defect is not a compliance or regulatory issue
- Documentation: No document impact.

Loan transactions failed during UAT testing when forms exceeded 25 pages and utilized barcodes.

The form programming was revised to correctly map the barcode to the appropriate pagination requirements of the form based on the number of totals pages generated in the print output (which is derived, in part, by the number of borrowers identified on the loan). The result is that transactions containing a barcode, and exceeding 25 pages on the print output successfully process.

## MyDocPrep: Billing Report enhanced

- Reference: PBI 357915
- Compliance Impacts: This defect is not a compliance or regulatory issue
- Documentation: No document impact.

Previously, the MyDocPrep Billing Report would not return the reports for a full month. This issue occurred when the monthly report contained a large amount of transactions.

This issue has been resolved; the MyDocPrep Biling Report now returns monthly reports containing over 250,000 transactions.

## DocPrep Workflow Processer enhanced

- Reference: PBI 351154
- Compliance Impacts: This defect is not a compliance or regulatory issue.
- Documentation: No document impact.

When the DocPrep database appeared to be overworked, timeouts occurred when calling GetNextLoansEx and GetActiveLoans stored procedures. When this exception was encountered, it immediately called the database again. This increased the total number of active processes within the database.

This issue has been resolved in the 2016.3 release.