2018 Release Three (3) Expere Engine and Tools Changelog

Expere Engine Release: 2018 Release Three (3)External release date is October 2018. Expere Engine build number is: 2018.3.0.2108 .

Content used for testing:

  • September 26, 2018: 2018100818.3.0.2108-N20180920N
New Features
  • See Features page for more information
Enhancements
Defect Corrections
  • None
WebSphere with Java 6 users iText error message
Summary: If you utilize WebSphere with Java 6 you may notice an iText-related error message with the latest release of Expere. This error occurs because the current iText license key is not Java 6 compatible.
Implementation Notes: Please consult the Expere Implementation Guide: WebSphere MQ Install and Setup Point to Point page for detailed information.
Updated Implementation Guide Installation Outline
  • Type: Enhancement
  • Reference: PBI 520297
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: Expere Implementation Guide
Summary: The Expere Implementation Guide - Installation Outline topic has been updated to include links for the list of installation steps to the associated topics.
Implementation Notes: This enhancement is available in the 2018 Release Three (3) of the Expere Engine. No user action is required.
SignerSignatureSequence behavior updated for static documents
  • Type: Enhancement
  • Reference: PBI 525930
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: Previously, users reported that when a static PDF was generated, only the first signature field appeared on the document when multiple instances of the same signature were required. Users were required to increment the SignerSignatureSequence value in each subsequent signature after the first occurrence manually when authoring a static document.

We have enhanced the behavior surrounding the SignerSignatureSequence in static documents to no longer require manually incremented values in multiple instances of a given signature.
Implementation Notes: This enhancement is available in the 2018 Release Three (3) of the Expere Engine.
Expanded eSign Document Detection
  • Type: Enhancement
  • Reference: PBI 518749
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: Expere Engine Tools Changelog, Expere Engine Tools User Documentation
Summary: With Expere 2018 Release Two (2) we enhanced the Expere response to include the InstanceSigningInstructions which indicates if a document is an ESign document, InkSign document, or a NoSignature document. The original Changelog can be found here.
With Expere 2018 Release Three (3) we have expanded how Expere determines a document is an eSign document. It was found some documents are dynamic in nature on when they can be eSigned or not. For example, there are some instances where a document is authored with a Notary section, but the Notary is not always included on the document once generated. This can be based on the transaction request. As a result, the Notary is either included or excluded at runtime. If the Notary is present, it is an InkSign document; however, if the Notary is excluded, it can be considered an eSign document. To make this determination Expere uses two elements. First, if the ESignature Document setting within Document Properties is set to "true," Expere looks for a second new element called SuppressESignature. If the SuppressESignature element is present, the document is set as InkSign in the InstanceSigningInstructions, requiring a physical signature.
Note: The new SuppressESignature element is authored within the document .REQ. Please refer to the Expere Engine Tools Changelog and User Documentation linked above.
Ability to generate transaction barcodes on RTF documents restored
  • Type: Enhancement
  • Reference: PBI 498686
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: You can now generate transaction barcodes on RTF-generated documents through the use of the <TaglineBarcodeDesc> element in your transaction .XML. The value within this element should represent the barcode pattern to appear on the RTF document. This enhancement modifies previous behavior where the presence of the <TaglineBarcodeDesc> element within the transaction caused it to fail.
Technical Notes: A sample request with the <TaglineBarcodeDesc> element could resemble the following:
<TaglineBarcodeDesc>Bar Code 1</TaglineBarcodeDesc>
Implementation Notes: This enhancement is available in the 2018 Release Three (3) of the Expere Engine.
Checkboxes rendered when XY coordinates are requested
  • Type: Enhancement
  • Reference: PBI 506732
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: It was reported that documents were not rendering check boxes when XY coordinates were being requested and being merged by an institution's third-party vendor. We have enhanced how Expere renders check boxes on documents; when they are merged by a third-party vendor, check boxes are not removed or missing.
Implementation Notes: This enhancement requires the 2018 Release Three (3) Expere Engine.
Document white-space reservation enhanced when using barcodes
  • Type: Feature
  • Reference: PBI 512325 / 514530
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: Previously users of barcodes found extra white-space above the tag-line was being saved when additional document text could fit on the page. Unfortunately this caused documents to print additional pages, sometimes causing increased recording costs when the documents impacted were recordable. In an effort to reduce excess white-space on documents when using barcodes, Expere now reads the barcode type being used and reserves only the space necessary to print the requested barcode.
Implementation Notes: This enhancement requires the 2018 Release Three (3) Expere Engine.
Update to Java memory settings
  • Type: Enhancement
  • Reference: PBI 440495
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: It was determined that the java memory settings specified in the web.config file (for the .NET install) were not being updated, causing server performance issues. The following java.option values were identified as requiring a value increase:
  • <java.option value="-Xms256m" />
  • <java.option value="-Xmx512m" />
These values have been updated to the following:
  • <java.option value="-Xms2048m" />
  • <java.option value="-Xmx4096m" />
Implementation Notes: This enhancement requires 2018 Release Three (3) Expere Engine update.
SignerID now returned when eSignatureWKES = True
  • Type: Enhancement
  • Reference: PBI 508688
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: Previously, when requesting ESignatureAndFieldSupport for WKES eSignatures, Expere was not returning the SignerID in the response. The SignerID is a critical piece when integrating with WKES for eSignature capture. Expere has been updated to return the SignerID when requesting ESignatureAndFieldSupport and eSignatureWKES is set to 'true.'
Note: the SignerID is also returned when ESignatureAndFieldSupport is requested and eSignatureWKES set to 'false.' This behavior has not changed.
Implementation Notes: This enhancement requires the Expere Engine 2018 Release Three (3) update.