2021 Release One (1) Expere Engine and Tools Changelog

Expere Engine Release: 2021 Release One (1)External release date is August 2021. Expere Engine build number is: 2021.1.0.1526.

New Features
Enhancements
Defect Corrections

Supplemental 2021.1.2 release

Note: The supplemental 2021.1.2 release has been posted to the Product Download Site. Click the Expere Engine tab in the left navigation pane and select 2021.1.2 release.
Expere Engine: Log4j updated
  • Type: Enhancement
  • Reference: PBI 706305, 706658
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: We previously informed you that the Expere Engine was using a vulnerable version of Log4j that was determined to have a security risk. As a result, we upgraded the Expere Engine to Log4j version 2.15.0. On December 14th, Apache confirmed another medium vulnerability that required an update to Log4j version 2.16.0. They have since confirmed an additional critical vulnerability on December 20th that requires an update to version 2.17.0. As a result, we have upgraded the Expere Engine to use Log4j version 2.17.0.
User action: For the latest Expere install, which includes an updated Expere Testing System with the Log4j security finding corrected, refer to the Product Download Site (PDS) and download the 2021.1.2 Engine. Consult your Professional Services representative or the Expere Implementation Guide for installation assistance.
Implementation Notes: This enhancement is available in the supplemental 2021.1.2 Release posted on the Product Download Site.
Expere Testing System: Log4j updated
Summary: It was identified that the Expere Testing System was using a vulnerable version of Log4j that was determined to have a security risk. We have corrected the security finding and created an Expere release containing an updated version of the Expere Testing System which includes the security remediation. Users will notice that previous versions of Expere contained an ExpereTestingSystem.ear and ExpereTestingSystem.war file. With the latest release of Expere, only the .WAR file is created.
User action: For the latest Expere install, which includes an updated Expere Testing System with the Log4j security finding corrected, refer to the Product Download Site (PDS) and download the 2021.1.2 Engine. Consult your Professional Services representative or the Expere Implementation Guide for installation assistance.
Note: Consult the Expere Implementation Guide: Installation with WebSphere topic to upgrade the Log4j2.xml and ExpereTestingSystem.properties files.
Implementation Notes: This enhancement is available in the supplemental 2021.1.2 Release posted on the Product Download Site.

Supplemental 2021.1.1 release

Expere Engine: Log4j updated
  • Type: Enhancement
  • Reference: PBI 705799
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: It was identified that the Expere Engine was using a vulnerable version of Log4j that was determined to have a security risk. We have corrected the security finding and created an Expere release containing an updated Expere Engine which includes the security remediation. For an updated Expere Engine to correct the Log4j security finding, refer to the Product Download Site (PDS) and install the 2021.1.1 Engine which contains the security correction. Consult your Professional Services representative or the Expere Implementation Guide for installation assistance.
Implementation Notes: This enhancement is available in the supplemental 2021.1.1 Release posted on the Product Download Site.

2021.1 release

Fee Merging behavior enhanced
  • Type: Defect
  • Reference: PBI 684633
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: A user reported that Default Data for Late Fee and Prepayment Penalty information resulted in duplicate Late Fee information when merging Default Data with the request transaction. Subsequently, this duplicate information resulted in an error in DocViewer.
Solution: This issue has been addressed: policies containing Late Charges and Prepayment Penalties exist now merge correctly into the request transaction.
Implementation Notes: This defect correction is available in the 2021 Release One of the Expere Enginesupplemental July release of Hosted Expere / Expere Document Services.
WCAG 2.0: Empty figure tags / blank paragraph behavior enhanced
  • Type: Enhancement
  • Reference: PBI 684124
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: Users reported an issue with empty Paragraph and Figure tags when running a full accessibility check in Adobe Acrobat. It was determined that the stylesheet used when generating the document inserted duplicate blocks that did not contain any content.

This behavior has been enhanced: empty Paragraph and Figure tags are no longer created in the tag tree and will not cause a full accessibility check to fail.

Implementation Notes: This enhancement is available in the supplemental July release of Hosted Expere / Expere Document Services2021 Release One of the Expere Engine.
Barcodes: barcodeInter25 format enhanced
Summary: It was discovered that barcodeInter25 requires an even number of characters in the barcode pattern in order to function properly; as a result, when an odd number of characters is provided for a barcodeInter25 barcode type, we are prepending a 0 to the barcode.
Note: as a reminder, BarcodeInter25 is a numeric-only barcode type.
Implementation Notes: This enhancement is available in the Expere Engine 2021 Release One.
WCAG 2.0: Waiver of Grantors Rights-GA tagging and screen reading enhanced
  • Type: Enhancement
  • Reference: PBI 680864
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: The following WCAG 2.0-related items have been addressed regarding the Waiver of Grantors Rights-GA document:
  • Tagging was incorrect: the tag for Notary Commission Expiration Date - OBJR should have appeared after the tags for Date and Seal.


  • The Adobe Acrobat screen reader read sections in the wrong order: the screen reader read the field for Grantor on page one, then began reading the field next to My Commission expires and then read page one items four and five.

This issues have been resolved; tagging and screen reading behaviors have been enhanced to act as expected.

Implementation Notes: This enhancement is available in the 2021 Release One of the Expere EngineJuly release of Hosted Expere / Expere Document Services.
WCAG 2.0: DocumentReference / hyperlink tagging and screen reader behavior enhanced
  • Type: Enhancement
  • Reference: PBI 678807
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: The following WCAG 2.0-related items have been addressed (applicable document appears in bold next to the bulleted issue):
  • Credit Agreement HE Variable Draw Repay-TX document: the Adobe screen reader read the italicized TexasConstitution out of order; the tag for TexasConstitution was incorrect in the tag tree. These items have been resolved: TexasConstitution is now read in the correct by the screen order and appears correctly in the tag tree.


  • Welcome Approved Notice document: the tag for "www.oregonlawhelp.com" was out of position and in its own Section within the tag tree; it appeared after the tagging for the paragraph where it resided. This item has been updated; www.oregonlawhelp.com now appears in the same section with its surrounding paragraph information.


Technical Notes:
Implementation Notes: This enhancement is available in the June release of Hosted Expere / Expere Document Services2021 Release One of the Expere Engine.
eOriginal > Upload feature: Sequence order added to response
Summary: As a part of our eOriginal Upload feature, the Expere response has been updated to include <Sequencing> and <FieldName> in the response under SignaturePointSet. This will be returned for all fillable field types when either ESignatureAndFieldSupport or ESignatureCoordinates is provided in the request (I.e. ESignatureAndFieldSupport and / or ESignatureCoordinates = true).
Technical Notes: Sample response snippet below:
Implementation Notes: This feature is available in the April release of Hosted Expere / Expere Document Services2021 Release One of the Expere Engine.
BRE and InsertInstructions Feature: BRE returned in InstanceProperties
Summary: Expere has been updated to return Business Return Envelope (BRE) and InsertInstructions when authored in content. These indicators are used in Wolters Kluwer Hosted Expere integrations for Print delivery of document packages to indicate when a BRE or extra inserts should be included in the package when printed and mailed form Wolters Kluwer Print Fulfillment. Self-hosted Expere customers may chose to ignore these values.
Implementation Notes: This feature is available in the 2021 Release One of the Expere Engine .
Read order and signature bookmark behavior enhanced
  • Type: Enhancement
  • Reference: PBI 634558
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: Users reported the following issues:
  • The Adobe Acrobat screen reader read the Confirm Receipt section, located at the bottom of the page, before items on the same page that preceded it.

  • Signatures appeared out of order in the Bookmark navigation pane in a tagged PDF. Instead of appearing after specific heading bookmarks, they appeared before them (see screen shot below).

This behavior has been enhanced: for non-merged, single documents, the screen reader reads the items in the correct order while bookmarks appear in the correct order.

Implementation Notes: This enhancement is available in the April release of Hosted Expere / Expere Document Services2021 Release One of the Expere Engine.
Barcode scaling enhanced
  • Type: Enhancement
  • Reference: PBI 657525
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: A user reported receiving an error when using a long barcode pattern. We had previously limited the number of characters that could be entered in the <Pattern/> element within the <AncillaryOutput/> > <Barcode/> container within a request. However, we have now enhanced the <Pattern/> element to no longer limit the number of characters that could be entered. As a result, Expere has been enhanced to now support larger number of characters through scaling.
Implementation Notes: This enhancement is available in the March release of Document Generation Services2021 Release One of the Expere Engine.
Expere EngineExpere Engine / Document Generation Services: SuppressPaperDelivery element/value returned with DiscreteParty for dynamic and static documents
  • Type: Feature
  • Reference: PBI 658905658905 / 656311
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: Expere Developer Guide: DiscretePartyExpere Developer Guide: DiscreteParty; Document Generation Services Web Services: DiscreteParty
Summary: As part of feature work to integrate Hosted Expere with Wolters Kluwer E-Sign, we updated the Expere Engine to return a new SuppressPaperDelivery element (PBI 658905) and value in the DiscreteParty section of the Expere response. If this value is set to "true," a paper delivery group is not created for the particular discrete party containing the "true" value. For this particular PBI, development and testing was conducted when using static documents to ensure the SuppressPaperDelivery element and value are returned in the Expere response.
Technical Notes: Sample response code below:
<DiscreteParty>
    <SuppressPaperDelivery>True</SuppressPaperDelivery>
</DiscreteParty>
Implementation Notes: This enhancement is available in the February release of Document Generation Services2021 Release One of the Expere Engine.
Expere Engine: DefaultData fees behavior enhanced
  • Type: Enhancement
  • Reference: PBI 661929
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: Users reported that Default Data policy fees did not merge with request transaction fees; instead, they appeared after the existing fees. This behavior has been enhanced so that Default Data fees are merged with existing fees under the same fee name.

Response sample before enhancement:

Response sample after enhancement:

Note: if no fees exist on the transaction, all fees from default data are appended to the transaction; additionally, deposit fees with the same name that have fee details present will have any matching detail nodes merged.
Implementation Notes: This enhancement is available in the 2021 Release One of the Expere EngineMarch release of Document Generation ServicesMarch release of Hosted Expere / Expere Document Services.
Expere Engine: Support for Font, FontSize, and Underline added for Signatures
  • Type: Enhancement
  • Reference: PBI 645801
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: Expere Document Services Web Services Guide: SignaturePointExpere Developer Guide: SignaturePointExpere Developer Guide: SignaturePoint
Summary: It was determined that Expere needed to support specifying a specific font and its size, and the ability to add an underline to a Signature and Signature Date field. As a result Font, Font Size, and Underline parameters are now supported for the SignatureField and SignatureDateField elements.
Implementation Notes: This enhancement is available in the January release of Hosted Expere / Expere Document Services2021 Release One of the Expere Engine2021 Release One (1) of the Expere Engine.
Expere Engine: Response updated to return EmailAddress in DiscreteParty
  • Type: Enhancement
  • Reference: PBI 625391
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: Expere Developer Guide: DiscreteParty
Summary: The DiscreteParty parameter has been updated to return an Email Address value (EmailAddress) in the Expere response file when provided in a request transaction.
Technical Notes: Sample request: 
<Borrower index="1">
			<FirstName>Betty</FirstName>
			<MiddleName>P</MiddleName>
			<LastName>Borrower</LastName>
			<MailingAddressCity>Borrower City</MailingAddressCity>
			<MailingAddressState>MN</MailingAddressState>
			<MailingAddressStreetAddr1>456 Borrower Address</MailingAddressStreetAddr1>
			<MailingAddressPostalCode>56565</MailingAddressPostalCode>
			<EmailAddress>borroweremail@test.com</EmailAddress>
			<DebtCollectionAttorneyAddress>123 Attroney Address</DebtCollectionAttorneyAddress>
			<DebtCollectionAttorneyName>Jane Attorney</DebtCollectionAttorneyName>
			<DebtCollectionAttorneyCity>Attorney City</DebtCollectionAttorneyCity>
			<DebtCollectionAttorneyID>123</DebtCollectionAttorneyID>
			<DebtCollectionAttorneyState>MN</DebtCollectionAttorneyState>
			<DebtCollectionAttorneyPostalCode>55555</DebtCollectionAttorneyPostalCode>
			<DebtCollectionAttorneyEmailAddress>attorneyemail@mail.com</DebtCollectionAttorneyEmailAddress>
		</Borrower>

Sample response:

<r:DiscreteParties>
			<r:DiscreteParty>
				<r:ID>123</r:ID>
				<r:Name>Jane Attorney</r:Name>
				<r:AddressLine1>123 Attroney Address</r:AddressLine1>
				<r:City>Attorney City</r:City>
				<r:State>MN</r:State>
				<r:ZipCode>55555</r:ZipCode>
				<r:MailingMethod>First Class</r:MailingMethod>
				<r:EmailAddress>attorneyemail@mail.com</r:EmailAddress>
			</r:DiscreteParty>
		</r:DiscreteParties>
Implementation Notes: This enhancement is available in the 2021 Release One of the Expere Engine.
Expere Engine: Unique identifier created for each notary block (eNotary feature enhancement)
  • Type: Enhancement
  • Reference: PBI 647196
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: As an enhancement to our eNotary feature, we have modified the Expere Engine to automatically add a SignatureUniqueIdentifier element for each field in a Notary Block; the SignatureUniqueIdentifier element now connects the fields within the Notary Block to the notary signature so the electronic delivery platform knows which fields are associated with each specific notary signature.
Note: The SignatureUniqueIdentifier element can be present as a child in the <SignaturePoint/> and in the <FillableField/> (<Fillablefield/> and <FillableCheckbox/>) set areas of the transaction request.
Technical Notes: See the following <SignaturePoint/> > <SignatureUniqueIdentifier/> code sample below:
<r:Signer>
			<r:Id>NotaryID</r:Id>
			<r:Description>Notary/r:Description>
			<r:SignaturePoints>
				<r:SignaturePoint>
					<r:IncludeDate>true</r:IncludeDate>
					<r:PageNumber>10</r:PageNumber>
					<r:PageOrder>0</r:PageOrder>
					<r:Height>36.0</r:Height>
					<r:Width>162.0</r:Width>
					<r:SignatureText>NotaryID</r:SignatureText>
					<r:XCoordinate>37.0</r:XCoordinate>
					<r:YCoordinate>307.22</r:YCoordinate>
					<r:Type>Signature</r:Type>
					<r:FieldName>SIG_Notary_1_NotaryID_true_0</r:FieldName>
					<r:SignatureRequired>true</r:SignatureRequired>
					<r:SignatureUniqueIdentifier>NotaryBlockSection1</r:SignatureUniqueIdentifier>
				</r:SignaturePoint>
Implementation Notes: This enhancement is available in the December release of Expere Document Services / Hosted Expere2021 Release One of the Expere Engine.