 |
| Release Notes Overview | |
Required Expere Engine Update for Ancillary Output Barcode Users and the October 3, 2015 TILA/RESPA Integrated Disclosures.
When ancillary barcodes are used, note, there are some documents that do not allow for barcodes, including the TRID documents: Loan Estimate, Loan Estimate Addendum, Closing Disclosure, Closing Disclosure Addendem, Closing Disclosure – Seller Only, Closing Disclosure - Seller Only Addendem, and the Written List of Providers.
If you are not using ancillary barcodes, the TRID documents are not affected by this issue.
The 2015.1 Expere Engine release includes an important update for users of the ancillary output barcodes to prevent barcodes from printing on documents in which space for the barcode is not available. The new TILA-RESPA Integrate Disclosures do not have space to accommodate a barcode. This update stops the ancillary output barcode from printing over other information that is required.
The 2015.1 Expere Engine release is a required updated for use with the TILA/RESPA Integrate Disclosures if ancillary output is used to generate barcodes.
If the ancillary output is being used to generated barcodes, this update must be used with the new Expere TILA/RESPA Integrated Disclosures which are effective Aug 1, 2015. This includes the following documents: Loan Estimate, Loan Estimate Addendum, Closing Disclosure, Closing Disclosure Addendum, Closing Disclosure-Seller Only, Closing Disclosure-Seller Only Addendum, and the Written List of Providers. These new Integrated Disclosures do not have space to accommodate a barcode. These forms use a modified tagline at the bottom of each page of the document due to the requirement of matching the model form and the space constraints that presents. As a result of having to match the model form, there is insufficient space to include a barcode. This update stops the ancillary output barcode from printing over other information that is required. The CFPB has been very specific that their models are to be followed precisely.
Users who have installed the 2015.1 Expere Engine release may encounter an issue when attempting to assemble content. Users should install the Expere Engine 2015.1.1 hotfix to avoid these issues. Depending on whether or not they have eSignatures turned on or off, Expere users with content coded for eSignature functionality will be at risk for this error. Users will receive an exception error if data is not passed to the SignerIdentifier element (currently a required field). The document will not assemble and processing time would be impacted.
The 2015.1.1 Engine hotfix will include the solution for the eSignature/SignerIdentifier exception error, and all other features from the 2015.1 Engine Release.
Refer to the Expere Engine and Tools 2015.1. and 2015.1.1 release notes for detailed information regarding new features, enhancements, and defect corrections implemented for the Expere Engine and Tools releases.
Changes were made to the DocViewer 2015.1 and 2015.1.1 releases; refer to those release notes for detailed information.
Changes were made to DocViewer; refer to the DocViewer 2015.2.1 release notes for detailed information.
|
