2016.2 Expere Engine and Tools Changelog Entries

New Features

Enhancements

Defect Corrections

.NET Runtime Required Installation Error resolved
  • Type: Defect
  • Reference: PBI 380115
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: Expere System Requirements Guide
Issue: 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.
Solution: 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.
Implementation Notes: This defect correction is available in the Expere Engine 2016.2 release.
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 Impacts: No documentation impact
Issue: 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.
Solution: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.”
Implementation Notes: This feature is available in the Expere Engine 2016.2 release.
Expere Engine: Endpoint URL issue resolved
  • Type: Defect
  • Reference: PBI 392807
  • Compliance Impacts: This defect correction is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: 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.
Solution: 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.
Implementation Notes: This defect correction is available in the Expere Engine 2016.2 release.
Expere Engine: Cash to Close calculated values provided
  • Type: Enhancement
  • Reference: PBI 385920 / 387587
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation 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.
Summary: 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
Technical Notes: 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>
Implementation Notes: This enhancement is available in the Expere Engine 2016.2 release.
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 Impacts: eSignature feature overview
Summary: 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.
Implementation Notes: This new feature is available in the Expere Engine 2016.2 release.
Expere Engine: document generation enhanced
  • Type: Defect
  • Reference: PBI 395280
  • Compliance Impacts: This defect correction is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: 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.

Solution: This issue has been resolved; we have addressed the issue above through code changes that have replaced the previous method.
Implementation Notes: This defect correction is available in the Expere Engine 2016.2 release.
Expere Engine: SignaturePointSet and eSignatureAndFieldSupport element changes
  • Type: New Feature
  • Reference: PBI 382028 / 392582
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: 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).
Java 8 and Saxon upgrade: DB and File System script process available
  • Type: Enhancement
  • Reference: PBI 376921
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: Installation instructions; Powershell and SQL scripts available on your media release
Summary: 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. The scripts are available on your release media.
Implementation Notes: This enhancement is available in the Expere Engine 2016.2 release.
Expere Engine: Special Character handling enhanced
  • Type: Enhancement
  • Reference: PBI 374746
  • Compliance Impacts: This enhancement is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: 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
Implementation Notes: This enhancement is available in the Expere Engine 2016.2 release.
Foundation for future platform enhancement
  • Type: Enhancement
  • Reference: PBI 382928
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: 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.
Implementation Notes: This enhancement is available in the Expere Engine 2016.2 release.
Expere Engine: Enhanced logging for caching and file system repository
  • Type: Enhancement
  • Reference: PBI 381741
  • Compliance Impacts: This enhancement is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: 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.
Implementation Notes: This enhancement is available in the Expere Engine 2016.2 release.
Expere Engine: Improved File System indexing
  • Type: Enhancement
  • Reference: PBI 382041
  • Compliance Impacts: This enhancement is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: 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.
Implementation Notes: This enhancement is available in the Expere Engine 2016.2 release.
Expere Engine: eSignature and AcroForm fields enhanced
Summary: Previously, users could not enable or disable eSignatures or AcroForm fields for transactions.

Users can now configure the bsi.properties field to enable or disable eSignature and AcroForm fields in the AncillaryOutput of a SelectAndGenerate or Generate request.

Implementation Notes: This enhancement is available in the Expere Engine 2016.2 release.
Expere Config Tool enhanced
  • Type: Enhancement
  • Reference: PBI 379682
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: Previously, an issue existed in the Expere Config Tool utility 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.

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.

Implementation Notes: This enhancement is available in the Expere Engine 2016.2 release.