2019 Release Two (2) Expere Engine and Tools Changelog

Expere Engine Release: 2019 Release Two (2)External release date is November 2019. Expere Engine build number is: 2019.2.0.2685.

Content used for testing:
  • September 26, 2018: 2019111419.2.0.2685-N20190326N
New Features
Enhancements
Defect Corrections
Expere Config Tool removed from release media
  • Type: Enhancement
  • Reference: PBI 583886
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: It was determined that the Expere Config Tool was missing certain settings and did not serve a useful purpose when using Expere. As a result, we have removed the Expere Config Tool from the release media, and this option is no longer available to install through the Expere.NET installer.
Implementation Notes: This enhancement is available in the 2019 Release One (1) of the Expere Engine.

Static documents now honor eSignature setting

  • Type: Defect
  • Reference: PBI 580130
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: Previously, the Expere response returned <XCoordinate> and <YCoordinate> values when a static document was not marked eSignable.
Note: eSignable is a setting within the REQ properties that can be identified at the time of authoring.

For example:

<r:SignaturePoint>
<r:IncludeDate>false</r:IncludeDate>
<r:PageNumber>2</r:PageNumber>
<r:PageOrder>1</r:PageOrder>
<r:Height>36.0</r:Height>
<r:Width>198.0</r:Width>
<r:SignatureText>Jane eSignature</r:SignatureText>
<r:XCoordinate>36.0</r:XCoordinate>
<r:YCoordinate>650.0</r:YCoordinate>
<r:Type>Signature</r:Type>
<r:FieldName>WKES_Signature__5</r:FieldName>
<r:Sequencing>5</r:Sequencing>
<r:SignatureRequired>false</r:SignatureRequired>
</r:SignaturePoint>
Solution: <XCoordinate> and <YCoordinate> values are no longer returned in the Expere response when a static document is not eSignable.
Implementation Notes: This defect correction requires an Expere 2019 Release Two (2) update.
Generate now honoring Document Format
  • Type: Defect
  • Reference: PBI 568694
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: The format parameter (<Format> element) was not being honored for RTF outputs when specified at a document level in the Expere Generate call. As a result, instead of generating an RTF document as specified in the request, only a PDF document was created. For example, the portion of the request that specifies an RTF output below was not honored:
<data:DocumentsToGenerate>
<data:DocumentID>PKGD.LoanAgreement-Commercial</data:DocumentID>
<data:Format>RTF</data:Format>
</data:DocumentsToGenerate>
Solution: This issue has been resolved; individual documents that were assigned an RTF value for the <Format> element now output as expected.
Implementation Notes: This defect correction is available in the 2019 Release Two (2) of the Expere Engine.
AccountNumber now returned with DiscreteParty in response
Summary: The DiscreteParty section within the Expere response file now contains the Account number in the form of a new <AccountNumber> element. This new element only appears when the Account number is specifically authored in the content. This enhancement was requested so documents could be assigned to a corresponding account.
Implementation Notes: This enhancement is available in the 2019 Release Two (2) of the Expere Engine.
Expere.NET Installer updated with OPPSA installation screens
Issue: A user reported that the Expere.NET installer was missing the following screens when installing the Expere Organization Policy and Product Setup Administration component:
  • Destination Folder
  • Installation URL

The OPPSA User Guide has been updated with the missing screens and contextual information.

Implementation Notes: This defect correction requires an Expere 2019 Release Two (2) update.
WKES field name updated when "Multiline" attributes used
  • Type: Enhancement
  • Reference: PBI 572310
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: A need existed to identify a WKES fillable field that contained multiple lines in the field name.

As a result, when content has been authored to include a multline field with WKES fillable fields, the field name now reflects the use of a "Multiline" attribute; for example: WKES_Multiline_email_M_#, where "Multiline" reflects the Field Type.

Implementation Notes: This enhancement is available in the Expere 2019 Release Two (2).
SignerID behavior enhanced when used with DiscreteParty
  • Type: Enhancement
  • Reference: PBI 567610
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: Users reported that the <SignerID> element value was being used to populate the <DiscretePartyID> element. The expected behavior is if the <DiscretePartyID> element contains a value, the <SignerID> element value should not override it. We have updated Expere to ignore the <SignerID> element when a <DiscretePartyID> value is present.
Implementation Notes: This enhancement is available in the Expere Engine 2019 Release Two (2).
Support for IDAutomation MICR font added
  • Type: Enhancement
  • Reference: PBI 573288
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: The Expere Engine now supports IDAutomation MICR font as a bank checking font for dynamic and static documents. We have embedded this font when generating documents and is available in the Expere 2019 Release Two; no user action is required.
Implementation Notes: This enhancement is available in the 2019 Release Two (2) of the Expere Engine.
User documentation: Expere .NET installation section updated in Implementation Guide
Summary: The Expere .NET installation section of the Expere Engine Implementation Guide has been updated to reflect the following changes to the overall installation process:
Implementation Notes: This enhancement is available in the Expere Engine 2019 Release Two (2).
PostProcess API behavior enhanced for use with DocSet
  • Type: Defect
  • Reference: PBI 570025
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: A user reported that after installing Expere 2019 Release One, they could view individual .PDF documents, but not merged or combined PDF documents. It was determined that our PostProcess API did not allow users to combine encrypted .PDF files when using a <DocSet/> element in the Expere request.
Solution: This issue has been resolved; the PostProcess API works with encrypted PDFs using the <DocSet/> element.
Implementation Notes: This defect correction requires an Expere Engine update.
Note: AES 256-bit encryption is not supported in Expere. Use 128-bit or lower.
Expere no longer supporting TLS 1.1
  • Type: Enhancement
  • Reference: PBI 566093
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No document impact
Summary: As of the 2019 Release Two, Wolters Kluwer no longer supports TLS 1.1 for use with the Expere Engine due to outdated security algorithms and cryptosystems. It is required that you enable 1.2. If you do not, callback functionality could be compromised.
Implementation Notes: Upgrade to TLS 1.2 or higher, then disable TLS 1.1 for all requests being sent to Expere. This enhancement is deployed in the 2019 Release Two of the Expere Engine.