Changelog Entries - 2025

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).

December

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:
  • Improved Handling of Package Destruction Requests (PBI 906301): the SmartSign Plus integration was enhanced to handle package IDs more gracefully in redraw requests.

    • Ignored Unknown Package IDs: if a package ID is not found in the database, the system will ignore it without error.
    • Skip Destruction Without Package ID: when destruction is requested but no package ID is provided, the destruction process will be skipped.
    • Logging Verification: system logs now clearly indicate that destruction was not executed in these cases, ensuring transparency and traceability.
  • Multiple RembrandID values now result in a single Participant (PBI 885502): Expere has been enhanced so that when multiple unique RembrandID values are present for the same person responsible for multiple roles, only one Participant ID is created in SmartSign Plus. See SmartSign+ Feature Guide: Print fulfillment workflow > Participant-level > NOTE > First Bullet and SmartSign+ Feature Guide: Expere Transaction XPaths for eOriginal > Participants collection > ...RembrandtIDRefs for more information.
  • (Hosted Expere / DocumentService) Support for Credential Passing Added (PBI 901255, 901254): integrators can now pass credentials directly within the request. Credentials and the appropriate Package ID* can be included as a base64-encoded JSON string in a custom http header (X-SmartSignPlus-Configuration) within the following fields of the request.
    • Login ID
    • API Key
    • Client ID
    • Client Secret
    • Organization ID
    • Lender Name
    • Package ID (used for redraws)
    Sample JSON string:
    
{
  "loginId": "xxxxxxxxxxx",
  "apiKey": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
  "clientId": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
  "clientSecret": "xxxxx-xxxxxxxxxxx-xxxxx",
  "organizationId": "123456789",
  "lenderName": "xxxxxxxxxx",
  "packageId": "" 
}
Expere: Improved PDF Tag Structure for Overflow Field Descriptions
  • Type: Enhancement
  • Reference: 895760
Summary: the tagging and bookmark logic has been enhanced for embedded PDF documents to align with accessibility standards and provide a better user experience.
What's Changed?
  • Heading-Based Bookmarks: Bookmarks are now authored with appropriate heading tags when applicable; for example: H1 - <HeadingText>.
  • Overflow Page Tagging: Overflow pages are displayed as <P> tags in the tag tree, ensuring proper semantic structure.
  • Bookmark Exclusions: Overflow page descriptions are no longer added as bookmarks, reducing clutter and improving navigation.
Impact: these updates enhance document accessibility and ensure compliance with tagging best practices, making navigation clearer for assistive technologies.
SmartSign Web: Enhanced Sort Order Handling for Reverse Register Indicator
Summary: when a reverse register indicator is passed from Expere to eCore, and a new e-note is generated and deposited in the vault, the EO Configure Sort Order process has been updated to ensure accurate document sequencing.
What's changed:
  • The sort order now includes only the Doc ID of the newly generated e-note.
  • The previously signed e-note is excluded from the signing process, preventing duplicate or unnecessary signing actions.
Impact: this enhancement ensures that only the latest e-note is considered for signing when a reverse register indicator triggers a new document creation, improving compliance and reducing operational errors.

November

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 November release:
  • (Document Generation Services) Support for Credential Passing Added (PBI 871078): integrators can now pass credentials directly within the request. Credentials and the appropriate Package ID* can be included as a base64-encoded JSON string in a custom http header within the following fields of the request.
    • Login ID
    • API Key
    • Client ID
    • Client Secret
    • Organization ID
    • Package ID (used for redraws)
    Sample JSON string:
    
{
  "loginId": "xxxxxxxxxxx",
  "apiKey": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
  "clientId": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
  "clientSecret": "xxxxx-xxxxxxxxxxx-xxxxx",
  "organizationId": "123456789",
  "lenderName": "xxxxxxxxxx",
  "packageId": "" 
}
    Note: Consider the following:
    • *a "packageId" parameter is not used within a custom header for SmartSignPlusPackageStatus, SmartSignPlusFinalize, and SmartSignPlusModifyPackage calls, and is used only in the custom header for redraws.
    • The JSON string is encoded in an "http" header, separate from the <Header/> element within the SOAP:envelope.
    • For more information, refer to SmartSign Plus Feature Guide: Optional Credential workflow
  • Participant data behavior functionality enhanced (PBI 894995 / 901441):
    • (PBI 894995) The Expere Engine and Document Generation Services have been enhanced so if a role does not contain a value, it will remain blank and not be populated with a system value in the Expere response. As a result, it is not assigned to any participant.
    • (PBI 901441) For Document Generation Services users, documents with missing participant data (for example: seller information in lead paint disclosures) are now converted to a paper, or "wet sign" format so that transactions can continue without failure due to unassigned fillable fields.
  • New custom field collection available (PBI 890790): users can now pass in a collection of custom fields when creating a package. See SmartSign+ Feature Guide: Expere Transaction XPaths for eOriginal > Custom fields collection for more information.
    Note: Custom fields must be configured in SmartSign Plus > Administration > Settings > Doc and Package Management > Custom Fields. The field names must match exactly with what is expected by SmartSign Plus custom field configuration to avoid errors.
Hosted Expere integrators: new JSON health check page added
  • Type: Feature
  • Reference: PBI 897374
Summary: integrators may now access a new Hosted Expere Health Check page in JSON format. A sample health check appears as follows:

{
  "status": true,
  "version": "20xx.x.xx.xxxx",
  "conditions": {
    "[DocService] Ping of DocService at https://xx-xx-xx.fsbmi-apps.com/xxxxxxxx/xxxxxx/xxx/xx/xxxxxxxxx.svc": true,
    "[CallbackHandler] Ping of callback handler at https://xx-xx-xx.fsbmi-apps.com/xxxxxxxx/xxxxxx/xxx/xx/xxxxxxxxx.svc": true,
    "[DeliverResponse] Ping of delivery response at https://xx-xx-xx.fsbmi-apps.com/xxxxxxxx/xxxxxx/xxx/xx/xxxxxxxxx.svc": true,
    "[DeliveryService] Ping of DeliveryService at https://xx-xx-xx.fsbmi-apps.com/xxxxxxxx/xxxxxx/xxx/xx/xxxxxxxxx.svc": true,
"[SQLServer]": true
  },
  "checkTime": "2025-09-05T20:59:06.9859343+00:00"
}
Expere: merged PDF behavior enhanced
  • Type: Enhancement
  • Reference: PBI 898176
Summary: users reported an error when attempting to generate a merged PDF document package. It was discovered during our initial triage that a field name value contained an "_" (underscore) as the last character in the value, resulting in the error. As a result, Expere has been enhanced to successfully parse field name values containing underscores.
DocViewer: JSON health check endpoint added
  • Type: Enhancement
  • Sprint: 19
  • Reference: 897518
Summary: The DocViewer application now exposes a machine-readable JSON health check endpoint in addition to the existing HTML health check page. This enables the orchestration pipeline to validate service health programmatically. The new endpoint returns the overall status, build version, a set of boolean condition checks (for content location, schemas folder, session state DB, STS, SWT key), and a timestamp.
Expere: Security issue and Monthly component upgrades
  • Type: Enhancement
  • Reference: PBI 898285, 891874, 891882, 891885, 892146, 892148
Summary: As part of a regular cadence to review and upgrade any items used with the Expere Engine for security issue and monthly component upgrades, we have upgraded the following items to the latest version:
  • Security Issue Upgrades:
    • WildFly
    • Apache Commons Collections
  • Maintenance Upgrades
    • Amazon Corretto Java
    • commons-imaging
    • dom4j
    • log4j
    • SLF4J API Module (org.slf4j:slf4j-api)
Note: No user action is required.
Expere: Web Services Guide enhanced with updated request parameter for Hosted REST API users
Summary: per user feedback, each individual method within the REST API section of the Expere Document Services Web Services Guide has been enhanced with updated request parameters.
Expere: Overflow page description order updated for EmbeddedPDF documents
  • Type: Defect Correction
  • Reference: PBI 876384
Issue: users reported that after generating an EmbeddedPDF document containing an Overflow page, the corresponding Overflow descriptions did not appear chronologically in the order they were authored in the .REQ file.
This was the expected output:

This was actual result:

Solution: Expere has been updated so that the Overflow page descriptions on a generated EmbeddedPDF document appear, chronologically, in the order in which they were authored in the .REQ file.

October

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:
Expere: Security issue and Monthly component upgrades
  • Type: Enhancement
  • Reference: PBI 894060, 889834, 890075
Summary: As part of a regular cadence to review and upgrade any items used with the Expere Engine for security issue and monthly component upgrades, we have upgraded the following:
  • Security Issue Upgrades:
    • WildFly upgraded to the latest available version
    • Apache Commons Lang, version 3.18.0
  • Maintenance Upgrades
    • NA
Note: No user action is required.
Expere / SMARTDoc: Indexing Issues when Iterating over CUSTOM paths resolved
Issue: the following issues were identified when executing SmartDoc transactions that include both borrowers and trusts in the SmartDocData:
  • TRUST Container Indexing: TRUST containers in the ARC data are not starting at index [1] as expected. Instead, indexing continues from the last borrower entry. For example, if there are 4 borrowers, the first TRUST container starts at [5], leaving [1] through [4] empty.
  • INTER_VIVOS_TRUSTEE Indexing Behavior: when multiple trustees are included in the transaction data but only one is applicable, the ARC data still returns containers for all trustees. This results in empty containers for the inapplicable trustees and an unexpected index (e.g., INTER_VIVOS_TRUSTEE[3] instead of starting at [1] for the applicable trustee).
  • _SequenceIdentifier Inconsistency: The _SequenceIdentifier value for TRUST containers is returned as "UpdateSequence". In contrast, BORROWER and INTER_VIVOS_TRUSTEE containers return a numeric value, leading to inconsistency in the ARC data structure.
Solution: the following updates have been implemented to address these issues
  • TRUST Container Indexing: when executing SmartDoc transactions that include both borrowers and trusts, trust-related data now operates independently from borrower data. Trust entries begin indexing at [1], ensuring clear separation and preventing the creation of blank containers.
  • INTER_VIVOS_TRUSTEE Optimization: SmartDoc will no longer return empty containers for trustees marked as inapplicable within the INTER_VIVOS_TRUSTEE data. This streamlines the output and improves clarity.
  • Consistent Sequence Identifier Usage: the _SequenceIdentifier field is now applied consistently across all iterated parties, ensuring uniformity and simplifying downstream data processing.
Expere: XPath compatibility message addressed
  • Type: Defect Correction
  • Reference: PBI 897849
Issue: a user reported receiving an XPath 2.0 Compatibility error message despite having the XPath 1.0 checkbox enabled in the Document Generation Services (DGS) Management Tool.
Solution: the XPath 2.0 Compatibility error message no longer appears if the XPath 1.0 checkbox is enabled in the DGS Management Tool.

September

Expere: SmartSign Plus® integration
Summary:
  • SOAP Integrators: new SmartSignPlusModifyPackage API created (PBI 884596): a new SmartSignPlusModifyPackage SOAP API has been created that allows users to delete, cancel, reactivate, or make any corrections to the package. For more information, refer to Expere Document Services Web Services Guide > SmartSignPlusModifyPackage and Expere - SmartSign Plus® Integration Guide > eNote Destruction Workflow Outline > SmartSignPlusModifyPackage API status definitions and actions.
  • Functionality enhanced when no participant is identified for a document (PBI 883923): Document Generation Services has been enhanced so that discrete party information is used and participants are properly assigned to the generated document(s) when ExecutionType=eSign, and when no signatures are present. When ExecutionType=ESign, and when no signatures are present, the discrete party ID authored in the .REQ file may be used to identify participants.
  • Identity Verification topic added to Integration Guide (PBI 892320): a new Working with Identity Verification help topic has been added to the SmartSign Plus Integration Guide; this topic explains how to pass in additional identify verification-related data points within a transaction. For more information, see Expere - SmartSign Plus® Integration Guide > Working with Identity Verification.
  • Expere: SmartSign Plus naming update in user documentation (PBI 893359): all online Expere help documents referencing SmartSign Plus have been reviewed and updated to ensure consistent terminology, formatting, and content alignment across the platform. This update improves clarity and user experience by maintaining uniformity throughout the help system.
WCAG: Expere Engine enhanced to support embedded and Tagged .PDF's
  • Type: Enhancement
  • Reference: PBI 889352
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 September release:
  • Embedded PDF fillable field behavior enhanced (PBI 889352): it was reported that when attempting to generate a standard PDF using the ESignatureAndFieldSupport ancillary option, fields that should have been fillable were flattened instead (for example: signature fields). This behavior has been enhanced so that generating a standard PDF using the ESignatureAndFieldSupport ancillary option once again results in fillable fields.
Expere: post processing added to support merging select individual documents when using DocumentService REST API
Summary: the DocumentService REST API has been enhanced include a new PostProcess-Synchronous API call to merge select individual documents. A user can now pass in the encrypted Base64 for desired documents through the PostProcess-Synchronous call, which in turn provides a merged PDF of these select documents back to the user.
Callback enhancement
  • Type: Enhancement
  • Reference: PBI 884716
Summary: DocGenService Host has been enhanced to reduce the number of callbacks to mitigate transactions from timing out. More specifically, the “CallBackRetryCount” has been reduced from eight (8) to two (2).
Expere: Barcode2D behavior enhanced for EmbeddedPDF documents
  • Type: Enhancement
  • Reference: PBI 887987
Summary: Expere has been enhanced so when using a Barcode2D with an EmbeddedPDF it results in a barcode that is the same as a Static PDF and can be scanned successfully.
This was the output before the enhancement:

This was output after the enhancement:

Expere: Security issue and Monthly component upgrades
  • Type: Maintenance
  • Reference: PBI 892765
Summary: As part of a regular cadence to review and upgrade any items used with the Expere Engine for security issue and monthly component upgrades, we have upgraded the following:
  • Security Issue Upgrades:
    • WildFly 37.0.0
  • Maintenance Upgrades
    • NA
Note: No user action is required.
DocViewer: Security issue and Monthly component upgrades
  • Type: Enhancement
  • Reference: PBI 888153
Summary: As part of a regular cadence to review and upgrade any items used with the DocViewer for security issue and monthly component upgrades, we have upgraded the following:
  • Security Issue Upgrades
    • System.Text.Json 6.0.11

August

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:
Expere Document Services / EDocServices SOAP API: post processing added to support merging select individual documents
Summary: Expere Document Services has been enhanced include a new PostProcessSynchronous API call to merge select individual documents using the EDocServices SOAP API. A user can now pass in the encrypted Base64 for desired documents through the PostProcessSynchronous call, which in turn provides a merged PDF of these select documents back to the user.
Expere: CUSTOM path support added for SMARTDoc data
Summary: users reported execution errors when attempting to map data under CUSTOM/TRUST in the SMARTDoc. As a result, Expere SMARTDoc functionality has been updated to allow iteration over the //CUSTOM/TRUST[#] and //CUSTOM/TRUST[#]/TRUSTEE[#]) XPaths.
Engine: Saxon upgrade to 12.7
  • Type: Enhancement
  • Reference: PBI 872377
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 12.7.
Expere: Security issue and Monthly component upgrades
  • Type: Maintenance
  • Reference: PBI 885917
Summary: As part of a regular cadence to review and upgrade any items used with the Expere Engine for security issue and monthly component upgrades, we have upgraded the following:
  • Security Issue Upgrades:
    • NA
  • Maintenance Upgrades
    • Amazon Corretto Java 21.0.8_9
Note: No user action is required.
Expere: new Overview Guide available available for Hosted and Self-Hosted Expere users
Summary: a new Expere Workflow Guide is now available that provides a launching point for understanding Expere; items discussed include the following:
  • Technical details
  • Expere workflow processes and charts
  • Security when calling Expere
  • Wolters Kluwer / Expere Support structure
  • Environment monitoring
  • Integration process
  • Supported tools
DocViewer: Security Enhancement
  • Type: Enhancement
  • Reference: PBI 885930
Summary: As part of the regular comprehensive security tests, we have updated mganss/HtmlSanitizer to version 7.1.542.

July

Note: The following item was deployed on July 15 to the Customer Test environment. All items in July will be deployed as expected to the Production environment on Thursday, July 17.
Expere: new indexing indicator added
  • Type: Defect Correction
  • Reference: PBI 885574
Issue: users reported an issue when passing in elements with indexes in their transactions as a result of the feature rolled out in PBI 784650.
Solution: Expere has been updated so users can pass in a new <ReIndexTransactionInd> = '1' element and value in the transaction in order to utilize indexes. No user action is required; by default the <ReIndexTransactionInd> indicator is set to '0' and is not required to be passed in the transaction.
Note: The items below were deployed as part of the original July CT release.
DocViewer: SonarQube Reliability Improvements for DGS Views
  • Type: Enhancement
  • Reference: PBI 872178
Summary: The DGS module previously contained reliability issues in its view components, contributing to a low SonarQube reliability rating. This work focused on addressing those issues to improve code quality and stability, aligning the reliability rating with best practices.
What Was Affected:
  • Code quality and reliability metrics in SonarQube for DGS-related view files
  • View files within the DocViewer and Shared directories of the TestWebApp
Resolution: Recommended reliability fixes were applied to the following files to eliminate SonarQube-reported bugs and elevate the reliability rating from D to A:
  • CreateSession
  • DocViewer
  • _Skin
  • _Layout
These changes reduce technical debt and improve maintainability across the affected components.
Expere: XPath 1.0 Compatibility Mode update
Summary: in preparation of our feature to disable XPath 1.0 Compatibility Mode, com.bankerssystems.expere.xPath_1_0_Compatibility element has been set to "false" in the bsi.properties file. This will officially disable XPath 1.0 Compatibility Mode on all transactions; for more information, refer to the Feature page > XPath 1.0 Compatibility Mode to be disabled
WCAG: Expere Engine enhanced to support embedded and Tagged .PDF's
  • Type: Enhancement
  • Reference: PBI 877546, 879578
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:
  • List items in tag tree enhanced to be semantically meaningful (PBI 877546): it was reported that <Div> tags were present within List teams in the Adobe Acrobat tag tree for a Tagged PDF document, specifically within an <LBody> tag.

    Expere has been enhanced so that all instances of <Div> under an <LBody> are removed; as a result, child tags of the <Div> tag are moved to the <LBody> parent.

  • Logging enhanced (PBI 879578): logging was updated to include a WARN message if an EmbeddedPDF document contains an empty field with a "widget" (a component of a fillable field).
DocServices (Expere Document Services SOAP API): docRequiresSignature removed
Summary: docRequiresSignature has been removed from DocServices SOAP API > DocDescriptor element.
Expere: Logo height and width behavior enhanced
  • Type: Enhancement
  • Reference: PBI 877157
Summary: Expere .NET has been updated to allow an empty value for either the <HeightInInches/> or <WidthInInches/> element when passing in a logo as an ancillary output. The expected behavior is that users can pass in either a <HeightInInches/> or <WidthInInches/> element and Expere will auto-scale the logo; see example below:

<AncillaryOutputsDoc>
	<AncillaryOutput>
		<OutputType>Logo</OutputType>
		<Logo>
			<Image>/9j/4AA...Br9abRRQA1+lNoooA//2Q==</Image>
			<Justification>Center</Justification>
			<Placement>AllPages</Placement>
			<HeightInInches>1.8</HeightInInches>
			<WidthInInches></WidthInInches>
			<AlternateText>Test Logo</AlternateText>
		</Logo>
	</AncillaryOutput>
</AncillaryOutputsDoc>

Expere .NET has been updated to allow either a <HeightInInches/> or <WidthInInches/> element with an empty value when passing in a logo as an ancillary output.
Expere: Security issue and Monthly component upgrades
  • Type: Enhancement
  • Reference: PBI 869411
Summary: As part of a regular cadence to review and upgrade any items used with the Expere Engine for security issue and monthly component upgrades, we have upgraded the following:
  • Security Issue Upgrades:
    • WildFly 36.0.1
Expere: list of supported special characters available
Summary: As part of a request to identify supported and unsupported characters, we have enhanced our user documentation to provide a list of supported characters.
Expere: user documentation enhanced for DiscreteParty scenarios
Summary: the Expere user documentation has been updated to better communicate how Discrete Parties are returned in the response in certain signing and merging scenarios.

June

Expere: SmartSign Plus® integration
Summary: as part of our ongoing work to integrate SmartSign Plus® with Expere,
  • /Txn/EOriginalSSPlusDeliveryType 0, Blank, or Missing logic updated (PBI 872181): the /Txn/EOriginalSSPlusDeliveryType 0, Blank, or Missing logic has been updated to now fully support an Expere-generated eNote. For more information, refer to Expere - SmartSign Plus® Integration Guide > Expere-generated eNote placeholder and Expere-generated dynamic eNote Workflow Outline > Step 7 Note
  • Participant mailing behavior enhanced (PBI 870321): the Expere SmartSign Plus® integration has been enhanced so that the package will succeed when multiple recipients along with mailing information are passed to SmartSign Plus; however, not all participants are intended to be a signer of any given document. For more information, refer to Expere - SmartSign Plus® Integration Guide > Print Fulfillment Workflow.
    Note:
    • For transactions that fall under this use case a "Successful with Warnings" message will be returned. "A mailing request was not generated for Rembrandt ID {id} due to missing participant."
    • The package will be mailed to the participants that fulfill all the SmartSignPlus mailing requirements.
  • SmartSignPlusPackageStatus API created for SOAP and REST integrations (PBI 861050 / 861051):
    • users can now retrieve a SmartSignPlus package status with either a new SmartSignPlusPackageStatus SOAP or REST API call, depending on their integration. For more information, refer to the following topics within the Expere Document Services Web Services Guide:
  • Optional Custom Packet Document Data (PBI 871220): the Generate and SelectAndGenerate Request and Responses (used with Expere EZ Config Packages and Packets in this case) have been updated to include a new optional PacketDocumentCustomDataItems element within the DocumentRef element. For more information, refer to Expere Document Services Web Services Guide > DocumentRef and PacketDocumentCustomDataItems.
    Note: The PacketDocumentCustomDataItems name / value pair appears as an attribute of the DocInstance element in the Expere response.
  • Expiration Setup-related XPaths deprecated (PBI 871714): the following XPaths have been removed from the Expiration Setup table in the SmartSign Plus® Integration Guide:
    • /Txn/EOriginalSSPlusSingleElectronicPackageEmailAddress
    • /Txn/EOriginalSSPlusSingleElectronicPackageFirstName
    • /Txn/EOriginalSSPlusSingleElectronicPackageLastName

    For more information, refer to Expere - SmartSign Plus® Integration Guide > Expere Transaction XPaths for eOriginal.
Expere: EmbeddedPDF Overflow pages enhancements
  • Type: Feature
  • Reference: PBI 874959, 876382, 871238, 874971
Summary: Expere has been enhanced to support field overflow functionality on EmbeddedPDF documents through the following work items:
  • Tagline element behavior enhanced (PBI 874959): it was reported in some cases where, even when following the proper naming conventions for tagline fields, the fields were not being excluded from the tag tree when generating a PDF. Expere has been enhanced so that the overflow page or primary embeddedPDF document (for example: first page) do not have these <Form> elements in the tag tree and passes accessibility checker; instead, they will appear as artifacts in the Content Panel.
  • Fillable field presence on overflow pages (PBI 876382 / 871238): it was reported that fillable fields were appearing on overflow pages in the following scenarios:
    • when data overflowed onto a second overflow page, fillable fields are present on that second page
    • the dashed lines surrounding the overflow descriptions on the overflow pages when more than one field overflowed

    Expere has been enhanced so that these are not fillable fields on the overflow pages.

  • Multiple overflow desciption bolding behavior updated (PBI 874971): it was reported that when multiple overflow descriptions were present, the Adobe Acrobat Accessibility Checker failed and the first overflow description was bolded while the remaining overflow descriptions appeared with no additional formatting. After further investigation, it was determined that the first overflow description was being created twice causing it to appear bold as well as causing the accessibility to fail. Expere has been enhanced so that the overflow descriptions are only produced once so that they do not appear bold and preventing an accessibility error.
Expere: SMARTDoc _StreetAddress parsing logic updates
Summary: Expere has enhanced the Street Address inside a SMARTDoc. If the incoming _StreetAddress value is 100 characters or less, Expere will place that entire value into _StreetName. This will help prevent incorrect parsing when the address is more unique (i.e. does not have a road designation, for example:. "St", "Ave", "Ln", etc). If the _StreetAddress value is greater than 100 characters, Expere will continue to parse _StreetAddress into its various component, for example: _HouseNumber, _DirectionPrefix, etc.
Note: The 100 character limit is a MERS restriction on the length of _StreetName.
Expere: indexes added for elements for UpdateTransaction
Summary: a user requested that Index values be added to all elements to all "collection containers" (i.e. parent elements) in UpdateTransaction returned transaction. As a result, the merged transaction resulting from Expere’s UpdateTransaction has been updated to include Indexes for all elements sequentially, retaining the order of the items as they exist.
Expere: Logging enhanced
  • Type: Enhancement
  • Reference: PBI 877158, 878579, 872893
Summary: we have made the following logging enhancements:
  • (PBI 877158) Logging was updated to include references to FOP rather than FOP 2.6.
  • (PBI 878579) As part of a larger effort to analyze usage of ESignatureAndFieldSupport and SignaturePointSet ancillary outputs, we have added an INFO level logging message when ESignatureAndFieldSupport and SignaturePointSet ancillary outputs are used together in the same transaction request.
  • (PBI 872893) Expere has been enhanced to now log a WARN message if the transaction data provides the same ID for two or more different parties.
DocumentService: docRequiresSignature removed
Summary: docRequiresSignature has been removed from DocumentService REST API > DocDescriptor element.
Expere: Security issue and Monthly component upgrades
  • Type: Maintenance
  • Reference: PBI 869003, 869373
Summary: As part of a regular cadence to review and upgrade any items used with the Expere Engine for security issue and monthly component upgrades, we have upgraded the following:
  • Security Issue Upgrades:
    • Microsoft.AspNetCore.Metadata 8.0.15
    • WildFly 36.0.0
  • Maintenance Upgrades
    • Amazon Corretto Java 21.0.7.6.1
Note: No user action is required.

May

Note: The following items were deployed on May 13, 2025 to the Customer Test environment. All items in May will be deployed as expected to the Production environment on Saturday May 17, 2025.
Expere: Discrete Party behavior enhanced
  • Type: Defect Correction
  • Reference: PBI 877684
Issue: users reported that discrete parties were not being created properly when an '_' (underscore) was present in the ID value.
Solution: Expere is updated to support an '_' (underscore) in an ID value so that no invalid Signers nor Discrete Parties are created.
Expere: TaggedPDF overrides DocumentRef element attribute for docFormat
  • Type: Defect Correction
  • Reference: PBI 866545, 877868
Issue: it was determined that when a packet contains documents in which some are specified to generate as Tagged PDF and some are specified to generate as a standard PDF, all documents were generated as a Tagged PDF.
Solution: Expere now generates Tagged PDF and standard PDF documents when specified in the request.
Note: If generating a merged PDF document, a message will appear in the logs stating the merged PDF document contains a combination of standard and Tagged PDF documents.
Note: The items below are part of the standard May release.
Expere: SmartSign Plus® integration
  • Type: Feature
  • Reference: PBI 870982, 861050
Summary: as part of our ongoing work to integrate SmartSign Plus® with Expere,
  • Participants behavior enhanced (PBI 870982): Expere has been enhanced to omit calling the SmartSign Plus Add Participants API when no participants are included in the transaction. Previously, the following would appear if no participants were included in the transactions:
    • field":"participants","message":"size must be between 1 and 2147483647"
  • New SmartSignPlusPackageStatus SOAP API available (PBI 861050): a new SmartSignPlusPackageStatus SOAP api is now available to retrieve the package status.
Expere: EmbeddedPDF Overflow pages enhancements
  • Type: Feature
  • Reference: PBI 869646, 871232
Summary: Expere has been enhanced to support field overflow functionality on EmbeddedPDF documents through the following work items:
  • PrintEntireContentOnTheOverflowPage updated (PBI 869646): Expere has been updated so that EmbeddedPDF documents with overflow Pages in which a source field specified PrintEntireContentOnTheOverflowPage now only prints the entire content on the overflow page when the content does not fit in the source field.
  • Forwarding Message update (PBI 871232): Expere no longer adds an asterisk ("*") to the end of the Forwarding Message when the PrintEntireContentOnTheOverflowPage overflow option is used with EmbeddedPDF documents.
    Note: The Forwarding Message behavior now functions identically between EmbeddedPDF and Static documents.
Engine: Discrete party behavior enhanced in response file
Summary: users reported that the non-authored discrete party information was not being returned in the response file when the <DiscreteParty> element was manually authored in the REQ source file. The expected behavior is that Expere should return discrete party information automatically in the response.
This behavior has been enhanced so discrete party information is always returned in the response.
Note: Expere will not return duplicate <DiscreteParty> elements in the response. In the scenario in which there are duplicate discrete parties, the manually authored <DiscreteParty> and its elements will be the one provided in the response.
Expere: Logging enhanced for packet-level ancillary output options
  • Type: Enhancement
  • Reference: PBI 868637
Summary: we have modified logging regarding packet-level ancillary output options as part of the development completed for PBI's 851089 and 848145.
Expere: Addressing document generation failures when specifying SmartSign Plus ®
  • Type: Defect Correction
  • Reference: PBI 874154
Issue: it was reported that certain documents failed when requesting SmartSign Plus ®. Analysis determined that the Expere Engine did not handle the namespace properly, ultimately throwing a null pointer exception.
Solution: Expere has been updated to successfully generate documents when SmartSign Plus® is requested.
Engine: Signature in FooterNotice behavior addressed when generating a Tagged PDF
  • Type: Defect Correction
  • Reference: PBI 869991
Issue: a user reported that Tagged PDF documents failed to generate. Internal analysis revealed that If a footer or header containing a signature field was present on the last page of a document without any other tagged content, the document would fail to generate.
Solution: Expere now generates Tagged PDF documents successfully if a Footer Notice or Header Notice includes a Signature Field and is the only content present on the last page of a document.
Engine: functionality reverted related to header and footer notices
  • Type: Defect Correction
  • Reference: PBI 870220
Issue: a user reported that a custom document failed to generate with a Tagged PDF document format. We determined the enhancement deployed for PBI 860750 inadvertently caused this issue.
Solution: We have rolled back the changes related to PBI 860750. We will release enhancements related to PBI 860750 in a future release.
DocViewer: General Updates
  • Type: Enhancement
  • Reference: PBI 861734
Summary: we have reviewed and upgraded items used with DocViewer for monthly component and security updates, per the PBI number referenced directly above.
Security Administration (Hosted users): General Updates
  • Type: Enhancement
  • Reference: PBI 864107
Summary: we have reviewed and upgraded items used with Security Administration for monthly component and security updates, per the PBI number referenced directly above.
Unsupport Merged PDF Scenarios documented
Summary: we have documented scenarios where a combination of merged PDF, SmartSign Plus®, Expere eNote, and SmartSign Web functionality is present. Refer to the links above for more information.

April

Note: The following item was deployed on April 4, 2025 to Customer Test and Production environments.
Expere: transaction failure issue addressed
  • Type: Defect Correction
  • Reference: PBI 871240
Issue: users reported that some transactions failed to generate documents after the March Production deployment that occurred on March 20. Internal research determined that the issue was cause by XPath 2.0 Compatibility issues.
Solution: Changes were made to allow transactions to use XPath 1.0 compatibility mode.
Note: The items below are part of the standard April release.
Expere: XPath 1.0 Compatibility Mode update
Summary: as part of our April Customer Test environment deployment, we have disabled XPath 1.0 Compatibility Mode. For more information, refer to Hosted Expere Changelog > Features > XPath 1.0 Compatibility Mode to be disabled
WCAG: Expere Engine enhanced to support embedded and Tagged .PDF's - April
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:
  • <Figure> tag behavior updated in Tag Tree (PBI 845789): users reported that <Figure> tags were appearing as direct children under <P> tags when part of a list (directly under a <Lbl> tag) in some Tagged PDF documents. Per WCAG requirements, <Figure> tags should appear as children of <Lbl> when part of a list. This behavior has been modified so that <Figure> tags appear as direct children of a <Lbl> tag when part of a list in a Tagged PDF document.
  • Support added for hyperlink and email address alternative text (PBI 847317): users reported that some hyperlinks in dynamic Tagged PDF documents did not contain corresponding alternate text, which is a WCAG requirement. Alternate text is available within the Object Properties > Tag > Alternate Description for Links dialog. for the appropriate tag and is read by the screen reader.

    As a result, Expere has been updated so that authored dynamic documents contains corresponding alternate text when generated as a Tagged PDF document. For more information, see ADA Implementation Guide > Working with Alternate Text for Links and Email Addresses.

  • Assembled PDF Form field tags (PBI 855362): it was reported that form fields were not being tagged consistently in Tagged EmbeddedPDF documents. Some fields were tagged with the Form Name passed in the parent <P> tag and text passed in the transaction XPath value, while other tag names incorrectly contained the Field Name instead of the transaction XPath value. This behavior has been modified so that tag names now correctly display the transaction XPath value for embedded PDF documents.
    Note: This enhancement has been implemented for individual Tagged EmbeddedPDF documents only; further development is required for merged Tagged EmbeddedPDF documents.
Expere: Package ID now passed back in SOAP and REST callbacks
Summary: Hosted Expere has been enhanced to now include the Package ID "DocSetPackageIDRef" in REST and SOAP callbacks.
Expere: DocumentList errors when using a Generate call with inline packages
  • Type: Enhancement
  • Reference: PBI 864317
Summary: users reported errors when attempting to generate documents with an inline package (Expere EZ Config Packages and Packets) that contained two documents with the <DocumentList/> descriptor. This issue was confined only to Generate API calls.

This behavior has been enhanced so that documents generate successfully using a Generate API call with an inline package containing two documents with the <DocumentList/> descriptor.

Note: For more information, refer to Document List and Partial Document List functionality.
Expere: Internal Code Optimization
  • Type: Enhancement
  • Reference: PBI 868765
Summary: as part of a regular cadence to review and upgrade any items used with our Expere application, the Engine has undergone code optimization in the document generation micro services when generating documents for use with SmartSign Plus®.
Expere: Internal Code Optimization when using Radio Buttons
  • Type: Enhancement
  • Reference: PBI 838692
Summary: as part of a regular cadence to review and upgrade any items used with our Expere application, the Engine has undergone a code optimization so that radio buttons no longer return Unique ID's in the response.
DocumentService: unused API calls removed
Summary: we have removed the following API calls from the DocumentService API:
  • /api/v1/Document/account/{accountId}/deliver
  • /api/v1/Document/account/{accountId}/WKES/register
  • /api/v1/Document/account/{accountId}/transaction/{transactionIdentifier}/images/{WKESTrackingId}
  • /api/v1/Document/account/{accountId}/deliver/{transactionId}
  • /api/v1/Document/account/{accountId}/WKES/packages
EZTransform with Document Service: internal implementation change
  • Type: Enhancement
  • Reference: PBI 825109
Summary: Document Service is now configured to utilize a new internal EZTransform API. No user action is required.
Expere / eOriginal: schema 25.0 updated for use with SmartSign Plus® and SmartSign Web
  • Type: Enhancement
  • Reference: PBI 863452
Summary: The eOriginal Schema has been updated from 24.4 to 25.0 for use with SmartSign Plus® and SmartSign Web.
Note: No user action is required.
SMARTDoc user documentation enhancements
Summary: the Raw7 REQ format in the SMART Doc validation > Non-currency number table has been updated to include an updated SMART Doc Mask entry; additionally, Raw has been removed from this same table as it will not return values in a SMART Doc > ARC data.
DocViewer: General Updates
  • Type: Enhancement
  • Reference: PBI 867207
Summary: general updates this release are limited to reviewing all dependent components and making any necessary updates.

March

Expere: ability to return document instance information
Summary: as part of our feature to integrate additional properties into a document instance, Expere now returns a new InstanceProperty element and Name and Value child elements in the Expere response when authoring Dynamic or EmbeddedPDF REQ document. For example, these elements can be authored to return non-signing entity information in the response.
Note:
  • There is a WSDL and simultaneous code change required for this feature.
  • Static documents are out of scope for this feature.
Expere: XPath 1.0 Compatibility Mode update
Summary: in preparation of our feature to disable XPath 1.0 Compatibility Mode, Expere log files have been updated to a WARN status when transactions fall into XPath1.0 Compatibility Mode but do not fail. Additional details, such as the XPath in question, are now displayed in the exception.
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:
  • Participation information returned in response (PBI 863465, 863472) SmartSign Plus® participant information is now returned in the Expere response file. Within the response, the eOriginal element now contains a new Participants child element.
    Note: There is a WSDL and simultaneous code change required for this feature.
  • One-Time PIN functionality updated (PBI 859935): Expere has been updated so that smsOtp (/Txn/EOriginalSSPlusParticipants/EOriginalSSPlusParticipant/IdentityVerificationSMSOneTimePINInd) is not dependent on Custom Pin (/Txn/EOriginalSSPlusParticipants/EOriginalSSPlusParticipant/IdentityVerificationCustomPINInd).
WCAG: Expere Engine enhanced to support embedded and Tagged .PDF's - March
  • Type: Enhancement
  • Reference: PBI 855580, 813755
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:
  • Bookmark behavior enhanced (PBI 855580): users reported that bookmarks starting with the word "Initial" or "Signature" did not appear in the Bookmarks section of a tagged EmbeddedPDF document. In the example below, the bookmark for "Step 1 - Title Transaction Type" highlights "Initial Title" in the Bookmarks section of the tagged PDF document, however "Initial Title" does not appear in the Bookmarks section.

    This behavior has been enhanced so that bookmarks starting with the word "Initial" or "Signature" appear in the Bookmarks section for Tagged and standard EmbeddedPDF documents and Tagged Dynamic documents.

  • Tagged PDF document behavior enhanced when using eSignatures with XY Coordinates (PBI 813755): Tagged PDF documents have been enhanced to remove empty <P> tags in the Signature area when ESignatureAndFieldSupport ancillary option is not specified
Expere: FooterNotice’s MiddlePages attribute update
  • Type: Enhancement
  • Reference: PBI 860750
Summary: users reported that initial fields in the FooterNotice were not fillable for all middle pages when MiddlePages=yes was specified in the .REQ file. This behavior has been enhanced so that when MiddlePages=yes is specified in the FooterNotice, all middle pages will have fillable initial fields in the FooterNotice for standard and Tagged PDF documents.
Expere: installation enhanced to use JRE
  • Type: Enhancement
  • Reference: PBI 864409
Summary: the Expere Installation with WildFly has been updated to use a Java Runtime Environment (JRE) instead of a Java Developer Kit (JDK) in order to reduce the installation size.
DocumentService: generate-results call includes optional parameter for documentId
Summary: users can now filter a generate-results call with a new optional documentId parameter.
Expere Document Services Web Services Guide: Document Service REST API > AncillaryOutputTypeEnum updated with new merging options
Summary: the list of avaiable enumerated values within the AncillaryOutputTypeEnum help topic has been updated to include the following new merging options:
  • PdfMergeDiscreteParty
  • MergedCopyPDFDiscreteParty
  • PdfMergeWithDocInstancesDiscreteParty
SMARTDoc user documentation enhancements
Summary: the SMART Doc validation tables in the Using SMART Doc functionality / dynamic Expere eNotes online help topic have been updated to include a comprehensive list of defined Output Format selections and their corresponding SMART Doc Mask options.
Expere: Security issue and Monthly component upgrades
  • Type: Maintenance
  • Reference: PBI 853704, 858126, 864522
Summary: As part of a regular cadence to review and upgrade any items used with the Expere Engine for security issue and monthly component upgrades, we have upgraded the following:
  • Security Issue Upgrades:
    • WildFly 35.0.1
    • FOP 2.10
  • Upgrades:
    • Amazon Corretto 21.0.6.7.1
Note: No user action is required.

February

Note: Please read the following deployment related information:
  • Scheduled maintenance will occur on Thursday, February 27 from 10:00 pm-12:00 am Eastern time. This maintenance window will consist of VDC Migration and NAT Gateway testing.
    • VDC Migration refers to the process of moving virtual machines (VMs) and other resources from one Virtual Data Center (VDC) to another. This can involve several steps, including:
      • Planning and Design: Assessing the current infrastructure and planning the migration strategy.
      • Preparation: Setting up the destination VDC, including network configurations and storage.
      • Migration Execution: Using tools like VMware Cloud Director Availability to move VMs and data. This can include one-click migration features for simplicity.
      • Validation and Testing: Ensuring that all resources are functioning correctly in the new VDC.
      • Cutover: Finalizing the migration and decommissioning the old VDC if necessary2.
    • A NAT Gateway (Network Address Translation Gateway) allows instances in a private subnet to connect to the internet or other AWS services, but prevents the internet from initiating a connection with those instances. Testing a NAT Gateway typically involves:
      • Configuration Check: Ensuring that the NAT Gateway is correctly configured with at least one public IP address and attached to the appropriate subnets3.
      • Connectivity Tests: Validating end-to-end connectivity by conducting TCP connection tests and UDP-specific application layer tests3.
      • Traffic Analysis: Using tools like VNet flow logs to analyze outbound traffic flows from the NAT Gateway3.
      • Troubleshooting: Addressing common issues such as subnet IP address availability, internet gateway attachment, and Elastic IP address association
  • A supplemental February Customer Test (CT) release was deployed on February 13th to address a transaction failure issue that users reported. See the changelog for PBI 864954 below for more information.
Expere: transaction issues addressed
  • Type: Defect Correction
  • Reference: PBI 864954
Issue: users reported that some transactions failed to generate documents after our February CT deployment that occurred on February 11. Internal research determined that the issue was caused by some EmbeddedPDF documents that did not contain fillable fields.
Solution: changes were made to resolve this issue and ensure that transactions containing EmbeddedPDF documents successfully generated documents.
Note: The items below were deployed as part of the original February CT release.
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:
  • Single Line source field using Overflow functionality enhanced (PBI 857684): Expere has been enhanced so that line leading is not applied to single line fields, resulting in the text and forwarding message fitting in the field horizontally.
  • Source and target field line leading adjusted (PBI 857682): Expere has been updated so that the source field and target field line leading is configured to a value compatible with the Helvetica font. The use of any other font with overflow functionality will result in an Expere error and failure to generate documents.
  • Field display order on Overflow page enhanced (PBI 857683): Expere has been updated so that fields overflow in the order they appear in the document: top to bottom and left to right.
Expere: Expanding merging PDF options
Summary: we have completed the work to support merged PDF documents by Discrete Parties. Expere now supports generating multiple merged PDF documents based on the discrete party or parties specified for each document. The following options can now be used as part of the request or by specifying in Expere EZ Config Packages and Packets:
  • EDS EDocService WSDL for SOAP users can now use the following new ancillary options:
    • PdfMergeDiscreteParty
    • MergedCopyPDFDiscreteParty
    • PdfMergeWithDocInstancesDiscreteParty
  • EDS DocumentService REST APIs can now use the following new ancillary options:
    • PdfMergeDiscreteParty
    • MergedCopyPDFDiscreteParty
    • PdfMergeWithDocInstancesDiscreteParty
Expere: XPath 1.0 Compatibility Mode update
Summary: in preparation of our feature to disable XPath 1.0 Compatibility Mode, we have made the following updates:
  • New OD Variable (PBI 843921): we have added the ability to set the XPath Compatibility Mode using the OD variable of ALLOW_XPATH_1. This OD variable will be set to true. This variable will update the BSI.properties variable com.bankerssystems.expere.xPath_1_0_Compatibility value.
    Note: In an upcoming release, the OD Variable and the BSI.Properties' com.bankerssystems.expere.xPath_1_0_Compatibility default value will be changed to "false", which has the potential of causing transactions to fail. See the Feature page for more details.
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:
  • SmartSign Plus Third Party eDelivery Service functionality enhanced (PBI 836326): closing documents can now be sent to one or many Settlement Agent/Closing Agent via eDelivery; the following XPaths have been added:
    • /Txn/EOriginalUseSSPlusInd /Txn/EOriginalSSPlusThirdPartyEDeliveryInd
    • /Txn/EOriginalSSPlusThirdPartyEDeliveries
    • /Txn/EOriginalSSPlusThirdPartyEDeliveries/EOriginalSSPlusThirdPartyEDelivery
    • /Txn/EOriginalSSPlusThirdPartyEDeliveries/EOriginalSSPlusThirdPartyEDelivery/EmailAddress
    • /Txn/EOriginalSSPlusThirdPartyEDeliveries/EOriginalSSPlusThirdPartyEDelivery/FirstName
    • /Txn/EOriginalSSPlusThirdPartyEDeliveries/EOriginalSSPlusThirdPartyEDelivery/LastName
    • /Txn/EOriginalSSPlusThirdPartyEDeliveries/EOriginalSSPlusThirdPartyEDelivery/PhoneNumber
    • /Txn/EOriginalSSPlusThirdPartyEDeliveries/EOriginalSSPlusThirdPartyEDelivery/IdentityVerificationCustomPINInd
    • /Txn/EOriginalSSPlusThirdPartyEDeliveries/EOriginalSSPlusThirdPartyEDelivery/IdentityVerificationCustomPINValue
    • /Txn/EOriginalSSPlusThirdPartyEDeliveries/EOriginalSSPlusThirdPartyEDelivery/IdentityVerificationCustomPINHintInd
    • /Txn/EOriginalSSPlusThirdPartyEDeliveries/EOriginalSSPlusThirdPartyEDelivery/IdentityVerificationCustomPINHintDesc
    • /Txn/EOriginalSSPlusThirdPartyEDeliveries/EOriginalSSPlusThirdPartyEDelivery/IdentityVerificationCustomPINSMSDeliveryInd
    • /Txn/EOriginalSSPlusThirdPartyEDeliveries/EOriginalSSPlusThirdPartyEDelivery/IdentityVerificationSMSOneTimePINInd
    As a result of this enhancement, the existing "eDelivery" Xpaths have been deprecated:
    • /Txn/EOriginalSSPlusSingleElectronicPackageInd
    • /Txn/EOriginalSSPlusSingleElectronicPackageEmailAddress
    • /Txn/EOriginalSSPlusSingleElectronicPackageFirstName
    • /Txn/EOriginalSSPlusSingleElectronicPackageLastName
WCAG: Expere Engine enhanced to support embedded and Tagged .PDF's - February
  • Type: Enhancement
  • Reference: PBI 851484, 852050
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:
  • List tagging behavior updated (PBI 851484): it was reported that lists that did not contain a "marker" (in other words: a numerical value or a bullet) displayed a tag for a nonexistent marker in the Adobe Acrobat tag tree. This behavior has been updated so that these nonexistent markers no longer appear as tags in the Adobe Acrobat tag tree.
  • Alternate Text for Spanish Checkboxes (PBI 852050): it was reported that the alternate text for checkboxes in Spanish on documents generated from EmbeddedPDF REQ were in English. This behavior has been updated so that the alternate text for checkboxes indicated as Spanish (i.e. entire document is in Spanish or a section is in Spanish) reads in Spanish
Expere: Logging enhanced when more than one eNote is autoselected
  • Type: Enhancement
  • Reference: PBI 852175
Summary: we have enhanced logging when more than one eNote gets autoselected.
Note: Transactions attempting to generate multiple eNotes will still fail.
Expere: Enhanced ancillary output functionality
  • Type: Enhancement
  • Reference: PBI 859754
Summary: It was identified that when inline packages were passed in without any ancillary options, the transaction would fail. We have enhanced Expere to handle an inline package (Package from EZ Config Packages and Packets) without an ancillary option.
Expere: docSetPackageIDRef behavior enhanced with response
  • Type: Enhancement
  • Reference: PBI 859720. 851157
Summary: we informed you in January per PBI's 849726, 849971 that the docSetPackageIDRef value had displayed the wrong value in the Expere response; as a result, Expere had been updated so that the response specified the docSetPackageIDRef value based on specific criteria. Additional component work was identified so docSetPackageIDRef is returned in the response.

Additionally, docSetPackageIDRef now displays the .PKG name used as primary package when configured in EZ Config Packages and Packets.
Expere: SmartSign Plus ® and SmartSign Web post process addressed
  • Type: Defect
  • Reference: PBI 860844
Summary: users reported that the MergedCopyPDF ancillary option was not being honored when generating an Expere Dynamic eNote. As a result, MergedCopyPDF is now honored when generating an Expere Dynamic eNote.

January

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:
  • Tagged PDF functionality supported (PBI 848167): Expere is updated so that EmbeddedPDF documents with overflow Pages can be generated as Tagged PDF documents.
  • Truncate behavior supported (PBI 850405): Expere has been updated so that when Truncate is specified in the Behavior dropdown, any text that exceeds the source field is truncated.
  • "Return" characters behavior enhanced in source and destination fields (PBI 855381): during internal testing, it was determined that the source and destination fields did not handle "return" characters (for example: line breaks) properly; as a result, some characters and words did not appear in the fields.

    This behavior has been enhanced: the source and destination fields have been updated to support "return" characters and thus display all characters and words.
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:
  • Vault & Financial Asset information in Expere EZ Config Packages and Packets now passed to SmartSign Plus® (PBI 850094): Vault and Financial Asset information have been added to Expere EZ Config Packages and Packets; these values are used to control if non-enote documents are vaulted. For more information, refer to SmartSign+ Feature Guide: Non-eNote workflow and Expere EZ Config Packages and Packets User Guide > Working with Documents in Packages.
  • OAuth support added when using SmartSign Plus version two (2) authentication API (PBI 812873): the Document Generation Services Tool Suite > SETUP page has been updated to support the SmartSign Plus® version two (2) authentication API through the creation of the following fields for data capture:
    • Client ID
    • Client Secret
    Note the following:
    • The previously entered value for Login ID is a legacy value and is no longer valid; refer to your SmartSign + configuration for the correct API LOGIN ID.
    • The Lender Name field has been updated to Closing Center Lender Name.

    Refer to the Document Generation Services Tool Suite User Guide > SETUP page for more information.
WCAG: Expere Engine enhanced to support embedded and Tagged .PDF's - January
  • Type: Enhancement
  • Reference: PBI 845069, 846766, 849713
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:
  • <Form> tags replaced with <P> tags in certain situations (PBI 845069): a user reported that <Form> tags were incorrectly present in the Adobe Acrobat tag tree instead of a more appropriate <P> tag. This behavior has been enhanced to use <P> tags rather than the <Form> tag when populating the document with conditional data.
  • <Form> tags replaced with <Figure> tags in certain situations (PBI 846766): a user reported that <Form> tags were incorrectly present in the Adobe Acrobat tag tree instead of a more appropriate <Figure> tag when using checkboxes and radio buttons. This behavior has been enhanced to use <Figure> tags rather than the <Form> tag for checkboxes and radio buttons when these options are not fillable fields.
  • Table behavior enhanced when empty <TH> cells are present (PBI 849713): a user reported that empty heading cells in a table were being tagged as a <TH> in the Adobe Acrobat tag tree. This behavior has been enhanced to now tag empty table heading cells as <TD> intead of a <TH> tag.
Expere: Internal Code Optimization when using Expere EZ Config Packages and Packets logos
  • Type: Enhancement
  • Reference: PBI 850491
Summary: in November we optimized our internal Expere code to better support logos used with Expere EZ Config Packages and Packets (PBI 850662). As part of a that update, additional updates were recommended. The Engine has undergone additional code optimization to better support logos used with Expere EZ Config Packages and Packets.
Expere: SmartDoc/eNote ARC validation updated
  • Type: Enhancement
  • Reference: PBI 851965
Summary: when the mask $#,###.## was being passed, the DataLinkDescription value was not appending the cents to the dollar amount. Expere has been updated so that the correct number of zeroes are now appended in order to match the format of the mask; for example: "1000" becomes "1000.00".
Expere: DocSetPackageIDRef behavior enhanced
  • Type: Enhancement
  • Reference: PBI 849726, 849971
Summary: users reported that that the DocSetPackageIDRef value displayed the wrong value in the Expere response. As a result, Expere has been updated so that the response specifies the "docSetPackageIDRef" value as follows:
  • If an PKGPKT is specified in the content URI, the value of the DocSetPackageIDRef is set to the package name specified in Expere EZ Config Package and Packets.

Additionally, "PackageName" is now returned as an attribute on the <InlinePackage> element in the inline package response.

Note:
  • No changes when the content URI specifies the PKG.
  • Additional development is required before this enhancement is completely functional.
Expere: Logging enhanced for packet-level ancillary output options
  • Type: Enhancement
  • Reference: PBI 851089, 848145
Summary: we have enhanced logging regarding packet-level ancillary output options. Additional details, including the stack trace, are provided about whether or not packet-level ancillary output options are being used.
EZ Transform: internal component upgrade to resolve security issue
  • Type: Maintenance
  • Reference: PBI 852487
Summary: as part of a regular cadence to review components used by Expere Engine for security issues, we have upgraded the following components:
  • Apache Tomcat 10.1.34
  • Apache Struts 6.4.0
Note: No user action is required.