2026 Release Two (2) Expere Engine and Tools Changelog

Expere Engine Release: 2026 Release Two (2)External release date is May 2026. Expere Engine build number is: 2026.2.0.1601.

Note: Users may notice that the 2026.2 Expere Engine release contains updates that reference the eOriginal SmartSign®+ solution. The Expere Engine is used to support both our Hosted and Self-Hosted ("On-Prem") customers, however, the updates made to support SmartSign®+ were implemented solely for our Hosted customers at this time but have Engine changes that Self-Hosted users will notice. See Changelog entries below for more information.
Expere: SmartSign Plus® integration
Summary: as part of our ongoing work to integrate SmartSign Plus® with Expere, the following functionality has been implemented in the 2026.2 release:
  • Authentication version updated (PBI 904355): The SmartSign Plus® authentication has been updated from version two (2) to version three (3).
  • Data scrubbing enhanced for participant and mailing information (PBI 918982): Scrubbing functionality was enhanced to remove participant container and mailing request data from transactions, ensuring related fields receive consistent scrubbed values so transactions can run successfully after scrubbing.
  • New XPaths created to support signing order (PBI 909030): integrators can now pass in custom participant information through the use of the following new XPaths:
    • /Txn/EOriginalSSPlusParticipants/EOriginalSSPlusParticipant/CustomFields
    • /Txn/EOriginalSSPlusParticipants/EOriginalSSPlusParticipant/CustomFields/CustomField
    • /Txn/EOriginalSSPlusParticipants/EOriginalSSPlusParticipant/CustomFields/CustomField/Name
    • /Txn/EOriginalSSPlusParticipants/EOriginalSSPlusParticipant/CustomFields/CustomField/Value
    See Expere - SmartSign Plus® Integration Guide - Expere Transaction XPaths for eOriginal > Participants Collection for more information.
EZTransform2: transformation behavior enhanced
  • Type: Enhancement
  • Reference: PBI 932832
Summary: With this enhancement, transformation failures no longer occur when encountering empty string conversions in stylesheets.
EZTransform2: Base64 data processing enhanced for whitespace handling
  • Type: Enhancement
  • Reference: PBI 934133
Summary: EZTransform2 has been enhanced to automatically remove any carriage returns or spaces from the base64-encoded stylesheets contained. EZTransform2 will now sanitize all base64 stylesheet strings which contain white space characters.
Expere / SMARTDoc: behavior enhanced to support additional Signer
Summary: The SmartDoc output now supports a user-requested scenario where the user signing in both an individual and trustee capacity is the same signing entity. This behavior is made possible by the addition of a second <SIGNER> element in the SmartDoc container / header, for example: 

<SMART_DOCUMENT xmlns="http://www.mismo.org" MISMOVersionIdentifier="1.02" PopulatingSystemDocumentIdentifier="FNMA_3200" _ID="ENOTE" xmlns:emrtg="http://www.mismo.org" xmlns:xlink="http://www.w3.org/1999/xlink">
  <HEADER _ID="Head01">
    <DOCUMENT_INFORMATION MustBeRecordedIndicator="False" NegotiableInstrumentIndicator="True" SMARTDocumentCategoryType="1" _FormNumberIdentifier="3200e" _StateType="Signed" _Type="Note"/>
    <SIGNATURE_MODEL>
   <SIGNER AreaIDREF="Borrower1SignatureArea" DataIDREF="Data01" SectionIDREF="BorrowerSignatures" SignatureIDREF="Borrower1SignatureImage" SignatureType="Image" TargetsIDREFS="View01" _RoleType="Borrower" _SignatureOrderNumber="1"/>
   <SIGNER AreaIDREF="Borrower1SignatureArea" DataIDREF="Data01" SectionIDREF="BorrowerSignatures" SignatureIDREF="Borrower1SignatureImage" SignatureType="Image" TargetsIDREFS="View01" _RoleType="Other" _RoleTypeOtherDescription="IntervivosTrustee" _SignatureOrderNumber="1"/>
    <SIGNER SignatureIDREF="TamperSealer01" SignatureType="DigitalSignature" TargetsIDREFS="Head01 Data01 View01 AuditTrail01 BorrowerSignatures TamperSealer01_DTS" _RoleType="TamperSealer"/></SIGNATURE_MODEL>
  </HEADER>
Expere: support added for Windows Server 2022 and 2025
Summary: the Expere Engine has been updated to support the use of Expere.NET with Windows Server 2022 or 2025.
Expere: support added for SQL Server 2019
Summary: the Expere Engine has been updated to support the SQL Server 2019 database.
EZTransform: system performance enhanced
  • Type: Enhancement
  • Reference: PBI 905469
Summary: EZTransform was updated to enhance system performance.
Implementation Notes: This enhancement is available in the supplemental February CT and Production release.
EZTransform2: JSON transaction data supported
  • Type: Enhancement
  • Reference: PBI 892186
Summary: We can now accept transaction data in JSON format in addition to XML format.
Requirements Editor users: ESignatureAndFieldSupport included in additional templates
Summary: For users of the Requirements Editor tool, the following additional Ancillary Output templates were created to include ESignatureAndFieldSupport functionality through the inclusion of the <ESignatureAndFieldSupport> container:
  • BarcodeWithESignatureAndFieldSupport.xml
  • BarcodeQRWithESignatureAndFieldSupport.xml
  • DuplexWithESignatureAndFieldSupport.xml
  • LogoWithESignatureAndFieldSupport.xml
  • WatermarkWithESignatureAndFieldSupport.xml
Expere Engine: Response Consistency for discretePartySupressPaperDelivery Transactions
  • Type: Enhancement
  • Reference: PBI 936160
Summary: .NET and Java response behavior was aligned for SuppressPaperDelivery and ForeignAddress fields in discretePartySupressPaperDelivery SOAP transactions. Both fields are now nullable in .NET, matching Java implementation which previously returned null while .NET returned false for SuppressPaperDelivery.
Impact: You may see different results when asserting against these elements in self-hosted environments. Testing in your environment is recommended before deploying to production.
Expere Engine: Monthly Component Updates
  • Type: Maintenance
  • Reference: PBI 832560, 917868, 891879, 927032, 927033, 929242, 916330, 931183, 931551, 932476, 931842
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:
    • EntityFrameworkCore
    • Microsoft JDBC Driver for SQL Server
    • .NET (dotnet) /AspNetCore
    • mganss/HtmlSanitizer
    • dotnet/AspNetCore
    • Microsoft.VisualStudio.Web.CodeGeneration.Design
  • Maintenance Upgrades:
    • FOP
    • Batik
    • Apache XML Graphics Commons
    • Amazon Corretto Java was updated to the latest available version.
    • WildFly was updated to the latest available version.
Note: No user action is required.
EZTransform: Monthly component updates
  • Type: Maintenance
  • Reference: PBI 917384
Summary: As part of a regular cadence to review and upgrade any items used by EZ Transform for security issues and component upgrades, we have made applicable component updates.
SmartSign Web: eNote redraw processing corrected
  • Type: Defect Correction
  • Reference: PBI 922850
Summary: We addressed an issue where a generic "object reference not set to an instance of an object" error was returned when processing a redraw request for an eNote with the same loan number.
What's Changed? SmartSign Web now correctly handles redraw requests for eNotes that share the same loan number as a previous transaction. Previously, when submitting a redraw request without destroying the original eNote in Expere, the system encountered an empty packet condition that caused a generic error.
Impact: You can now successfully process redraw requests for eNotes without encountering errors when using the same loan number, even if the original eNote was not destroyed through the standard Expere process.