2025 Release Two (2) Expere Engine and Tools Changelog

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

Note: Users may notice that the 2025.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.
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: 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: 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: Internal Code Optimization
  • Type: Enhancement
  • Reference: PBI 868765, 838692
Summary: as part of a regular cadence to review and upgrade any items used with our Expere application, the Engine has optimized code for the following:
  • Document generation micro services were enhanced when generating documents with SmartSign Plus®
  • Radio buttons no longer return Unique ID's in the response
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.
Expere (.NET): XPath 1.0 Compatibility flag updated to be nullable
  • Type: Defect Correction
  • Reference: PBI 874674
Issue: it was determined that XPath 1.0 Compatibility Mode did not function as expected when ExpereNetServiceInterface.dll was used with the 2025 Release One of the Expere Engine (.NET). Internal analysis revealed that the XPath_1_0_Compatibility parameter in SelectAndGenerate and Generate API calls defaulted to "false", resulting in XPath 1.0 Compatibility Mode always being set to "false" if the XPath_1_0_Compatibility parameter was not passed as "true".
Solution: in the 2025 Release Two of the Expere Engine, the XPath_1_0_Compatibility parameter in SelectAndGenerate and Generate API calls is now optional. Instead, the Expere Engine will default to the value set in BSI.Properties > com.bankerssystems.expere.xPath_1_0_Compatibility.
Note: If choosing to disable XPath 1.0 Compatibilty Mode, users can perform either of the following:
  • Pass the XPath_1_0_Compatibility parameter in SelectAndGenerate and Generate API calls as "false".
  • Set BSI.Properties > com.bankerssystems.expere.xPath_1_0_Compatibility to "false".
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.
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.
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.