Changelog Entries - 2024

This help topic encompasses new features, enhancements, and defect corrections covering all aspects of your hosted environment, including Expere Document Services. Expere Engine, DocViewer, and Print Fulfillment (for Delivery users).

Note: Consolidated changelogs: Beginning in January 2023, all products and components used with Hosted Expere are now available within a single, consolidated set of changelogs. This means all release information for these products will be available within a single help topic, and you will no longer need to navigate to individual changelogs to locate relevant release information for each product.

The changelog is still organized by month; within each release section, we have grouped the individual changelog entries by product (feature, enhancement, and defect correction). You can still find archived changelogs for all previous releases within the Archive page.

We hope you find the updated changelog format to be an improvement to your workflow, and we look forward to continually providing you with pertinent release information while increasing our user documentation efficiency.

You may need to clear your cookies, data, and browsing history. Some users may notice that changelogs do not appear on this page. If that is the case, clear your cookies.

December

Expere: Overflow pages on Embedded PDF documents
Summary: Expere has been enhanced to support field overflow functionality on EmbeddedPDF documents through the following work items:
  • "ReduceFontAndTruncate" behavior enhanced (PBI 844525): Expere has been updated so that when ReduceFontAndTruncate is specified in the Behavior dropdown, the text font size will be reduced in size down to 8 point font at minimum. If text still does not fit at 8 point font, then the text will be truncated.
  • "PrintEntireContentOnTheOverflowPage" behavior enhanced (PBI 844739): Expere has been updated so that when PrintEntireContentOnTheOverflowPage is specified in the Behavior dropdown, the entire value specified for the source field would appear on the overflow page. If a Forwarding Message value is specified, it appears in the source field in the document.
Note: Additional development is still needed before this feature is available for use, including when generating Tagged PDF documents.
Expere: Expanding merging PDF options
Summary: we want to make you aware of an upcoming functionality that will be available in the future. As part of our effort to support merging PDF documents by Discrete Parties, the following enhancements have been made to Expere:
  • (Hosted Expere - SOAP users) EDocService WSDL updated (PBI 838402); the EDS EDocService WSDL for SOAP users has been updated to include the following new ancillary options:
    • PdfMergeDiscreteParty
    • MergedCopyPDFDiscreteParty
    • PdfMergeWithDocInstancesDiscreteParty
  • (Hosted Expere - REST users users) DocumentService REST API updated (PBI 838403); the EDS DocumentService REST API has been updated to include the following new ancillary options:
    • PdfMergeDiscreteParty
    • MergedCopyPDFDiscreteParty
    • PdfMergeWithDocInstancesDiscreteParty
  • Expere Document Services (EDS) Tool Suite updated with new discrete party options (PBI 838405): the EDS Tool Suite now displays the Merged Pdf by Discrete Party, Merged Copy Pdf by Discrete Party, and Merged PDF with Doc Instances by Discrete Party ancillary output options on the following pages:
    • Select Generate and Deliver
    • Select and Generate
    • Select / Generate

    For more information, refer to the Expere Document Services Tool Suite user guide > SERVICES pages.

Note: Additional development is still needed before it is available for use.
Expere: SmartSign Plus® integration
Summary: as part of our ongoing work to integrate SmartSign Plus® with Expere, the following functionality has been implemented for the December release:
Expere: XPath 1.0 Compatibility Mode logging updated
Summary: As part of our feature to disable XPath 1.0 Compatibility Mode while continuing to generate documents, we have increased our logging support when a transaction falls into XPath 1.0 Compatibility Mode, to include document information. An example log message would contain portions of the following (including the document name):
2024-11-25 10:34:19,087 ERROR [com.pingdynasty] [][acf5e72fac194775bb9c27d8cf362c4d][PKG.Mortgage2Closing][INS.UniformResidentialLoanApplication-M2]
Expere: monthly component upgrade
  • Type: Maintenance
  • Reference: PBI 840187
Summary: As part of a regular cadence to review and upgrade any items used with Expere Engine, we have upgraded the following components:
  • Amazon Corretto 21.0.5
Note: No user action is required.
Expere: large XML request optimization
  • Type: Maintenance
  • Reference: PBI 850716
Summary: As part of a regular cadence to review and upgrade any items used with our Expere applications, our code was optimized to better handle how our microservices handle large XML requests; no user impact is expected.

November

Expere: Overflow pages on Embedded PDF documents
Summary: Expere has been enhanced to support field overflow functionality on EmbeddedPDF documents through the following work items:
  • "ContinueOnOverflowPage" behavior enhanced when providing / not providing an overflow description (PBI 844642, 844526): EmbeddedPDFs now allow data to carry over to a "destination page" when ContinueOnOverflowPage is specified in the Behavior field in the REQ file > Field Grid > Overflow section. The overflow page is only supported as the last page of the document.

    Users can enter the following additional information:

    • When specified, the Overflow Description value defined in the REQ appears on the overflow page above the text that carries over.
    • When specified, the Forwarding message value defined in the REQ appears at the end of the source field following an asterisk (for example: *See Attached), and the remaining text in printed on the Page specified in the REQ.
Note: Additional development is still needed before this feature is available for use, including when generating Tagged PDF documents.
Expere: Expanding merging PDF options
Summary: as part of our effort to support merging PDF documents by Discrete Parties, the following enhancements have been made to Expere:
  • Document Title set to original PacketName (PBI 841992) When either a MergedCopyPDFDiscreteParty or PdfMergeDiscreteParty ancillary output is passed the merged PDF files' Document Title is set to the original PacketName. The packet name is specified in the PKG file in the content library or in EZ Config Packages and Packets.
  • Support added when Packets are authored in the PKG file (PBI 839187): Both MergedCopyPDFDiscreteParty and PdfMergeDiscreteParty ancillary outputs are supported when Packets are authored as part of the PKG file in the content library.
Note: Additional development is still needed before this feature is fully functional if using EZ Config Packages and Packets.
Expere: SmartSign Plus® integration
  • Type: Feature
  • Reference: PBI 839983, 839606, 834324
Summary: as part of our ongoing work to integrate SmartSign Plus® with Expere, the following functionality has been implemented for the November release:
  • PDF extension behavior updated (PBI 839983): the ability to upload external documents has been enhanced so when the document is viewed in SmartSign Plus, the PDF extension does not appear twice.
  • Package name updated (PBI 839606): the package name has been updated so when viewing it in SmartSign Plus, the /Txn/EOriginalSSPlusPackageNameDesc value appears before the Expere package name. For more information see Expere Transaction XPaths for eOriginal > Txn/EOriginalSSPlusPackageNameDesc.
  • Non-eNote workflow documented (PBI 834324): a new Non-eNote workflow has been documented and added to the SmartSign Plus® Integration Guide.
WCAG: Expere Engine enhanced to support embedded and Tagged .PDF's - November
  • Type: Enhancement
  • Reference: PBI 837807, 840417
Summary: as a part of our continued effort to create WCAG compatible documents we have updated the Expere Engine to now support the generation of Tagged .PDF documents. We will continue making enhancements to the Expere Engine for Tagged .PDF support, so check back for items being identified and corrected. As part of our continued work to support Tagged .PDF's, we have implemented enhancements to resolve the following WCAG-related changes in the November release:
  • Assembled PDF Form field tag behavior enhanced (PBI 837807); users reported that Embedded PDF documents generated as tagged PDF's contained empty <Form> fields with the expectation that these fields contain a value extracted from the request transaction. This behavior has been enhanced: form fields are tagged correctly for Embedded PDF documents so that the value for the field is present in the tag tree.
  • "Characters in a text object cannot be mapped to Unicode" behavior addressed (PBI 840417): users reported that the PAC 24 WCAG validation tool was displaying a "Characters in a text object cannot be mapped to Unicode" error on merged, tagged PDF documents. Internal analysis determined that the issue occurred when a text form field contained an empty, flattened string value. Flattening the text form field creates a text object on the pdf, and since it is empty, it cannot be mapped to Unicode.

    This behavior has been addressed; merged, tagged PDF documents no longer produce the "Characters in text object cannot be mapped to Unicode" error in PAC 24.
Expere: Internal Code Optimization when using Expere EZ Config Packages and Packets logos
  • Type: Enhancement
  • Reference: PBI 850662
Summary: as part of a regular cadence to review and upgrade any items used with our Expere application, the Engine has been undergone a code optimization to better support logos used with Expere EZ Config Packages and Packets.
Expere: Embedded PDF updated to support a SignatureType of "Initials"
  • Type: Enhancement
  • Reference: PBI 823346
Summary: users requested that the Expere Engine be updated so that the SignatureType element can be set to "Initials" for an Embedded PDF document, resulting in a <SignaturePoint> element containing a <Type> value of "Initials". This is done in the Product Technical Rule (PTR) in the native REQ file; see Modifying the PTR for the Signature Areas - Static/PDF > Step Two (2) in the Requirements Editor (RE4) User Guide for more information.

Expere is updated so that when "SignatureType:Initials" is authored for a field on an EmbeddedPDF, the Expere Response includes a <SignaturePoint> with <Type> value of "Initials".
Expere: PDF behavior enhanced when attempting to digitally sign multi-signature document
  • Type: Enhancement
  • Reference: PBI 843273
Summary: users reported that digitally signing a multi-signature PDF document would result in an error when saving the document. Users were forced to close Adobe Acrobat and reopen it in order to digitally sign and then save the document. Expere has been enhanced so that users are not required to exit Adobe Acrobat and reopen a document in order to sign it multiple times.
Expere: Logging enhanced
  • Type: Enhancement
  • Reference: PBI 848421
Summary: we have enhanced logging to provide more details about how long it takes to complete a transaction.
Note: No user action is required.
Expere: internal component upgrade to resolve security issue
  • Type: Maintenance
  • Reference: PBI 848185, 844857
Summary: as part of a regular cadence to review components used by Expere Engine for security issues, we have upgraded the following components:
  • WildFly 34.0.0
  • Apache Commons IO, version 2.17.0
Note: No user action is required.
eOriginal SmartSignWeb: DocumentProfileID included in the response file
Summary: this enhancement is to add the DocumentProfileID for Expere-generated eNote documents, as well as a Correction on a Expere generated eNote placeholder and is in the returned document package. This value is derived from the VaultID field in eOriginal.
Expere / eOriginal: schema 24.4 updated for use with SmartSign Plus® and SmartSign Web
  • Type: Enhancement
  • Reference: PBI 841380
Summary: The eOriginal Schema has been updated from 24.3 to 24.4 for use with SmartSign Plus® and SmartSign Web.
Note: No user action is required.
Expere: DynamicOverflowService optimization
  • Type: Maintenance
  • Reference: PBI 842891
Summary: As part of a regular cadence to review and upgrade any items used with our Expere applications, the DynamicOverflowService functionality has undergone a code optimization; no user impact is expected.
Expere: Sequencing issue of Signature / Signature Date fields for WKES
  • Type: Defect
  • Reference: PBI 840807
Issue: it was reported that the signature date field was being sequenced higher than the signature field when using Wolters Kluwer E-Sign (WKES) ancillary output; this sequencing value is part of the signature date field naming convention (for example: WKES_Signdate_firstname_lastname@domain.com_10028-28). WKES has a requirement that signature fields are the highest sequenced field for our signers. As a result, the signature date field did not display a value on the signed document.
Solution: This behavior has been enhanced so that signature date fields once again display a value on the signed document by modifying the sequencing so that signature fields contain the highest sequenced number in its naming convention.

October

Note: Please read the following deployment related information:
  • A supplemental October Customer Test (CT) release was deployed on October 15th that rolled back changes noted below.

    Users may have seen changelogs to support Multiple Commercial Notes (PBI 801194 and 790242) and Multiple IRA Plans (PBI 810106 in a single transaction, as well as internal code optimization work (PBI 834658, 790242, 836432, 835949). Those changes had been shelved and placed in the Redacted section at the bottom of the October section in the Hosted Expere Changelog.

Expere: UpdateTransaction enhancements rolled back
  • Type: Enhancement
  • Reference: PBI 846497
Summary: an issue was identified following the October 8th deployment and is related to UpdateTransaction enhancements to support multiple Commercial Notes and multiple IRA plans in single transactions using EZ Config Default Data. These enhancements were shelved, necessitating a supplemental October CT deployment.
Note: The items below were deployed as part of the original October CT release.
Expere: SmartSign Plus® integration
Summary: as part of our ongoing work to integrate SmartSign Plus® with Expere, the following functionality has been implemented for the October release:
  • Ability to finalize a package added (SOAP) (PBI 837795): users can now finalize a package to eOriginal Closing Center using a SOAP request. For more information, see Expere Web Services Guide > SmartSignPlusFinalize.
  • Destruction behavior enhanced for in-progress packages (PBI 838694): the following statuses have been updated when destructing packages:
    • STARTED: Available Destruction Types changed from "1", "2", "3" to "None"
    • EDEPOSITED: Available Destruction Types changed from "3" to "None"
    • EDEPOSIT_PENDING: Available Destruction Types changed from "1", "2", "3" to "None"
    • Canceled: Available Destruction Types changed from "1", "2", "3" to "3"
    • EXPIRED_PRINT_PENDING: Available Destruction Types changed from "3" to "None"
    • EXPIRED_MAILOUT_PENDING: Available Destruction Types changed from "3" to "None"
    Refer to eNote Destruction Workflow Outline > Package status definitions and actions for a comprehensive list of statuses, definitions, and any potential actions.
  • Expere eNotes supported (PBI 825950): An Expere eNote can now be passed to SmartSign Plus when /Txn/EClosingNoteInd = 1 and deposited into a customer's eVault. Previously, the SmartSign Plus workflow only accepted Expere eNote placeholders. See eNote Workflow Outline > Passing an Expere-generated eNote for more information.
  • Single Electronic Package execution behavior enhanced for "Paper" (PBI 837507): when /Txn/EOriginalSSPlusSingleElectronicPackageInd = 1, the corresponding SmartSign+ execution type is now "Paper".
  • Integration Guide enhanced for Expere-generated eNote placeholder and Expere-generated dynamic eNote Workflow topic (PBI 834323): The Expere - SmartSign Plus® Integration Guide has been updated to document the workflows when using either an Expere-generated eNote placeholder or Expere-generated dynamic eNote. For more information, see Step 5: Expere-generated eNote placeholder and Expere-generated dynamic eNote Workflow Outline.
Expere: Expanding merging PDF options
Summary: we have begun work on supporting merged PDF documents by Discrete Parties. In the near future, Expere will support generating multiple merged PDF documents based on the discrete party or parties specified for each document through the use of new MergedCopyPDFDiscreteParty and PdfMergeDiscreteParty options.
Note: Additional development is still needed before it is available for use
WCAG: Expere Engine enhanced to support embedded and Tagged .PDF's - October
  • Type: Enhancement
  • Reference: PBI 833078
Summary: as a part of our continued effort to create WCAG compatible documents we have updated the Expere Engine to now support the generation of Tagged .PDF documents. We will continue making enhancements to the Expere Engine for Tagged .PDF support, so check back for items being identified and corrected. As part of our continued work to support Tagged .PDF's, we have implemented enhancements to resolve the following WCAG-related changes in the October release:
  • Tagline field behavior enhanced (PBI 833078): it was reported that tagline "Form" fields in the source REQ file are appearing in the Adobe Acrobat Tag Tree for a tagged PDF document, despite not being authored.

    This behavior has been enhanced; when generating a tagged Embedded PDF document, tagline "Form" fields no longer appear in the Adobe Acrobat Tag Tree.
Expere: monthly component upgrade (FOP, WildFly)
  • Type: Maintenance
  • Reference: PBI 833154, 826968
Summary: As part of a regular cadence to review and upgrade any items used with Expere Engine, we have upgraded the following components:
  • FOP 2.9
  • WildFly 33.0.1
Note: No user action is required.
Expere: Embedded PDF - Conditioning Fillable Field
  • Type: Enhancement
  • Reference: PBI 823345
Summary: currently fillable fields on Embedded PDF documents do not honor conditional logic on when the field appears as a fillable field. Expere has been enhanced so that conditional logic can be added to FieldFields of all types (i.e. ‘Initial’, ‘Text’) to allow users to electronically enter data.
Expere: Missing InstanceBarCodeValue in response message
  • Type: Defect
  • Reference: PBI 842065
Issue: a user reported that an expected InstanceBarcodeValue element and value did not appear in the Expere response file after generating Integrated Disclosure documents. The expected behavior was that the InstanceBarcodeValue value would appear in the response when generating Integrated Disclosure documents that specify Barcode → TextString. It was determined that the previous update for PBI 838313 did not include documents utilizing stylesheets in which ‘IntegratedDisclosure’ was part of the stylesheet name.
Solution: The InstanceBarcodeValue field is once again populated in the Expere response file when documents use a stylesheet with ‘IntegratedDisclosure’ in the file name (i.e. WKFS_Styleguide_IntegratedDisclosure).

Redacted

Expere: UpdateTransaction method enhanced to support multiple IRA plans
Summary: in April, we had released PBI 810106 but had to remove the changes due to issues found during customer testing (PBI 821935). This issue has been resolved (PBI 790242) while reintroducing changes made in PBI 810106. These updates include the ability to submit multiple IRA plans in one transaction and be assigned a specific product for each IRA plan when /Txn/Deposit/IRAPlans/IRAPlan/EZConfigIRAPlanProductDesc is passed in the transaction. When needing to support the multiple IRA Plans in a given transaction, for the data to merge properly, the EZConfig Default Data Product associated to the IRA Plans must only contain an IRA Booklet Policy and the EZ Config Default Data Product associated to the Account should not contain an IRA Booklet Policy.
Note:
  • The /Txn/Deposit/IRAplan/OrgResponsibilityType XPath now has a flag of "ApplyToAll" set so each IRAPlans/IRAPlan gets this value set when there are Multiple IRA Plans in a transaction. As a result, users must consume an updated base content package that supports this feature. The content used with this feature must be consumed with version 24.03 or newer as data points were moved between the EZ Config Default Data .REQ files; see the March 2024.03 content release notes for more information.
  • To utilize multiple product scenario support with Deposit, IRA and Commercial lines of business, integrators will need to use the EZ Gateway UpdateTransaction method.
For more information, see the following:
Expere: UpdateTransaction method enhanced to support multiple commercial notes
Summary: in April, we had released PBI 801194 but had to remove the changes due to issues found during customer testing (PBI 821935). This issue has been resolved (PBI 790242) while reintroducing changes made in PBI 801194. These updates include the ability to submit multiple Commercial Notes in one transaction and be assigned a specific commercial product for each Commercial Note when /Txn/Notes/Note/EZConfigCommercialProductDesc is passed in the transaction.
Note:
  • In order to utilize this feature, users must consume an updated base content package that supports this feature. The content used with this feature must be consumed with version 24.01 or newer as data points were moved between the EZ Config Default Data .REQ files; see the January 2024.01 content release notes for more information.
  • To utilize multiple product scenario support with Deposit, IRA and Commercial lines of business, integrators will need to use the EZ Gateway UpdateTransaction method.
For more information, see the following:
Expere: Internal Code Optimization with UpdateTransaction
  • Type: Enhancement
  • Reference: PBI 834658, 790242, 836432, 835949
Summary: as part of a regular cadence to review and upgrade any items used with our Expere application, the UpdateTransaction functionality has undergone a code optimization. As part of this update, the following known issue was addressed: if passing an element with an attached Key Path with the incoming transaction, an error is thrown if the element being targeted by the Key Path does not exist. An example Xpath that exhibits this behavior is Txn/Deposit/Accounts/Account/DelayedAvailabilityFormType.

September

Expere: SmartSign Plus® integration
Summary: as part of our ongoing work to integrate SmartSign Plus® with Expere, the following functionality has been implemented for the September release:
  • Fillable Fields of type: Multi Line Text for Static REQs (PBI 834530): when FieldType - 'Alphanum' and MultiLine - 'true' the corresponding FieldName has been updated with the following naming convention: SS+TAG{"tagName": "Enter FillableText ID", "type": "MULTI_LINE_TEXT", "role": {"type": "Borrower", "num": 1}, “required”: true}. For more information, see PDF Form Field Name Guidelines for FillableField > Multi-line text.
  • All statuses supported when destructing packages (PBI 792573): all statuses are now supported when destructing packages. Refer to eNote Destruction Workflow Outline > Package status definitions and actions for a comprehensive list of statuses, definitions, and any potential actions.
  • “Injectable Issued Date” enhancement implemented (PBI 820639): when /Txn/SystemGeneratedIntegratedDisclosureDateIssuedInd="1" (true) and the FillableField FieldName (as authored in the REQ) value is IssuedDate, Expere now applies the SmartSign Plus naming convention for “injectable issued dates”. An "Injectable Issued Date" is a field that SmartSign Plus uses to populate the date field based upon when the document was made electronically available and viewed by the consumer or when the document went to print. For more information, see PDF Form Field Name Guidelines for FillableField > Date.
  • New REST "SmartSignPlusFinalize" API created (PBI 764108): a new REST "SmartSignPlusFinalize" API now allows users to finalize a SmartSignPlus package and assign it to the eOriginal Closing Center. See EDS Web Services Guide > SmartSignPlusFinalize for more information.
  • /Txn/EOriginalSSPlusPrintMailingCostCenterDesc updated to be "Optional" (PBI 833451): /Txn/EOriginalSSPlusPrintMailingCostCenterDesc is now an optional element and is not required to be passed in the transaction.

    For more information, see Expere Transaction XPaths for eOriginal.

  • Ability to support templates (PBI 827473): if a user would like to utilize Document Templates (for example: Charm Booklet, Your Own Home Loan Toolkit, etc) via SmartSign Plus, they must have the template configured in SmartSign Plus> Administration > Settings > Document Templates and include the templateId in the transaction. The templateId is the unique SmartSign Plus identifier given to a template upon creation.

    For more information, see Expere Transaction XPaths for eOriginal > Document Collection.

  • SmartSign Plus feature / Expere Document Services web services guides updated (PBI 771400): the following information has been added to the SmartSign Plus feature and Expere Document Services web service guides:
    • SmartSign Plus feature guide: A new Before You Begin topic containing a list of supported / non-supported scenarios.
    • Expere Document Services web service guide: the PackageInformation topic includes all supported elements.
  • "Num" behavior enhanced (PBI 823449): SmartSign Plus now supports a scenario when a "num" and corresponding value are not present in the Expere response file.
Expere: <InstanceBarcodeValue> displays in Expere response
  • Type: Enhancement
  • Reference: PBI 838313
Summary: a user reported that a null pointer error would appear when a Barcode type (for example: "PDF417") was not authored in a Tagline element that contained a barcode (commonly referred to a "Transaction barcode"). A previous version of the Expere Engine was configured to allow a user to bypass the Barcode type and still receive an <InstanceBarcodeValue> element and value in the Expere response. However, the latest version of the Expere Engine did not allow this. As a result, the Expere Engine has been updated to include an <InstanceBarcodeValue> in the response for Transaction barcodes where the type of barcode is not authored. Also, note that by including the <InstanceBarcodeValue> value, the response will include the <AncillaryOutputOption> container, for example:

...
<r:InstanceBarcodeValue>987987201</r:InstanceBarcodeValue>
<r:AncillaryOutputOption>
	<r:OutputType>Barcode</r:OutputType>
	<r:Barcode>
		<r:Pattern>987987201</r:Pattern>
		<r:UseCoverPage>false</r:UseCoverPage>
		<r:FirstPageOnly>false</r:FirstPageOnly>
	</r:Barcode>
</r:AncillaryOutputOption>
...
Expere: eSignature date field length enhanced
  • Type: Enhancement
  • Reference: PBI 823496
Summary: users reported that when using an eSignature date field, the generated fillable date field did not fully display a date using "mm/dd/yy format". Instead, the last "y" character was truncated (for example: "10/12/2").

This behavior has been enhanced so when using an eSignature date field, the complete date using a "mm/dd/yy" format is displayed.

Note: Users can opt for either a "mm/dd/yy" or "mm/dd/yyyy" date format.
Expere: EmbeddedPDF response updated for Signer Description
  • Type: Enhancement
  • Reference: PBI 832759
Summary: it was reported that when using a previous version of a document that was authored as a Static document, entering a value of "Notary, Notary" in the SignerRole resulted in the same value appearing in the <Description> element in the Expere response file. Only "SignerRole:Notary" was honored.

<r:Signer>
	<r:Id>NotaryID</r:Id>
	<r:Description>Notary, Notary</r:Description>
	<r:SignaturePoints>
		<r:SignaturePoint>
			<r:IncludeDate>true</r:IncludeDate>
			<r:PageNumber>1</r:PageNumber>
			<r:PageOrder>1</r:PageOrder>
			<r:Height>26.25</r:Height>
			<r:Width>197.54999</r:Width>
			<r:SignatureText>_</r:SignatureText>
			<r:XCoordinate>155.25</r:XCoordinate>
			<r:YCoordinate>249.75</r:YCoordinate>
			<r:Type>Signature</r:Type>
			<r:FieldName>SIG_Notary, Notary_0_NotaryID_false_1_GrantorNotary_eSig</r:FieldName>
			<r:Sequencing>7</r:Sequencing>
			<r:SignatureRequired>false</r:SignatureRequired>
		</r:SignaturePoint>
	</r:SignaturePoints>
</r:Signer>
However, after this document was converted to an EmbeddedPDF, users could no longer add a "Notary, Notary" value for the Signer Role. As a result, Expere has been updated to support a "Notary, Notary" SignerRole value which will be honored in the Expere response file.
Note: The "SignerRole:Notary" value will continue to be honored and is the recommended value for SignerRole when authoring documents with Notaries.
Expere: RTF output behavior enhanced
  • Type: Enhancement
  • Reference: PBI 834813
Summary: a user reported that the Acknowledgment section on a generated RTF document did not preserve space to enter data.

As a result, the Acknowledgement section on a generated RTF document preserves space to physically enter data. Data fields authored to contain an underline are presented in an RTF document; additionally, updates were made so that checkboxes display similiarly to those on a PDF document.
Expere: internal component upgrade to resolve security issue
  • Type: Maintenance
  • Reference: PBI 798912, 813365
Summary: As part of a regular cadence to review components used by Expere Engine for security issues, we have upgraded the following components:
  • io.swagger.core.v3 2.2.22
  • jackson-databind_2.16.2
  • jackson-core_2.16.2
Note: No user action is required.
Expere: 2D Barcode compression behavior enhanced
  • Type: Defect
  • Reference: PBI 831295, 837547
Issue: a user reported a barcode discrepancy between two different versions of content where a 2D Barcode was generated on the cover page of the document. This 2D Barcode that was applied to an older, Static version of the content resulted in a scannable barcode. However, after that same content was converted to an Embedded PDF, the barcode was compressed, resulting in an issue with scanning.
Solution: This behavior has been enhanced; as a result, using a 2D Barcode results in a barcode size equivalent to that of a Static and Dynamic document. Functionality has also been updated so that 2D Barcodes height closely matches the barcode field height on the Embedded PDF pages.
Note: For any barcode type that contains text in the barcode, users may notice a font size difference, however the barcode and value will remain the same.
Expere: EmbeddedPDFs to support line breaks
  • Type: Defect
  • Reference: PBI 818892
Issue: a user reported that an Embedded PDF document containing line breaks in transaction data (coded as <br/>) displayed the actual <br/> syntax in the generated PDF document instead of adding line breaks to the transaction data.
Solution: Expere has been updated so that generated EmbeddedPDF documents display actual transaction data containing line breaks.
Expere: SOAP Callback behavior enhanced
  • Type: Enhancement
  • Reference: PBI 836007
Summary: It was determined that values were not being returned in the REST callback when the originating request was made with SOAP. Values were only being returned in the REST callback if the originating request was REST. This behavior has been enhanced so that values are returned in the REST callback when a SOAP call is made.
Expere: monthly component upgrade
  • Type: Maintenance
  • Reference: PBI 826967
Summary: As part of a regular cadence to review and upgrade any items used with Expere Engine, we have upgraded the following components:
  • Amazon Corretto 21.0.4.7.1
  • WildFly 33.0.0
Note: No user action is required.

August

Note: Please read the following deployment related information:
  • A supplemental CT release was deployed on August 12 that addresses a null pointer exception when there is only a single radio button produced for a radio group. See PBI 836611 below.
Expere: document generation update to handle single radio button null pointer
  • Type: Defect
  • Reference: PBI 836611
Issue: Expere document generation failed on a dynamic document when the radio group resulted in only having a single radio button. This issue was discovered through log monitoring and was caused by our iText8 upgrade.
Solution: Expere has been updated to successfully generate documents when there is a single radio button in a radio group.
Note: The items below were deployed as part of the original August CT release.
Expere: SmartSign Plus® integration
Summary: as part of our ongoing work to integrate SmartSign Plus® with Expere, the following functionality has been implemented for the August release:
  • SmartSign Plus eDelivery Service functionality added (PBI 825773): closing documents can now be sent to a Settlement Agent/Closing Agent via eDelivery; the following XPaths have been added:
    • /Txn/EOriginalSSPlusSingleElectronicPackageInd
    • /Txn/EOriginalSSPlusSingleElectronicPackageEmailAddress
    • /Txn/EOriginalSSPlusSingleElectronicPackageFirstName
    • /Txn/EOriginalSSPlusSingleElectronicPackageLastName
    Note: SmartSign Plus eDelivery service supports the electronic delivery of documents to Settlement Agents/Closing Agents for printing/ wet signing documents. A wet signature is a physical signature made with wet ink on a document. The SmartSign Plus eDelivery service does not support electronic delivery of eNotes because eNotes are signed electronically.

    For more information, see Expere Transaction XPaths for eOriginal > eDelivery

  • Closing Center assignment functionality added (PBI 790237): the following XPaths have been added that allow users to include the email address for the user accessing the eOriginal Closing Center:
    • /Txn/EOriginalClosingCenterAssignments
    • /Txn/EOriginalClosingCenterAssignments/EOriginalClosingCenterAssignment
    • /Txn/EOriginalClosingCenterAssignments/EOriginalClosingCenterAssignment/EmailAddress

    For more information, see Expere Transaction XPaths for eOriginal > Closing center assignments.

  • Package finalization (PBI 805334): this work item was completed in order for Expere Document Services to support the finalization of a package through SmartSign Plus.
  • Ability to add a "Lender Name" during SmartSign Plus setup (PBI 779994): as part of the initial SmartSign Plus configuration, users can now add a Lender Name value in the Document Generation Services Tool Suite > SETUP Page. For more information, see SETUP page > SmartSign+ Credentials section and Implementation Guidelines > Document Generation Service Tool Suite settings.
  • SmartSign Plus® naming convention supported with Embedded PDF and Static documents (PBI 767471, 767472, 820395): Expere has been updated to support the SmartSign Plus® naming convention for fillable fields and fillable checkboxes for use with Embedded PDF and Static documents. For more information, see PDF Form Field Name Guidelines and supporting topics.
  • Identity Verification updated (PBI 824701): functionality has been added to support identity verification through a custom PIN number, the custom PIN hint, and PIN SMS delivery system. For more information, see Expere Transaction XPaths for eOriginal.
  • Date format translation updated (PBI 829741): Expere users can pass in date formats as YYYYMMDD or YYYY-MM-DD. Date formats entered as YYYYMMDD are converted to YYYY-MM-DD when passed to SmartSign Plus®.
  • Integration Guide > XPath topic updated (PBI 834321): the Expere Transaction XPaths for eOriginal help topic, which contains a comprehensive list of XPaths used when working with eOriginal transactions, has been separated into the following sub-tables:
    • Package collection
    • Expiration setup
    • Participants collection
    • Return Address collection
    • Closing Center assignments
    • eDelivery
    • Document collection
Expere: Fillable Field Default Behavior Change - released in August
  • Type: Feature
  • Reference: PBI 813121
  • Documentation Impacts: Features page
Summary: we recently informed you via PBI 819179 that Expere was being enhanced to generate Fillable Fields when specified rather than producing them by default. These changes simplify the logic and makes Expere more maintainable. This change will now be available in the following releases:
  • Hosted Expere users: August production release
  • On-prem, self-hosted Expere users: Expere 2024 Release Two
Note: This enhancement was previously released to the Customer Test (CT) environment on July 9th.
Expere: <SuppressESignature/> logic updated
  • Type: Enhancement
  • Reference: PBI 829776
Summary: It was identified that signature fields were not being removed in the PDF and Tagged PDF in certain scenarios when the <SuppressESignature/> element resulted in true. Expere has been updated so that signature fields are removed on the PDF and Tagged PDF when <SuppressESignature/> element results in true.
Engine: <StaticSignature/> behavior updated
Summary: it was reported that when a the source document (REQ file) used the <StaticSignature/> element, and it was the only signature on the document, the Expere response file specified that the document was an "InkSign" document (<InstanceSigningInstructions/>="InkSign"). As a result, the document was sent to a Third Party eSigning Platform as a document requiring an "InkSign" signature from a Loan Officer; however, the document had a "Static Signature" applied.

Expere has been updated so that when a document contains <StaticSignature/> and <SignerNameAboveLine/> elements and when no other non-<StaticSignature/> signatures are present on the document, the <InstanceSigningInstructions/> value is NoSignatures in the Expere response file.
EZ Transform enhancements
  • Type: Feature
  • Reference: PBI 825743, 826209, 814064
Summary: EZ Transform has been updated to include the following:
  • A new internal API that will be utilized by future enhancements to EZ Transform. External-facing user documentation will available in the near future.
  • Apache Tomcat 10.1.24
Expere: iText8 upgrade / enhancement
  • Type: Enhancement
  • Reference: PBI 825821, 810591, 818440
Summary: the Expere Engine has updated to use iText8. With this update, we have identified and addressed certain known issues; these are listed below. Customers may notice differences in the generated PDF.
  • Known differences:
    • If smart quotes are authored in tooltips when generating Tagged PDFs, Expere will convert the smart quotes to standard quotes. Smart quotes in other parts of the document, if they exist, will remain.
    • Checkbox borders appear slightly thicker.
    • Hovering over a radio button will display the field name (for non-WKES radio buttons)
  • Issues resolved:
    • PDF generation behavior resolved (PBI 825821): users reported that certain Tagged PDF documents failed to generate a merged PDF document when using either the MergePdf or MergedCopyPdf ancillary output option while generating succesfully as individual PDF documents. This behavior has been enhanced so that using either the MergePdf or MergedCopyPdf ancillary output option generates a merged PDF document successfully.
Expere: internal component upgrade to resolve security issue
  • Type: Maintenance
  • Reference: PBI 829927, 822068, 798914, 798752, 829639
Summary: As part of a regular cadence to review components used by Expere Engine for security issues, we have upgraded the following components:
  • Batik 1.17
  • Windows Installer XML (WiX) 3.14.1
  • JSON-Java 20231013
  • Bouncy Castle 1.78
  • 7pzip removed in order to use the Native Windows-compatible powershell script
Note: No user action is required.
Expere: monthly component upgrade
  • Type: Maintenance
  • Reference: PBI 826965
Summary: As part of a regular cadence to review and upgrade any items used with Expere Engine, we have upgraded the following components:
  • Amazon Corretto 21
Expere EZTransform: internal components cleanup
  • Type: Maintenance
  • Reference: PBI 830522
Summary: Some analysis was performed on Expere EZTransform and it was identified that it referenced some third-party components that weren’t actually used. Updates were made to remove these third-party components.
Note: No user action is required.
Expere / eOriginal: schema 24.3 updated for use with SmartSign Plus® and SmartSign Web
  • Type: Enhancement
  • Reference: PBI 830389
Summary: The eOriginal Schema has been updated from 24.2 to 24.3 for use with SmartSign Plus® and SmartSign Web.
Note: No user action is required.
Expere: Fillable Fields appearing in response file behavior addressed
  • Type: Defect
  • Reference: PBI 834791
Issue: a user reported that fillable fields were present in the Expere response file for a particular Embedded PDF document when no fillable fields were authored in the native REQ document.
Solution: Expere no longer produces fillable fields in the Expere response file when the native REQ is not authored to produce fillable fields.
Expere: EmbeddedPDF Document Generation enhanced
  • Type: Defect
  • Reference: PBI 827803
Issue: It was identified that for a specific EmbeddedPDF REQ (HUD203KSpecificationOfReparis-M2.req), document generation would error.
Solution: Expere has been updated to generate this document successfully,

July

Expere: SmartSign Plus® integration
Summary: as part of our ongoing work to integrate SmartSign Plus® with Expere, the following functionality has been implemented for the July release:
  • <FillableFieldSet/> "num" value logic enhanced (PBI 827529): when multiple <FillableFieldSet/>-related entries (for example: <FillableText/> were present in the Expere response file, all "num" values in the <FieldName/> container were being assigned the same value. The expected behavior is that the "num" value should be the value that is specific to the associated party's <ID/>. As a result, this behavior has been enhanced so that the "num" value is specific to the associated party's <ID/> in the Expere response file and the field name on the PDF.
  • Support for documents without Signer Information (PBI 815460): for E-Sign documents, if the participant AccessMethodType is “EMAIL” and no email address is provided, the SmartSign Plus® execution type is changed from E-Sign to Paper.
  • Signature Date fields set “formatType” to “DATE” (PBI 825653): the SmartSign Plus® Acroform field naming convention for Signature Date fields has been updated to set the "formType" to “DATE" when the “type” is “AUTO_DATE”. See PDF Form Field Name Guidelines for SignaturePointSet for complete details for SmartSign Plus field naming conventions.
  • Mailing information provided at the Package-level (PBI 822523): Mailing information is now supported at the package level in order to satisfy requirements for SmartSign Plus® Print Fulfillment. To enable package level mailing, users should set EOriginalSSPlusPackageMailingInd = 1. See Print fulfillment workflow > Package level for more information.
  • Mailing information provided at Participant-level (PBI 822522): Mailing information is now supported at the participant level in order to satisfy requirements for SmartSign Plus® Print Fulfillment. To enable participant level mailing, users should set EOriginalSSPlusPackageMailingInd = 0. See Print fulfillment workflow > Participant-level for more information.
Fillable Field Default Behavior Change
  • Type: Feature
  • Reference: PBI 824672, 824670, 819179
  • Documentation Impacts: See Features page for more information
Summary: Expere has been updated to generate Fillable Fields when specified rather than producing them by default. These changes simplify the logic and makes Expere more maintainable.

The previous default allowed documents to support fillable fields but not eSignature fields. The new behavior will support fillable fields when eSignatureAndFieldSupport options are specified in the request; otherwise, fillable fields will not be generated on the documents. Please see Features page for more details.

Note: Effective Dates are as follows:
  • Customer Test Environment: July 2024
  • Production Environment: August 2024
Expere: internal code optimization with XY Coordinate and Wolters Kluwer E-Sign (WKES) functionality
  • Type: Enhancement
  • Reference: PBI 819077, 820296, 819072, 829380, 828961
Summary: As part of a regular cadence to review and upgrade any items used with our Expere applications, the XY Coordinate and WKES, functionality has undergone a code optimization; no user impact is expected.
WCAG: Expere Engine enhanced to support embedded and Tagged .PDF's - July
  • Type: Enhancement
  • Reference: PBI 826126, 825652
  • Documentation Impacts: See below for any pertinent links.
Summary: As a part of our continued effort to create WCAG compatible documents we have updated the Expere Engine to now support the generation of Tagged .PDF documents. We will continue making enhancements to the Expere Engine for Tagged .PDF support, so check back for items being identified and corrected. As part of our continued work to support Tagged .PDF's, we have implemented enhancements to resolve the following WCAG-related changes in the July release:
  • Merged PDF PAC 2021 exception resolved (PBI 826126): users reported that the PAC 2021 compatibility checker flagged merged PDF documents with XMP Metadata and Title in Metadata errors. Updates were made and as a result, XMP Metadata and Title in Metadata errors are no longer present in PAC 2021.
  • Embedded PDF checkbox format updated (PBI 825652): it was reported that a particular Embedded PDF document contained checkboxes that were not read correctly by the NVDA screen reading tool. When the NVDA tool encountered a checkbox on the generated PDF document, the tool is expected to announce that a checkbox was present and either checked or not checked; this was not occurring.

    Internal analysis determined that the structure of certain checkboxes in the Adobe Acrobat Tag Tree was incorrect. In the screen shot below, the tag form is incorrect for the Investor / Builder checkbox compared to the Owner-Occupant checkbox in that the tag should be structured <Form> "CheckboxName" with a child tag for the checkbox. Additionally, the first instance has alternate text generated (if viewed in Properties for that tag), however it is missing from the second instance.

    This behavior has been modified so that the checkbox Adobe Acrobat Tag Tree is structured <Form> "CheckboxName" with a child tag for the checkbox in Embedded PDF documents.



Expere internal components upgraded
  • Type: Enhancement
  • Reference: PBI 826091, 798744
Summary: As part of a regular cadence to review and upgrade any items used with our Expere applications, we have upgraded the following:
  • Wildfly 32.0.1
  • Apache Santuario 4.0.2
Note: No user action is required.
Expere: SmartSign Web - Expere eNote behavior enhanced
  • Type: Enhancement
  • Reference: PBI 827336
Summary: the Expere eNote logic has been enhanced so that If an eNote exists, the signature list will only have signatures for the eNote based on the following enumerated values (using Txn/EOriginalUploadInd:
  • 0 = no documents should be uploaded to eOriginal (with the exception of the eNote)
  • 1 = all documents should be uploaded to eOriginal
Embedded PDF document not honoring eSignatureDateSupport Ancillary Option
Issue: it was reported that generating an Embedded PDF file using an ESignatureAndFieldSupport ancillary output > eSignatureDateSupport = "false" the resulting date field was fillable and appeared as a <SignaturePoint/> in the corresponding Expere response file.
Solution: This behavior has been resolved so that if using an ESignatureAndFieldSupport ancillary output > eSignatureDateSupport = "false", the resulting date field is not signable, and the Expere response file should only display a SignaturePoint container for the signature field with an IncludeDate = "true".
Expere: SmartSign Web - defect correction
  • Type: Defect
  • Reference: PBI 824227
Issue: users reported that during testing, the suffix on the static eNote was not being mapped,
Solution: If Txn/Borrowers/Borrower/Suffix is passed in the transaction, it is mapped to smartDocTemplateData/signer; suffix. For more information, see eOriginal data points used for a fixed or ARM loan.

June

Expere: SmartSign Plus® integration
Summary: as part of our ongoing work to integrate SmartSign Plus® with Expere, the following functionality has been implemented for the June release:
  • Field not created for SmartSign Plus ® when an ID is absent for fillable fields and checkboxes (PBI 824737): Expere will not generate a form field nor return a <FillableFieldSet/> container in the response file when no ID (for example: (RembrandID, SignerID, '*') is specified for Fillable Fields or Fillable Checkboxes. For more information, see SmartSign Plus® Feature Guide > Additional "num" notes.
  • 'Num' value for each field to the associated signer's assigned integer (PBI 817351, 824963): we recently released functionality per PBI 812414 (April release) that handles a signer identified as '*' or wildcard; as a result, any signer of the document can complete or sign the specified field. Currently, the Engine needs to assign these fields to the first signer of the document. This functionality has been enhanced so that when multiple instance documents contain fillable fields that specify the signer as the "*" (wildcard), the Engine assigns these fields to the first signer of the document instance. If no signer exists, the Discrete Party is used; if no Discrete Party is present, the first signer of the transaction is used.

    Additionally, when multiple RembrandtIDs are specified in the <RembrandtIDRefs> element in <EOriginalsSSPlusParticipants/> > <EOriginalSSPlusParticipant/>, each of these RembrandtIDs will be associated to the same 'num' value as specified in the SmartSign Plus® acroform fields.

    For more information, see SmartSign Plus® Feature Guide > Additional "num" notes.

  • New status and messaging returned in eOriginal element (PBI 801105, 819473):
    • Expere Document Services Tool Suite: as part of the WSDL update that made in PBI 801104, the Expere Document Services Tool Suite > SUPPORT page was updated to include a new "Successful with Warnings" status accessible in the State dropdown. See SUPPORT Page for more information.
    • Document Service: for DocumentService REST API users, the <EOriginal> element has been updated to include a new <ExperePackageName> and <Messages> elements. Additionally, the <RequestStatus> element has been updated to include a new SuccessfulWithWarnings parameter. For more information, see Expere Document Services Web Services Guide > EOriginal and RequestStatus.
  • Access method added to the Participant container (PBI 821924): users can pass in either the "EMAIL" or "API" access methods through a new /Txn/EOriginalSSPlusParticipants/EOriginalSSPlusParticipant/AccessMethodType XPath. This new XPath replaces /Txn/EOriginalSSPlusAccessMethodType. For more information, see SmartSign Plus® Feature Guide > Expere Transaction XPaths for eOriginal.
Upcoming Fillable Field Default Behavior Prep Work
  • Type: Feature
  • Reference: PBI 819179
Summary: In preparation for the upcoming Fillable Field Default Behavior changes scheduled for July/August 2024 (Please see Feature Page for more details), users will notice that bookmarks for Signature Fields in Tagged PDF and Standard PDF documents will not appear in Adobe Acrobat when the following configuration settings are present:
  • AcroformSupport = false
  • eSignatureAndFieldSupport = true
  • eSignatureCoordinatesOnly = true
  • NonSignatureFieldCoordinatesOnly = false
Engine: Saxon upgrade to 10.9
  • Type: Enhancement
  • Reference: PBI 818520
Summary: As part of the regular comprehensive security tests that are run against Expere components, we have updated the Expere Engine to use Saxon version 10.9. This upgrade was conducted to resolve issues where font settings were not being preserved in the field when line breaks were present in the transaction data.
Expere EZTransform: internal components upgraded
  • Type: Enhancement
  • Reference: PBI 787852
Summary: Summary: As part of a regular cadence to review and upgrade any items used with our Expere applications, we have upgraded the following: EZTransform to use the following third-party components:
  • Apache Struts_2.5.33
  • Jackson-Databind 2.17.2
  • Commons-FileUpload 1.5
Note: No user action is required.
Expere internal components upgraded
  • Type: Enhancement
  • Reference: PBI 825653, 822599
Summary: As part of a regular cadence to review and upgrade any items used with our Expere applications, we have upgraded the following:
  • Amazon Corretto Java 17.0.11_9
  • Wildfly 32.0.0
Note: No user action is required.
Expere Engine: Font and Bold emphasis behavior enhanced when using <br/>
  • Type: Enhancement
  • Reference: PBI 800837, 740793
Summary: The following line break (br/>)-related functionality has been enhanced by upgrading to Saxon 10.9:
  • It was reported that when a DTA in an .REQ file contained a phrase or sentence authored with a specific font (e.g. using an "Emphasis" tag and a Font of "Courier New"), a line break (<br/>) in the code resulted in the subsequent text reverting to a default font (e.g "Times New Roman"), rather than preserving the specified font. After the Saxon 10.9 upgrade, a font selected through an "Emphasis" tag is preserved regardless if line breaks are used.

  • It was reported that when a DTA in an .REQ file contained a phrase or sentence authored with a "Bold" Emphasis tag, a line break (<br/>) resulted in the subsequent text not being bolded, rather than bolding the entire phrase or sentence. After the Saxon 10.9 upgrade, a Bold emphasis selected is preserved regardless if line breaks are used

Removal of FOP26 element
  • Type: Enhancement
  • Reference: PBI 812856
Summary: Expere has been updated to completely remove the FOP26 flag from all API's. Moving forward Expere will only support one version of FOP.
Expere / eOriginal: schema 24.2 updated for use with SmartSign Plus® and SmartSign Web
  • Type: Enhancement
  • Reference: PBI 818612
Summary: The eOriginal Schema has been updated from 24.1 to 24.2 for use with SmartSign Plus® and SmartSign Web. There were no updates that impacted users.
DocViewer: Third Party Cookie Phaseout
  • Type: Enhancement
  • Reference: PBI 822257
Summary: Google is implementing a new "Tracking Protection" feature that will limit the use of "third-party cookies" that track internet usage when using Google Chrome. As part of this "third-party cookie phaseout", DocViewer will continue to be accessible for our Expere users.

May

Expere: SmartSign Plus® integration
Summary: as part of our ongoing work to integrate SmartSign Plus® with Expere, the following functionality has been implemented for the May release:
  • PackageInformation child element name changes (PBI 819943): the following PackageInformation data type child elements have been renamed and can be included in the request, response, or PKG files:
    • EOriginalSSPlusPrintMailingCostCenter is now EOriginalSSPlusPrintMailingCostCenterDesc
    • EOriginalSSPlusPrintMailingCarrierType is now EOriginalSSPlusPrintMailingCarrierName, while all enumerated values for this element have been removed.
    • EOriginalSSPlusPrintMailingReturnAddress / EOriginalSSPlusPrintMailingReturnAddressLine1 is now EOriginalSSPlusPrintMailingReturnAddress / EOriginalSSPlusPrintMailingReturnAddressStreetAddress
    • EOriginalSSPlusPrintMailingReturnAddress / EOriginalSSPlusPrintMailingReturnAddressLine2 is now EOriginalSSPlusPrintMailingReturnAddress / EOriginalSSPlusPrintMailingReturnAddressStreetAddress2
    • EOriginalSSPlusPrintMailingReturnAddress / EOriginalSSPlusPrintMailingNumCopies is now EOriginalSSPlusPrintMailingCopiesCount

    See PackageInformation and EOriginalSSPlusPrintMailingReturnAddress for more information.

  • WSDL Update: new <Messages> element added to <EOriginal> (PBI 801104): the <EOriginal> element has been updated to include a new <ExperePackageName and <Messages> elements. Additionally, the <RequestStatus> element has been updated to include a new SuccessfulWithWarnings parameter. For more information, see Expere Document Services Web Services Guide > EOriginal.
  • Signature Dates updated to AUTO_DATE (PBI 818798): the format for Signature Date fields has been updated to set the "type" to "AUTO_DATE" when /Txn/EOriginalSSPlusUseManualDateInd does not equal "1" ("true"; or if /Txn/EOriginalSSPlusUseManualDateInd equals 0 or is not present). See SmartSign Plus® Feature Guide > PDF Form Field Name Guidelines for SignaturePointSet > Date / AUTO_DATE for more information.
    Note: "AUTO_DATE" is the default option; in order to have a "type" of "Date", users would need to pass in an XPath of /Txn/EOriginalSSPlusUseManualDateInd=1.
  • <InstanceSigningInstructions/> updated when fillable fields or checkboxes are present (PBI 818852): the <InstanceSigningInstructions/> value will appear as "ESign" in the Expere response when the following conditions are met:
    • >Txn/EOriginalSSPlusFieldSupport = 1 (true) in the request file
    • a document contains fillable fields or checkboxes (as indicated in a FillableFieldSet>FillableCheckbox container within the Expere response) but does not have an eSignature field (<SignaturePointSet/>)

    See SmartSign Plus® Feature Guide > Applying SmartSign+ to Expere documents > EOriginalSSPlusFieldSupport use cases for more information.

  • EOriginalSSPlusExpirationType updated to include "DIRECT_TO_PRINT" and "EXPIRE_TO_PRINT" options (PBI 818313): The EOriginalSSPlusExpirationTypeType XPath has been updated to include enumerated values of 'DIRECT_TO_PRINT' and 'EXPIRE_TO_PRINT' (replacing "TRID"). Additional values are "NONE" and "SCHEDULED".
  • File name passed to SmartSign+ using Expere "InstanceDisplayName" (PBI 817949): the file name being passed to SS+ has been updated to use the Expere InstanceDisplayName; any invalid file name characters are removed from the InstanceDisplayName.
WCAG: Expere Engine enhanced to support embedded and Tagged .PDF's - May
  • Type: Enhancement
  • Reference: PBI 813603, 821765
  • Documentation Impacts: See below for any pertinent links.
Summary: As a part of our continued effort to create WCAG compatible documents we have updated the Expere Engine to now support the generation of Tagged .PDF documents. We will continue making enhancements to the Expere Engine for Tagged .PDF support, so check back for items being identified and corrected. As part of our continued work to support Tagged .PDF's, we have implemented enhancements to resolve the following WCAG-related changes in the May release:
  • LinkReferences in Header Rows in split tables behavior enhanced (PBI 813603, 821765): it was reported that when a data table was split between pages containing a LinkReference in a header row, the table appeared as two different groupings of tags in the Adobe Acrobat tag tree, and the linked text (<LinkText/> element did not appear in the Adobe Acrobat tag tree for the first page.

    This behavior has been resolved in the Adobe Acrobat tag tree: a table previously split into two tables between pages now appears as one table, and the LinkReference text displays correctly
SMART Doc address logic enhanced
  • Type: Enhancement
  • Reference: PBI 821734
Summary: The Expere Engine updated how the following values within the <PARSED_STREET_ADDRESS> inside the <PROPERTY> element of the SMARTDoc are set (see screenshot below):
  • _DirectionSuffix (i.e. SW)
  • _StreetSuffix (i.e. HIGHWAY)


Additionally, Expere will no longer set a value for _StreetType.
eOriginal SmartSign Web: Support for Corrective Placeholder eNote and SmartDoc XML Request added
  • Type: Enhancement
  • Reference: PBI 814433
Summary:Support for the Corrective Placeholder and SmartDoc XML request have been updated so that if a new eNote and/or other documents are generated they will appear above the old documents when signing.
Note: If viewing through SmartSign Web, the documents are not reordered in the main display.
DocViewer: FooterNotice element now ignored
  • Type: Enhancement
  • Reference: PBI 813734
Summary: DocViewer has been updated to now ignore the FooterNotice element. Previously, DocViewer did not display any FooterNotice elements; however, if the REQ included any xpath data items within the FooterNotice, it caused problems with subsequent locations for the xpath in the document display. As a result, FooterNotice elements are now ignored in addition to not being displayed within DocViewer.

April

Note: Please read the following deployment related information:
  • We are rescheduling maintenance for the Production environment of Expere Document Services to address a customer-reported issue identified in the Customer Test environment. The reported issue is unique to a particular EZ Config Default Data user scenario.
  • A supplemental April CT release was deployed on April 12th that rolled back Expere and EZ Config Default Data-related changes noted below.

    Users may have seen changelogs to support Multiple Commercial Notes (PBI 801194) and Multiple IRA Plans (PBI 810106) in a single transaction. However, due to the defect corrected in the April 12th supplemental CT release, those changes had been shelved and placed in the Redacted section at the bottom of the April section in the Hosted Expere Changelog, and will be part of a future release.

Expere: document generation issue resolved when passing in a non-existent EZ Config product
  • Type: Defect
  • Reference: PBI 822668
Issue: Expere document generation failed when passing in an EZ Config product that did not exist.
Note: This defect was not introduced in our production deployment.
Solution: As a result, documents will generate when passing in an EZ Config product that does not exist.
Expere is updated so that DisplayName is optional
  • Type: Enhancement
  • Reference: PBI 821935
Summary: users reported that the UpdateTransaction API call produced a "Display Name not found" error in the Customer Test environment. This issue was discovered following the April 9, 2024 deployment and is related to the UpdateTransaction changes to support Multiple Commercial Notes and Multiple IRA Plans in a single transaction using EZ Config Default Data.

As a result, these enhancements that were deployed to the CT environment on April 9 have been rolled back; they will be redeployed in a future release.
Note: The items below were deployed as part of the original April CT release.
Expere: SmartSign Plus® integration
Summary: as part of our ongoing work to integrate SmartSign Plus® with Expere, the following functionality has been implemented for the April release:
  • Expiration settings updated when adding a package (PBI 804478): users can pass expiration settings that allow a package to be sent to Print Fulfillment. For more information, see Expere Transaction XPaths for eOriginal > /Txn/EOriginalSSPlusExpirationType.
  • PrintFulfillment elements added to PackageInformation element (PBI 805559, 814058): users can now return Print Fulfillment information within the <PackageInformation/> element. This element contains several child elements, detailed information of which can be found here: SmartSign Plus® Feature Guide > Expere Transaction XPaths for eOriginal and Expere Document Services Web Services Guide > PackageInformation.
  • SSN and custom PIN now populate (PBI 810038): SSN and Custom PIN values are now retrieved from the Participant container and passed to SmartSign Plus participants.
  • <FieldName/> naming convention updated to support "*" (wildcard) for Signer (PBI 812414): for handling the signer identified as '*' or wildcard meaning any signer of the document can fill-in or sign the specified field, for Phase 2, due to limitations of SS+, the Engine needs to assign these fields to the 1st signer of the document.
  • Radio button behavior enhanced with Embedded PDF documents (PBI 813395): it was intended that radio buttons did not function as expected on Embedded PDF documents; for example, users could select both options if two radio buttons were present. The expected behavior was that only one option could be selected; selecting an option would deselect the other option. This behavior has been enhanced, so that radio buttons are generated correctly on Embedded PDF documents.
  • Ability to set the access method for document signing (PBI 810008): users can now set the access method using a new EOriginalSSPlusAccessMethodType XPath with a value of either EMAIL or API. See Expere Transaction XPaths for eOriginal > /Txn/EOriginalSSPlusAccessMethodType for more information.
    Note: If using eOriginal Closing Center, the value must be set to "API" which will trigger an in-person signing. If passed in the transaction, it would override EZ Config Packages and Packets package (PKG) setup.
  • Ability to add participants to an eNote and other documents (PBI 811671): eSign documents with missing participants are now converted to "Paper" and assigned to all other participants. See eNote Workflow Outline for more information.
  • XPath added for users intending to use eOriginal Closing Center (PBI 807494): a new XPath, /Txn/EOriginalUseClosingCenterInd, has been added alllowing users to indicate if they intend to use Closing Center. See Expere Transaction XPaths for eOriginal for more information.
WCAG: Expere Engine enhanced to support embedded and Tagged .PDF's - April
  • Type: Enhancement
  • Reference: PBI 801184, 797053
  • Documentation Impacts: See below for any pertinent links.
Summary: As a part of our continued effort to create WCAG compatible documents we have updated the Expere Engine to now support the generation of Tagged .PDF documents. We will continue making enhancements to the Expere Engine for Tagged .PDF support, so check back for items being identified and corrected. As part of our continued work to support Tagged .PDF's, we have implemented enhancements to resolve the following WCAG-related changes in the April release:
  • Signature and Date order behavior enhanced (PBI 801184): it was reported that the eSignature and Date fillable fields were displayed out of order in the Adobe Acrobat tag tree, resulting in synthentic screen readers to read tags in an incorrect order. Expere has been enhanced to display the eSignature and Date fillable fields in the correct order in the Adobe Acrobat tag tree.
  • Multiple column list behavior enhanced when split across pages (PBI 797053): it was reported that when lists were present in multiple columns and spanned two pages, the lists were incorrectly tagged in the Adobe Acrobat tag tree as two lists. The expected behavior was despite the lists spanning two pages, the lists should have been tagged as one list. This behavior has been enhanced, lists that exist within multiple columns and span two pages are now tagged as one list in the Adobe Acrobat tag tree.
Engine: Remove option to specify FOP version
Summary: The Expere Engine was updated to remove the option to specify FOP26. As a result, the following actions have been implemented:
  • The bsi.properties file, used to control certain properties, has been updated to remove the com.bankerssystems.expere.render.FOP26 property.
  • SelectAndGenerate and Generate requests have removed references to the FOP26 element. As a result, the Expere Engine will disregard any attempt to pass this element in with a value of "false".
Engine: Updated to use Amazon Corretto 17.0.10.7.1 with WildFly
  • Type: Enhancement
  • Reference: PBI 818222
Summary: The Expere Engine has been updated to use Amazon Corretto 17.0.10.7.1 with WildFly. No user action is required.
Expere / eOriginal: schema 24.1 updated for use with SmartSign Plus® and SmartSign Web
  • Type: Enhancement
  • Reference: PBI 815754
Summary: The eOriginal Schema has been updated from 24.0 to 24.1 for use with SmartSign Plus® and SmartSign Web. There were no updates that impacted users.
Expere / eOriginal SmartSign Web: Duplicate ID's supported
  • Type: Enhancement
  • Reference: PBI 814002
Summary: Duplicate Rembrandt ID's can be passed in the transaction if more than one role is represented by the same party (for example: borrower and trustee) without the transaction failing.
DocViewer: Default Data information now passed with BeginSession call
Summary: Document Generation Services (DGS), Expere Document Services (EDS), and DGS Core were enhanced so that Expere EZ Config Organization and Product information can now be passed to DocViewer with a BeginSession API call along with an Expere Generate API call.
Note: Refer to the links above for detailed information on using this new functionality.
DocViewer retains Completed/Create PDF checkboxes when Packages and Packets is used
  • Type: Enhancement
  • Reference: PBI 709564
Summary: The Completed and Create PDF checkboxes are now retained in DocViewer when EZ Config Packages and Packets is used. This functionality already existed for documents and packages passed in without Packages and Packets.
DocViewer: Aggregate adjustment amount
  • Type: Enhancement
  • Reference: PBI 815534
Summary: DocViewer has been updated to ensure that the Aggregated Adjustment amount now displays on the Closing Disclosure and Loan Estimate documents displayed within DocViewer. Previously the Aggregated Adjustment amount was not visible within DocViewer despite successfully displaying within the generated PDF.
DocViewer: Mortgage acknowledgement section and Authority document updated
  • Type: Defect Correction
  • Reference: PBI 820322
Summary: DocViewer has been updated to ensure that the values for by, of, and of in the Acknowledgement section of the Mortgage document now populate with data when both collateral owners are individuals.

Additionally, the Note Information Inclusion dropdown field now correctly displays on the Authority document. Previously, these values were blank.

Redacted

Expere: UpdateTransaction method enhanced to support multiple IRA plans
Summary: Expere has been updated so that multiple IRA plans can be submitted in one transaction and be assigned a specific product for each IRA plan when /Txn/Deposit/IRAPlans/IRAPlan/EZConfigIRAPlanProductDesc is passed in the transaction. When needing to support the multiple IRA Plans in a given transaction, for the data to merge properly, the EZConfig Default Data Product associated to the IRA Plans must only contain an IRA Booklet Policy and the EZ Config Default Data Product associated to the Account should not contain an IRA Booklet Policy.
Expere: UpdateTransaction method enhanced to support multiple commercial notes
Summary: Expere has been updated so that multiple Commercial Notes can be submitted in one transaction and be assigned a specific commercial product for each Commercial Note when /Txn/Notes/Note/EZConfigCommercialProductDesc is passed in the transaction.
Note: In order to utilize this feature, users must consume an updated base content package that supports this feature. The content used with this feature must be consumed with version 24.01 or newer as data points were moved between the EZ Config Default Data .REQ files; see the January 2024.01 content release notes for more information.

March

Note: A supplemental March CT release was deployed on March 19th that promoted changes made in PBI 818343.

Users may have seen changelogs pertaining to the Saxon upgrade (PBI 810458) and two line break scenarios (PBI's 800837 and 740793) that were resolved. However, due to the defect corrected in the March 19th supplemental CT release, those changes had been been shelved and placed in the Redacted section at the bottom of the March section in the Hosted Expere Changelog. These changes for PBI's 800837 and 740793 are now part of the May release.

Engine: Line break issues resolved
  • Type: Defect
  • Reference: PBI 818343
Issue: a user reported that when generating a PDF document, a data point containing text authored in a standard font specified by Expere resulted in a font change when line breaks were present (<br/>). Additional analysis determined that this issue only occurred when the text followed a checkbox; the text after the line break placement changed to a different font than what was desired when a checkbox was present because a Pi font is used to produce the symbol of a checkbox.
Solution: this issue has been resolved by reverting to the previously supported version of Saxon so that fonts are preserved in a text string despite the existence of line breaks.
Note: The items below were deployed as part of the original March CT release.
Engine: FOP 2.8 upgrade
Summary: the Expere Engine has been updated to use FOP 2.8 exclusively when generating documents; users will no longer need to pass in a FOP26=true element and value in transaction when generating documents. Hosted Expere users are not required to make any changes; on-prem Expere users are required to set FOP26=true in their installed BSI.Properties file.
Note:
  • As part of this upgrade, Expere will no longer generate documents using FOP 1.1.
  • The FOP26 element will be removed in a future release.
Expere: SmartSign Plus® integration
Summary: as part of our ongoing work to integrate SmartSign Plus® with Expere, the following functionality has been implemented for the March release:
  • Ability to add participants (PBI 771091): users can now pass participants in as a Borrower.
    Note:
    • If the participant <EmailAddress/> is not provided in the request on an E-Sign document, the following warning message will appear: Signing Party with <RembrandtID> is missing email, package will not be completed, please reorder package or log into SmartSign Plus to complete. <SmartSign Plus environment URL>.
    • Documents without participants will be viewable by all participants.

    For more information, refer to the eNote Workflow Outline.

  • Ability to return Package Information (798140): users can now return Package Information with values for the following parameters:
    • /Txn/EOriginalSSPlusGroups
    • /Txn/EOriginalSSPlusGroups/EOriginalSSPlusGroup
    • /Txn/EOriginalSSPlusGroups/EOriginalSSPlusGroup/GroupName
    Note: This work is related to work done in PBI 799271.
DocViewer: Stylesheet and version information now passed with Generate request
Summary: Document Generation Services (DGS), Expere Document Services (EDS), and DGS Core were enhanced so that the stylesheet and version information can now be passed to DocViewer with a BeginSession API call along with an Expere Generate API call. Previously, when a Generate request was used for merging transaction data between Expere and EZ Config Default Data, stylesheet and version information must be passed in a separate API call.
Note: Refer to the links above for detailed information on using this new functionality.
WCAG: Expere Engine enhanced to support embedded and Tagged .PDF's - March
  • Type: Enhancement
  • Reference: PBI 810310, 812027, 805562
  • Documentation Impacts: See below for any pertinent links.
Summary: As a part of our continued effort to create WCAG compatible documents we have updated the Expere Engine to now support the generation of Tagged .PDF documents. We will continue making enhancements to the Expere Engine for Tagged .PDF support, so check back for items being identified and corrected. As part of our continued work to support Tagged .PDF's, we have implemented enhancements to resolve the following WCAG-related changes in the March release:
  • Character Encoding behavior enhanced (PBI 810310): it was reported that Tagged PDFs were producing a "Character Encoding Failed" exception in Adobe Acrobat when running its Accessibility Checker. Internal analysis determined that generating a Tagged PDF with an <ESignatureAndFieldSupport/> ancillary output with <eSignatureCoordinatesOnly/> and <NonSignatureFieldCoordinatesOnly/> coordinates set to "true" in the request were causing this exception. See below for code sample:
    
<AncillaryOutputsDoc>
	<AncillaryOutput>
		<OutputType>ESignatureAndFieldSupport</OutputType>
		<ESignatureAndFieldSupport>
			<!-- A boolean value to determine if eSignatures should be repressed in favor of X/Y coordinates. -->
			<!-- Values: true, false -->
			<eSignatureCoordinatesOnly>true</eSignatureCoordinatesOnly>
			<!-- A boolean value to determine if eSignature date is supported. -->
			<eSignatureDateSupport>true</eSignatureDateSupport>
			<!-- The text that will be used for the eSignature tooltip -->
			<eSignatureTooltip>ESignature ToolTip</eSignatureTooltip>
			<!-- The text that will be used for the eSignature initials tooltip -->
			<eSignatureInitialsTooltip>ESignature Initials ToolTip</eSignatureInitialsTooltip>
			<!-- A boolean value to determine if all acroform fields that are not eSignature should be repressed in favor of X/Y coordinates. -->
			<!-- Values: true, false -->
			<NonSignatureFieldCoordinatesOnly>true</NonSignatureFieldCoordinatesOnly>
			<!-- A boolean value to determine if eSignatures initial fields should render as Text fields -->
			<!-- Values: true, false -->
			<eSignatureWKES>false</eSignatureWKES>
		</ESignatureAndFieldSupport>
	</AncillaryOutput>
</AncillaryOutputsDoc>

    This behavior has been updated so that Tagged PDFs using eSignatureAndFieldSupport ancillary output with <eSignatureCoordinatesOnly/> and <NonSignatureFieldCoordinatesOnly/> coordinates set to "true" in the request now pass an Adobe Acrobat Accessibility Check.

  • Path Object Not Tagged behavior enhanced (PBI 812027): it was reported that Tagged PDFs were producing a "Path Object Not Tagged" exception in the PAC 2021 Accessibility Checker. Internal analysis determined that this error occurred when using the <ESignatureAndFieldSupport/> ancillary output. This behavior has been enhanced so that using an <ESignatureAndFieldSupport/> ancillary output when generating a Tagged PDF document no longer results in a "Path Object Not Tagged" exception in the PAC 2021 Accessibility Checker.
  • "Text with insufficient contrast" behavior enhanced with multiple LinkText elements (PBI 805562): it was reported that Tagged PDFs were producing a "Text with insufficient contrast" exception in the PAC Accessibility Checker when multiple LinkText references (which are authored in the native .REQ file) are present in the the footer of a document. This behavior has been updated so that TaggedPDF documents (individual / merged PDF documents) containing multiple links related to a specific LinkText element do not result in a "Text with insufficient contrast" exception in the PAC Accessibility Checker.
Expere: SMART Doc PDF copy updated to return SignaturePointSet
Summary: Expere SMART Doc functionality has been enhanced to include a <SignaturePointSet/> container and corresponding information in the Expere response for the PDF Copy of an eNote when the eNote has been specified to be eSignable in the REQ's Properties. Typical behavior for an eSignable document is to also have esignature fields and be fillable and also be identified as eSign in the response for <InstanceSigningInstructions/>. The PDF Copy for an eNote will not have esignable fields and will have a designation of NoSignatures for <InstanceSigningInstructions/>.
Engine: Document assembly behavior updated when using images with a Tagged PDF
  • Type: Enhancement
  • Reference: PBI 799727
Summary: It was reported that images failed to display on some generated Tagged PDF documents. After internal analysis was conducted, it was determined that Expere should be updated to fail transactions and not generate documents when images are not located and cannot be printed on the document.
Note: This enhancement will only affect those documents assembled with FOP 2.8.
Expere EZTransform: internal components upgraded
  • Type: Enhancement
  • Reference: PBI 808933, 805138, 809282
Summary: As part of a regular cadence to review and upgrade any items used with our Expere applications, we have upgraded the following: EZTransform to use the following third-party components:
  • Tomcat 10
  • Java EE 10
  • Java SE 21
Expere: new Expere Workflow Guide available
Summary: A new Expere Workflow Guide has been created that provides detailed information on various common workflows when using Expere. Additionally, this guide contains information about key Expere-related concepts, such as Autoselection and Callbacks.
Note: This guide will be periodically updated with additional workflows, key concepts, and other pertinent information.
Expere: field order behavior enhanced
  • Type: Enhancement
  • Reference: PBI 812001
Summary: Users reported that documents were not populating in their loan origination system due to elements appearing in incorrect order in the Expere Response. As a result, functionality has been added to Expere to reorder the Response elements when necessary.
DocViewer: US Territories supported
  • Type: Enhancement
  • Reference: PBI 811107
Summary: DocViewer has been updated to support the following US Territories:
  • American Samoa (AS)
  • Guam (GU)
  • Commonwealth of Northern Mariana Islands (MP)
  • Commonwealth of Puerto Rico (PR)
  • U.S. Virgin Islands (VI)
DocViewer: Sorting behavior enhanced
  • Type: Enhancement
  • Reference: PBI 779680
Summary: DocViewer has been enhanced so that fees are sorted for any document that contains a SortByValue, including the Loan Estimate Addendum.
DocViewer: expected language not appearing
  • Type: Enhancement
  • Reference: PBI 808874
Summary: On the Note Commercial Line of Credit Non Revolving, there is certain language which was not appearing in DocViewer. This language should appear, depending upon whether an element exists in the XML. DocViewer has been enhanced to accommodate if the element exists or does not exist and to display the proper language.

Redacted

Engine: Saxon 10.9 upgrade
  • Type: Enhancement
  • Reference: PBI 810458
Summary: As part of the regular comprehensive security tests that are run against Expere components, we have updated the Expere Engine to use Saxon version 10.9.

February

Expere: SmartSign Plus® integration
Summary: as part of our ongoing work to integrate SmartSign Plus® with Expere, the following functionality has been implemented for the February release:
WCAG: Expere Engine enhanced to support embedded and Tagged .PDF's - February
  • Type: Enhancement
  • Reference: PBI 803558, 799649
  • Documentation Impacts: See below for any pertinent links.
Summary: As a part of our continued effort to create WCAG compatible documents we have updated the Expere Engine to now support the generation of Tagged .PDF documents. We will continue making enhancements to the Expere Engine for Tagged .PDF support, so check back for items being identified and corrected. As part of our continued work to support Tagged .PDF's, we have implemented enhancements to resolve the following WCAG-related changes in the February release:
  • Watermark functionality added with Embedded PDF files (PBI 803558): users can now use a Watermark ancillary output with an Embedded PDF file. Additionally, internal analysis determined that the presence of an Embedded PDF Barcode Cover Page was included in the page count of the entire document. As a result, Expere has been enhanced so that the cover page was not included in the page count when generating an Embedded PDF with a Barcode Cover Page. For more information, see ADA Implementation Strategies Guide > Working with Watermarks and Expere Developers Guide > Watermarks (Self-hosted users) / Implementation Strategies > Watermarks (Hosted users).
  • Ancillary process flows updated (PBI 799649): updates were made to our ancillary process flows; as a result, no customer-facing changes were implemented.
Expere: Partial Document list functionality updated to support Embedded PDF documents
Summary: in March 2023 (PBI 744444), we informed you that the Expere Engine was enhanced support the selection of either a full or partial document list. As part of this overall effort, Partial Document List functionality has been updated to include EmbeddedPDFs in the Partial Document List.
Expere: Notary and Recordable document behavior enhanced when using namespace prefixes
  • Type: Enhancement
  • Reference: PBI 805425
Summary: It was reported that recordable and notary documents were being returned as "ESign" instead of "InkSign" when /Txn/ExcludeESignatureAndENotaryInd=1 was passed in the transaction .XML and when a namespace prefix was defined.

This behavior has been modified so that Expere now supports namespace prefixes when /Txn/ExcludeESignatureAndENotaryInd is specified.
Tool Suite: Loan Number extracted from VMP MISMO XPath
  • Type: Enhancement
  • Reference: PBI 802347 (Hosted Expere / Expere Document Services), 796750 (Document Generation Services)
Summary: A Loan Number that exists within the VMP MISMO /LOAN/_APPLICATION/MORTGAGE_TERMS/@LenderLoanIdentifier XPath can now be used as a value for a transaction within the Loan Number column in the Tool Suite > SUPPORT Page > search results list.
Document Generation Services Tool Suite:

Expere Document Services Tool Suite:

Expere / eOriginal: schema 24.0 updated for use with SmartSign Plus® and SmartSign Web
  • Type: Enhancement
  • Reference: PBI 797709
Summary: The eOriginal Schema has been updated from 14.5 to 24.0 for use with SmartSign Plus® and SmartSign Web. There were no updates that impacted users.

January

Expere: SmartSign Plus® integration
Summary: as part of our ongoing work to integrate SmartSign Plus® with Expere, the following functionality has been implemented for the January release:
  • PackageInformation element added to request & response (PBI 799271): the Generate and SelectAndGenerate requests have been updated to pass in package information (<PackageInformation/>) as part of the <InlinePackage/> element, Additionally, the <DocSet/> element returns this <PackageInformation/> element and values in the Expere response file. The <PackageInformation/> is being added to support the upcoming functionality of setting up SmartSign Plus integration information in EZ Config Packages and Packets for a given package.
    Note: Additional elements will be added to the PackageInformation element as development continues.
  • New custom fields added (PBI 795113): custom fields Expere EDS ID and Expere DGS ID have been implemented and can now be passed to SmartSign+ for notifications. These pre-configured settings are available within SmartSign Plus® Admin > Settings > Doc and Package Mgmt > Custom Fields; the values must be an exact match.
  • SSN field can be passed in transaction for auto-registration (PBI 799087): users may now include an optional SSN value in the transaction that can be used when completing auto-registration in MERS.
  • Support enhanced for HELOC vaulting (PBI 797989) In order to support vaulting of the HELOC note, Expere has been updated to return values in the response for <Vault/> and <FinancialAsset/> elements if present within a document that is part of a document package. The response file will resemble the following:
    
<r:PackageDoc PackageDocID="PKGD.AffidavitOfMortgagorNJ_Copy">
    <r:DocDescriptor>
                     <r:DocID>PKGD.AffidavitOfMortgagorNJ_Copy</r:DocID>
                     <r:DocType>Dynamic</r:DocType>
                     <r:DocDisplayName>Affidavit of Mortgagor-NJ</r:DocDisplayName>
                     <r:DocRootEntityName>INS.AffidavitOfMortgagorNJ_Copy</r:DocRootEntityName>
                     <r:ESignatureDocument>true</r:ESignatureDocument>
                     <r:Vault>true</r:Vault>
                     <r:FinancialAsset>true</r:FinancialAsset>
    </r:DocDescriptor>
    <r:DocWorkOrder>
                     <r:DocPrepare>true</r:DocPrepare>
                     <r:DocAutoselected>false</r:DocAutoselected>
                     <r:DocSuggested>false</r:DocSuggested>
                     <r:DocFormat>TaggedPDF</r:DocFormat>
                     <r:DocStyle>WKFS_StyleGuide</r:DocStyle>
    </r:DocWorkOrder>
</r:PackageDoc>

    See Expere Document Services Web Services Guide > DocDescriptor for more information.
DocViewer: additional output format supported
  • Type: Feature
  • Reference: PBI 796964
Summary: As part of our support of additional output formats, DocViewer has been enhanced to support a new date output of "MM/YYYY" and "M/YYYY."
Note: Example displays consist of the following:
  • MM/YYYY: 01/2024
  • M/YYYY: 1/2024; 10/2024
WCAG: Expere Engine enhanced to support embedded and Tagged .PDF's - January
  • Type: Enhancement
  • Reference: PBI 802124, 724801, 797968
  • Documentation Impacts: See below for any pertinent links.
Summary: As a part of our continued effort to create WCAG compatible documents we have updated the Expere Engine to now support the generation of Tagged .PDF documents. We will continue making enhancements to the Expere Engine for Tagged .PDF support, so check back for items being identified and corrected. As part of our continued work to support Tagged .PDF's, we have implemented enhancements to resolve the following WCAG-related changes in the January release:
  • Embedded PDF logging functionality enhanced (PBI 802124): logging has been enhanced when an Embedded PDF contains improperly labeled fillable fields so that an entry normally marked as an ERROR is now marked as a WARN. If the list of fillable fields is blank, no WARN entry will be logged.
    Note: When a signature field is improperly labeled, the system will continue to throw an ERROR level message.
  • Watermarks supported in dynamic documents (PBI 724801): dynamic documents have been updated to support the use of watermarks in Tagged PDF outputs. In order to pass accessibility checks, the watermark now contains an alternate text value that is defined when generating an individual tagged or merged tagged PDF. See ADA Implementation Guide > Working with Watermarks for more information.
  • Tag Tree modified for fillable fields in merged PDF (PBI 797968): It was reported that certain Tagged and merged PDFs' tag tree displayed a value for a field that was authored as a fillable field in a document that was not eSignable, specifically a Signature or Acknowledgement section. When the document utilized an eSignatureAndFieldSupport and either a PdfMerge or MergedCopyPdf ancillary output and when the document was not eSignable, the tag tree displayed Form values in some cases. This issue has been resolved so that when generating a Tagged and merged PDF with eSignatureAndFieldSupport ancillary output, the resulting tag tree will NOT display values for fillable fields.
SMARTDoc address logic updated
  • Type: Enhancement
  • Reference: PBI 801206
Summary: Previously when Expere parsed SMARTDocs mailing addresses, it also converted the mailing addresses to comply with that of the USPS (United States Postal Service) mailing address convention. After further analysis, it was determined that Expere will now only parse the mailing addresses as the mailing addresses do not need to adhere to USPS mailing address conventions.
Engine: AnchorText behavior enhanced
Summary: The AnchorText ancillary output functionality has been enhanced based on user feedback. As a result, the AnchorText document included in a document package when the AnchorText ancillary output is selected and lists each document that contains anchors by providing the InstanceDisplayName, the SignerRole, and SignerName values; for example:
Application Disclosure-WI | Borrower | John Doe
Engine: Ancillary Barcode Height option honored
Summary: Expere now supports specifying per-document ancillary barcode height. The barcode height authored in the native REQ file will be applied to that document's ancillary barcode.
Note: Consider the following:
  • Barcode height can be specified for all Expere-supported ancillary barcode types.
  • If no value is specified, then apply the default height value.
  • In scenarios where the barcode type is authored in the REQ while the ancillary specifies a different barcode type, the ancillary barcode type will take precedence.
  • If a document has a footer and a barcode height defined, it is possible the amount of space defined for the footer will need to be adjusted to get the desired output.
  • The maximum barcode height is 44 points / .61 inches. If a larger space is specified when authoring the barcode, additional white space will be reserved, but the barcode height will be 44 points/.61 inches.
Expere: Landscape orientation behavior enhanced for static documents
  • Type: Enhancement
  • Reference: PBI 759968
Summary: Users reported that certain static documents that consisted of both portrait and landscape page orientation did not display the landscape-oriented pages correctly. For example, one document contained portrait orientation all but the last page of the document, which contained a landscape orientation. This last page was inadvertently display the page in portrait orientation and was truncating some of the information. As a result, Expere has been enhanced so that landscape page orientation is now preserved in static documents.
Expere: Engine updated to used Wildfly 30.0
  • Type: Enhancement
  • Reference: PBI 801294
Summary: The Expere Engine has been updated to use WIldfly 30.0.
Expere Document Services: internal changes implemented for transaction errors
  • Type: Enhancement
  • Reference: PBI 801195
Summary: Expere Document Services has been enhanced to address an issue where SelectGenerateDeliver calls were sporadically failing.
EZTransform: Tomcat component upgrade
  • Type: Enhancement
  • Reference: PBI 791921
Summary: EZTransform has been updated to use Apache Tomcat version 9.0.84.
Integrators: DocumentService response mismatched against Swagger
  • Type: Defect
  • Reference: PBI 801311
Issue: Users reported that the Swagger page corresponding to our DocumentService REST API were mismatched as it related to the Generate-Synchronous response and fillable fields, specifically the values associated with the FillableText and FillableFieldelements.
Solution: This behavior has been modified so that the Swagger page is now consistent with the Generate-Synchronous response as it pertains to the FillableText and FillableField elements and values.