# Expere Engine and Tools Change Log Entries

## Form tagline enhancement

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

Previously, the tagline on custom forms was set to "N," indicating that the form was not a custom form. The expected behavior is that the tagline displays a "Y" to indicate it is a custom form. A typical tagline consists of the following:

- 2014111814.3.2.3023-R20081203N; the "N" indicates that the form is base content; the "N' appeared in all instances.

This issue has been resolved; custom forms are now accurately identified with a "Y" in the tagline.

The effective date for all products within the scope of this document for this release is . This release utilizes Expere Engine version 2016.2.0.

## Expere Engine: continued enhancement of eSignatureAndFieldSupport and SignaturePointSet elements

- Type: New Feature
- Reference: PBI 393921
- Compliance Impacts: This new feature is not a compliance or regulatory issue.
- Documentation: eSignature feature overview, Using eSignature and Acroform fields

Recently, we had implemented `SignaturePointSet` and `eSignatureAndFieldSupport` element changes in PBI's 382028 / 392582. With this continued focus we have implemented the following flags for the `eSignatureAndFieldSupport` element to return X/Y coordinates:

- eSignatureCoordinatesOnly - if set to "true," eSignature fields are suppressed on the form and X/Y coordinates are returned.
- NonSignatureFieldCoordinatesOnly - if set to "true," other Non-Signatures fillable fields (textboxes and checkboxes) are suppressed on the form and X/Y coordinates are returned.

For more information, see the eSignature feature overview section on the Using eSignature and Acroform fields page.

## Logging enhancement: FATAL level added

- Type: Enhancement
- Reference: PBI 382127
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Documentation: No document impact.

## Expere Engine: document generation enhanced

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

Previously, users reported slow performance and time out issues when generating documents. These issues occurred with custom organizations where images existed at a parent level.

When a missing image existed: the system scanned the entire organization tree instead of the requested hierarchy level and incrementally scanning the levels above the original level.

This issue has been resolved; we have addressed the issue above through code changes that have replaced the previous method.

## Expere Engine: SignaturePointSet and eSignatureAndFieldSupport element changes

- Type: New feature
- Reference: PBI 382028 / 392582
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Documentation: Using eSignature and Acroform fields

In an effort to support returning XY coordinates for all fillable fields we have begun the development work. The first step in supporting this feature is creating a new element (eSignatureAndFieldSupport). This element will only pass XY coordinates for esignatures at this time. In a future release it will control XY coordinates for all fillable fields. See the Using SignaturePointSet and eSignatureAndFieldSupport section in Using eSignature and Acroform fields for details on these two elements.

## Java 8 and Saxon upgrade: DB and File System script process available

- Type: Enhancement
- Reference: PBI 376921
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Docmentation: Powershell Script

Recently, Java 8, Saxon, and stylesheet upgrades have been implemented; with these upgrades, users must run a script to remove duplicate imports for the database and file system. Click the link below to access the installation documents and scripts for the appropriate database and file system (.ZIP file).

- Remove-duplicates-docs-scripts.zip file

## .NET Runtime Required Installation Error resolved

- Type: Defect Correction
- Reference: PBI 380115
- Compliance Impacts: This defect correction is not a compliance or regulatory issue.
- Documentation: Expere System Requirements Guide

It was reported that when installing Expere Engine 2015.3.0.1355 on Windows Server 2012 R2, a .NET Runtime Required error appeared stating that .NET 4.0 was required. However, Windows Server 2012 includes .NET 4.5.1.

Users were instructed to either click OK on the error message or create the following folder: `C:\Windows\Microsoft.NET\Framework\v4.0.30319`, then remove the folder after completing the installation.

This issue has been addressed; we have removed the verification that checks the .NET version. Users can now complete the Expere Engine installation without seeing this error message or performing the workaround above.

## Expere Engine: Barcode cover sheet enhancement

- Type: Defect Correction and Enhancement
- Reference: PBI 378815
- Compliance Impacts: This defect correction/enhancement is not a compliance or regulatory issue.
- Documentation: No document impact.

When utilizing UseCoverPage with the Ancillary Barcode functionality, data within the Instance Display Name elements would overflow off the cover sheet when too long.

Note: Barcode cover sheets are added for TRID documents and static documents without space for barcodes.

This behavior has been enhanced. The Instance Display Name now wraps on the cover sheet. The following text was added to the cover sheet so recipients of the documents know to return the cover sheet with the document:

- “Please include the cover sheet with the associated document for proper processing, when document return is requested.”

## Expere Engine: Endpoint URL issue resolved

- Type: Defect Correction
- Reference: PBI 392807
- Compliance Impacts: This defect correction is not a compliance or regulatory issue.
- Documentation: No document impact.

When viewing the endpoint URL (Common/WSEndpoint) with NO transaction data, it was expected that Expere would return the results of the GetServiceInfo call; however, the SAXParser threw an exception due to the absence of data. This resulted in the GetServiceInfo call not occurring.

With the Expere 2016.1.3 hotfix, Expere now successfully returns the results of the GetService Info call when the endpoint is viewed with no transaction data.

## Expere Engine: Cash to Close calculated values provided

- Type: Enhancement
- Reference: PBI 385920 / 387587
- Compliance Impacts: This enhancement is a compliance or regulatory issue.
- Documentation: No document impact.
- User Impact: Users who rely on Wolters Kluwer Financial Services for computing totals under “Calculating Cash To Close” on the Loan Estimate are impacted. (“Txn/IntegratedDisclosuresUseExpereComputationsInd” schema point set to “True”.) Those values must be parsed and stored by the user; the stored values must be provided in the Expere transaction when calling for the Closing Disclosure to be used on Page 3 for the “Calculating Cash To Close” section.

The `ExpereResponse.xml` file now contains Cash to Close calculated values available in a new `<r:DocCustomDataItems/>` parent element and `<r:DocCustomDataItem/>` child elements. Each of these elements has a `DataItemName` attribute and number for the value.

The new Expere Engine stylesheet, `AddDocCustomDataItem.xsl`, adds these elements as `DocCustomDataItems`.

The new elements exist as children and grandchildren of the `<r:DocDescriptor/>` element. The `<r:DocCustomDataItem/>` elements contain the following `DataItemName` attribute values:

- /Txn/IntegratedDisclosuresLoanEstimateCashToCloseStoredValueAmount
- /Txn/IntegratedDisclosuresLoanEstimateClosingCostsFinancedStoredValueAmount
- /Txn/IntegratedDisclosuresLoanEstimateTotalClosingCostsStoredValueAmount

The following code snippet appears in the `ExpereResponse.xml` file:

    <r:DocDescriptor>
    		<r:DocID>PKGD.LoanEstimate</r:DocID>
    		<r:DocType>Dynamic</r:DocType>
    		<r:DocDisplayName>Loan Estimate</r:DocDisplayName>
    		<r:DocRootEntityName>INS.LoanEstimate</r:DocRootEntityName>
    		<r:DocCustomDataItems>
     <r:DocCustomDataItem DataItemName="/Txn/IntegratedDisclosuresLoanEstimateTotalClosingCostsStoredValueAmount">34287</r:DocCustomDataItem>
     <r:DocCustomDataItem DataItemName="/Txn/IntegratedDisclosuresLoanEstimateClosingCostsFinancedStoredValueAmount">-34287</r:DocCustomDataItem>
     <r:DocCustomDataItem DataItemName="/Txn/IntegratedDisclosuresLoanEstimateCashToCloseStoredValueAmount">107815</r:DocCustomDataItem>
    </r:DocCustomDataItems>
    	 </r:DocDescriptor>

## Expere Engine: Special Character handling enhanced

- Type: Enhancement
- Reference: PBI 374746
- Compliance Impact: This enhancement is not a compliance or regulatory issue
- Documentation: No document impact.

Previously, hosted and non-hosted transactions that called the Expere Engine failed when using certain special characters on static documents.

We have enhanced the Expere Engine to support the following special characters:

Newly Supported:

- 8211: en dash
- 8212: em dash
- 8304: Degree sign
- 9472: Horizontal box

Existing (Previously Supported):

- 8216: left single quotation mark
- 8217: right single quotation mark
- 8220: left double quotation mark
- 8221: right double quotation mark

Note: Dynamic documents already support special characters.

## Foundation for future platform enhancement

- Type: Enhancement
- Reference: PBI 382928
- Compliance Impact: This enhancement is not a compliance or regulatory issue.
- Documentation: No document impact.

We have laid the ground work for a future enhancement to support additional hosted platforms. However, no customer-facing changes currently exist for this change. We will provide additional information as it impacts our users in a future release.

## Expere Engine: Enhanced logging for caching and file system repository

- Type: Enhancement
- Reference: PBI 381741
- Compliance Impact: This enhancement is not a compliance or regulatory issue.
- Documentation: No document impact.

Logging has been enhanced for the caching and file system repository to help track the progress of requests; these enhancements include the RequestID, OrgID, and PackageID. This enhancement is also a result of the changes made in PBI 382041 below.

Note: This change only impacts clients using the File System.

## Expere Engine: Improved File System indexing

- Type: Enhancement
- Reference: PBI 382041
- Compliance Impact: This enhancement is not a compliance or regulatory issue.
- Documentation: No document impact.

Changes were made to the file system repository to make the indexing process more efficient.

Note: This change only impacts clients using the File System.

## Expere Engine: eSignature and AcroForm fields enhanced

- Type: Enhancement
- Reference: PBI 381106
- Compliance Impact: This enhancement is not a compliance or regulatory issue.
- Documentation: Using eSignature and Acroform fields

Previously, users could not enable or disable eSignatures or AcroForm fields for transactions.

Users can now pass eSignature and Acroform values in the AncillaryOutput of a SelectAndGenerate, Generate, and SelectGenerateAndDeliver request. For detailed information on enabling or disabling eSignature or Acroforms, see Using eSignature and Acroform fields.

## Expere Config Tool enhanced

- Type: Enhancement
- Reference: PBI 379682
- Compliance Impact: This enhancement is not a compliance or regulatory issue.
- Documentation: No document impact.

Previously, an issue existed in the Expere Config Tool utility (Important update regarding the Expere Config Tool) in the 2016.1 release. Users reported an error when launching the Expere Config Tool utility and as a result, could not update various fields.

As a workaround, we had provided instructions on how to manually update the following configuration files and various settings within these files:

The Expere Config Tool has been enhanced, consisting of the following:

- The error that prevented users from launching the Expere Config Tool utility has been resolved; users can now use this tool to update values within the configuration files above.
- The Max Cached Object field has been removed; with our recent upgrade to ehCache 2.10, users no longer need to specify how much cache needs to be allocated for a specific number of objects.

Users can access the updated Expere Config Tool utility here.

## Expere OPPSA package behavior enhanced

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

Previously, when a document was removed from base content, OPPSA stopped printing when it encountered the missing document. In some instances, the system stopped printing any remaining documents depending on where the document was located.

This behavior has been enhanced; when an OPPSA package includes a document that has been removed, an error appears stating which document must be removed from the specified package in the OPPSA product.

## Expere upgraded to Java 8 and Saxon

- Reference: PBI 302204
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Documentation: Windows Environment Software Requirements, Java Environment Software Requirements, Expere Authoring Tools.

Summary: Embedded versions of Expere .NET and Requirements Editor now utilize Java 8 and Saxon.

For more information, see the following Expere System Requirements Sections:

- Windows Environment Software Requirements
- Java Environment Software Requirements
- Expere Authoring Tools

## Java and .NET Implementation Guide consolidated

- Type: Enhancement
- Reference: PBI 372968
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Documentation: Expere Implementation Guide

We have recently consolidated the .NET and Java installation procedures to now reside in one webhelp implementation, available here: Expere Implementation Guide.

## Barcode spacing issue resolved

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

Issue: Previously, the Expere Engine reserved space for ancillary barcodes on dynamic documents even though the barcode element was not included in the .REQ file.

Solution: This issue has been resolved; when generating a dynamic document and selecting an ancillary barcode option, the document will no longer reserve space for the barcode if the .REQ file does not contain a barcode element.

This feature requires an Expere Engine update.