Jump to main content

# 2023 Release One (1) Expere Engine and Tools Changelog

Expere Engine Release: 2023 Release One (1)External release date is March 2023. Expere Engine build number is: 23.1.0.4919.

Expere: Document List / Partial Document List functionality
Type: Feature Reference: PBI 744444 Documentation Impacts: Features > Document List functionality; Implementation Strategies > Document List / Partial Document List functionality; Expere Document Services Web Services Guide: DocDescriptor
Summary: We have enhanced the Expere Engine to support the selection of either a full or partial document list. In conjunction with a Requirements Editor update allowing users to select either a Document List (full document list) or Partial Document List, the Engine has been updated to include a new optional `<PartialDocumentList/>` element.
    <DocDescriptor>
       <PartialDocumentList>true</PartialDocumentList>
    </DocDescriptor>
Note: For a document to be included in a Partial Document List, some additional data needs to be captured when authoring the REQ. Please see the Implementation Strategies > Document List / Partial Document List functionality for more information. Note also that this is supported in the Expere TXN only.

Expere: Document List functionality enhancement
Type: Feature Reference: PBI 709825 Documentation Impacts: Feature page; Expere Developer Guide: Document List / Partial Document List functionality
Summary: A user requested an Expere enhancement to provide the Closing Instructions when no other documents would be created; as a result, we have enhanced the Document List functionality to allow for the creation of an empty document list. Note: Expere Content will be updated in the future to implement this functionality.

WCAG 2.0: Expere Engine enhanced to support Tagged .PDF's
Type: Feature Reference: PBI 745396, 750118, 747377, 750142, 708011, 695045 Documentation Impact: See below for pertinent links
Summary: As a part of our continued effort to create WCAG 2.0 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 2.0-related changes: LinkText behavior enhanced with multiple references in dynamic document (PBI 745396): users reported that when using the Link – element and the referenced appeared on a different page, the tagged PDF did not include the reference correctly in the tag tree. As a result, Expere has been enhanced to tag references on different pages correctly. Dynamic document accessibility checker error (PBI 750118): when generating a dynamic document as a tagged PDF with a barcode, the resulting document failed the Adobe Acrobat accessibility checker. This behavior has been resolved so that a dynamic document can be generated as a tagged PDF with a barcode. Assembly error addressed (PBI 747377): users reported an assembly error when attempting to generate a Tagged PDF version of the Deed of Trust document (FNMAFHLMCDeedOfTrust-M2); as a result, Expere has been enhanced so that the Deed of Trust document can be generated as a Tagged PDF. With this upgrade all Tagged PDFs and API requests using the FOP26 parameter will be generated using FOP 2.8. Barcode cover page tagging behavior enhanced (PBI 750142): users reported that when generating an embedded PDF or dynamic REQ with a barcode cover page (`<UsecoverPage="true">`), the following occurred in Adobe Acrobat: the resulting tagged PDF document failed the accessibility checker The barcode cover page text did not appear in the resutling tag tree This behavior has been modified so that the generated PDF will pass the Adobe Acrobat accessibility checker and subsequent barcode cover page text will appear in the tag tree when using a barcode cover page with an embedded PDF or dynamic REQ. Incorrect tagging with Electronic Remote Online Notary (ERON) when generating dynamic documents (PBI 708011): users reported that tags for the electronic notary section within certain tagged PDF documents appeared out of order within the Adobe Acrobat tag tree. Tags for the electronic notary are now tagged in the correct order in the Adobe Acrobat tag tree. Fillable signature / date fields and checkboxes behavior enhanced (PBI 695045): users reported the following issues when generating a tagged PDF of the HUD92541BuildersCertificationAndAgreeToExecuteBuildersWarranty-M2.req dynamic document: The tag order for fillable checkboxes was incorrect The tags for some fillable fields, namely `SignatureField` and `SignatureDate` fields, were missing from the tag tree These issues have been resolved; fillable checkboxes are now tagged in the correct order, and `SignatureField` and `SignatureDate` fields are present in the tag tree.

WCAG 2.0: Expere Engine enhanced to support Embedded PDF's
Type: Feature Reference: PBI 728082, 750351, 746699, 750531, 756865, 750644, 755798, 755714, 739329, 748774, 760507, 760760 Documentation Impact: Expere Engine and Tools Changelog > Features > WCAG 2.0;
Summary: As part of our continued effort to create WCAG 2.0 compatible documents, we have updated the Expere Engine to support a new document format that we refer to as Embedded PDF. The Embedded PDF will allow Expere to support Tagged PDFs of what was traditionally Static REQs. We will continue making enhancements to the Expere Engine for Embedded PDF REQ files, so check back for items being identified and corrected. As part of our continued work to support Tagged PDFs for Embedded PDF REQ files, we will have implemented the below enhancements: Tooltip behavior enhanced (PBI 728082): users reported that tool tips appeared and were read for all fields, consisting of fillable and non-fillable fields on embedded PDF documents. The expected behavior is that fillable fields are only generated for fillable fields. Expere has been enhanced so that tool tips now only appear and are read with fillable fields on embedded PDF documents. Barcode field generates on executed PDF containing FillableFields (PBI 750351): users reported that an embedded PDF document contained a fillable field where the barcode was present in the tagline. The expected behavior is that no fillable field should be present in the tagline. As a result, Expere has been enhanced so that no fillable field appears in the tagline. Barcode39 displaying text below barcode as ancillary output in embedded PDF (PBI 746699): users reported that text appeared below the barocde when using a Barcode39 ancillary output with an embedded PDF. The expected behavior is that any text passed in the `<pattern/>` element within the Barcode39 ancillary output should appear above the barcode. Expere has been enhanced to place any text above the barcode. For more information on using barcodes as ancillary outputs, see the Expere Developer Guide > Barcodes. ESignature field naming convention updated (PBI 750531): the Expere eSignature naming convention has been updated to reflect the following for Signature fields and Signature Date fields when generating embedded PDF, static, and dynamic REQ's: Signature fields now use "underscores" ("_") instead of "dots" or "periods" ("."); for example: `SIG_Borrower_1_1_true_1_eSig` or `PurchaserSignatureArea_eSig` Signature Date fields now use the above mentioned Signature field naming convention and "_eSigDate;" for example: `SIG_Borrower_1_1_true_1_eSig_eSigDate` or `PurchaserSignatureArea_eSig_eSigDate` Note: This naming convention applies to static, dynamic, and embedded PDF REQ's. For more information, refer to Using eSignature and Acroform fields > Signature Field and SignatureDateField naming for embedded PDF REQ files; this help topic will continue to be updated as enhancements are implemented. Embedded PDF - "IsTagged" behavior enhanced when selecting standard PDF (PBI 756865): users have reported that when creating a standard PDF document from an embedded PDF REQ file, a "Tags" value is appearing in the tag tree in Adobe Acrobat. The expected behavior is that "No Tags Available" should appear. We have enhanced this behavior so that "No Tags Available" appears in the Adobe Acrobat tag tree when generating a standard PDF from an embedded PDF REQ file. Embedded PDF tagline tagging behavior modified (PBI 750644): the following changes were implemented: On certain documents (for example: "Request for Verification of Employment FNMA 1005"), the fields below were incorrectly appearing in the Adobe Acrobat tag tree when generating a tagged PDF using an embedded PDF REQ document; note also the naming convention and examples appeared as the following: `Form_UserDefined_Left_page1` ("_page2" and so on) `Form_UserDefined_Center_page1` `Form_UserDefined_Right_page1` `Form_CustomBrandTag1` ("`_CustomerBrandTag2`" and so on) `Form_WarrantyControl1` ("`_WarrantyControl2`" and so on) Note: See "Form.WarrantyControl has been changed to Form_WarrantyControl" bullet below. `Form_Barcode` `Form.WarrantyControl` has been changed to `Form_WarrantyControl`. See ADA Implementation Guide > Working with Taglines > Embedded PDF tagline tagging - naming convention for more information. Embedded PDFs: cover page being tagged in Standard PDF (PBI 755798): users reported that when generating a standard PDF using an embedded PDF REQ document and an ancillary barcode with cover page, the cover page text was inadvertently tagged in the Adobe Acrobat tag tree. This behavior has been enhanced so that when generating a standard PDF using an embedded PDF REQ document and ancillary barcode with cover page, the cover page text does not appear in the Adobe Acrobat tag tree. FirstPageOnly behavior modified when using ancillary barcodes with embedded PDF REQ documents (PBI 755714): users reported that ancillary barcodes appeared on all pages of an embedded PDF when selecting `<FirstPageOnly>"true"</FirstPageOnly>` as a child element of an ancillary barcode option. Using this `<FirstPageOnly>"true"</FirstPageOnly>` element should have resulted in barcodes only appearing on the first page of the document. This behavior has been addressed: when selecting `<FirstPageOnly>"true"</FirstPageOnly>` with an ancillary barcode option using an embedded PDF REQ document, only the resulting first page of the embedded PDF displays a barcode. Embedded PDF - radio button support enhanced (PBI 739329): Expere has been enhanced to support ESignature and Wolters Kluwer E-Sign radio buttons in generated embedded PDF documents; users will note the proper naming convention now appears in the tag tree for each radio button. InstanceDisplayName behavior with embedded PDF documents enhanced (PBI 748774): users reported the following when generating an embedded PDF document as a standard PDF: the Document Title value (found in Adobe Acrobat > Document Properties > Initial View > Show dropdown) was set to use Title of the document and appeared in the upper left corner of the document; the File Name value should have appeared instead (found in the same Show dropdown as stated above). Generating a standard PDF from an embedded PDF resulted in Tagged PDF: Yes appearing in the Document Properties > Advanced section. These behaviors have been addressed: when an embedded PDF is generated as a standard PDF, the File Name value is used as the Title of the document and appears in the upper left corner of the document. Tagged PDF: No now appears in the Document Properties > Advanced section when generating a standard PDF from an embedded PDF. Embedded PDF enhancement (PBI 760507): Embedded PDF functionality has been enhanced to ensure consistent generation of tagged PDF documents (i.e. merging of tagged PDF). Non-fillable WKES checkboxes supported with Embedded PDF's (PBI 760760): Users reported that non-fillable WKES checkboxes were not tagged correctly in Embbeded PDF documents. The expected behavior is the naming convention in the tag tree should match that of standard non-fillable fields and checkboxes. For example: in the tag tree, the naming convention should consist of the following regardless of whether a standard or WKES non-fillable field or checkbox is used: Form <name>_OBJR (for example: Owner_Resident_Yes_OBJR) This behavior has been enhanced so that the checkbox name should be the same between standard non-fillable and WKES fields and checkboxes when generating Embedded PDF documents. Note: Although we continue to work on enhancements regarding embedded PDF REQ files, base content containing embedded PDF REQ files will be released in the future.

Engine: eSignature field naming convention updated for static and dynamic documents
Type: Enhancement Reference: PBI 751692, 751697 Documentation Impacts: Using eSignature and Acroform fields > Signature Field and SignatureDateField naming for embedded PDF and static REQ files
Summary: we had previously updated the Expere eSignature naming convention to reflect the items below for Signature fields and Signature Date fields when generating embedded PDF REQ's. We have now updated static and dynamic document functionality to match the embedded PDF naming convention functionality: Signature fields now use "underscores" ("_") instead of "dots" or "periods" ("."); for example: `SIG_Borrower_1_1_true_1_eSig` or `PurchaserSignatureArea_eSig` Signature Date fields now use the above mentioned Signature field naming convention and "_eSigDate;" for example: `SIG_Borrower_1_1_true_1_eSig_eSigDate` or `PurchaserSignatureArea_eSig_eSigDate` Note: With static and dynamic documents, Expere will automatically change periods / dots (".") to underscores ("_") for Signature and Signature Date fields; therefore, no user action is required for the Expere content. However, it is recommended that integrations are reviewed if they are using or expecting specific field names. Non-Signature and Signature Data fields using periods / dots will be accounted for in a future Engine release; for example: checkboxes and text fields. This naming convention applies to embedded PDF, static, and dynamic REQ's.

Engine: upgrade to .NET Framework 4.8
Type: Enhancement Reference: PBI 738756 Documentation Impacts: Expere System Requirements: Windows Environment Software Requirements
Summary: The Expere Engine has been upgraded from .NET Framework verion 3.5 to now use .NET Framework 4.8.

Expere Engine: updated to use WildFly 26.1.3
Type: Enhancement Reference: PBI 761958 Documentation Impacts: No documentation impact
Summary: The Expere Engine has been updated to use Wildfly version 26.1.3. No user action is required.

Engine: new FOP 2.6 flag added to `bsi.properties` file
Type: Enhancement Reference: PBI 730313 Documentation Impacts: Expere Implementation Guide: Using the `bsi.properties` file
Summary: Users can now specifiy whether to use the FOP 2.6 rendering option in the `bsi.properties` file through the use of a new `com.bankerssystems.expere.render.FOP26` property. Note: There is no user action required. Here is the complete entry in the `bsi.properties` file:
    ##Indicates whether to use FOP 2.6 for all dynamic docs, regardless of what is specified in the API
    ##Valid values are:
    ## true - only use FOP 2.6
    ## false - use what is specified in the API
    ##Default is false
    com.bankerssystems.expere.render.FOP26=false

Engine: Enhanced support of multiple MiddlePages when signatures are included in footers
Type: Enhancement Reference: PBI 751216
Summary: when the page count exceeded three pages in a transaction where the FannieMae1003FreddieMac65URLAContinuationPage ("Continuation Page") was included, the document would throw an exception when no fillable fields were present for that document. This functionality has been enhanced to accommodate this additional scenario.

Engine: Mandatory attribute behavior enhanced with fillable checkboxes
Type: Enhancement Reference: PBI 750941
Summary: users reported an Expere response file contained a Mandatory attribute set to No for a fillable checkbox (`FillableCheckbox`), despite it being set to Yes in the .REQ file, in this case the AttorneyorTitleInsuranceCompanyPreferenceNotice.req. This behavior has been addressed: when the Mandatory attribute is set to Yes in the .REQ file for a fillable checkbox, the corresponding response value reflects this value.

Engine: SMARTDoc validator error with 12.345% value displayed
Type: Defect Reference: PBI 747390 Documentation Impacts: See the Features page for more information and links below if applicable.
Summary: Results of the eOValidator indicated that there was a mismatch between the mask value and the amount displayed on the SMARTDoc for the 12.345% format value when a four digit decimal (i.e. 0.1212) is provided: only three decimal places appeared. As a result, Expere has been enhanced so that four decimals now appear for the mask value on the SMARTDoc and PDF. For example: .1212%; the `MaskDescription` value in the XML file requires four decimal places (e.g. "####").

DocViewer: incorrect formatting behavior enhanced
Type: Enhancement Reference: PBI 662167
Summary: When a value was entered in DocViewer that resulted in an invalid character error, the file that tracked the XPath changes saved the invalid value rather than the NULL or the previous value. This behavior has been enhanced so that when an invalid character error appears, DocViewer does not track the invalid characters but rather the the original value in the on the EndSession page.

DocViewer: messaging behavior enhanced
Type: Enhancement Reference: PBI 756574
Summary: Users reported that when attempting to close a document within DocViewer, an "Are you sure you want to leave this page?" message appeared, implying that the user made a change in DocViewer even if no change had been made. As a result, we have enhanced DocViewer so that no message will appear if changes have not been made.

DocViewer: latency issues addressed
Type: Enhancement Reference: PBI 758965
Summary: Users reported that the Authority document experienced considerable delay when loading the document and selecting fields in DocViewer. Internal analysis revealed that an unnecessary overlay dictionary was stored in the session when the session state was stored in SQL. Whenever a change was made, DocViewer retrieved the overlay dictionary, storing it in the session cache. This issue has been resolved: latency issues have been resolved in DocViewer.

DocViewer: Condition Behavior addressed
Type: Enhancement Reference: PBI 743075
Summary: DocViewer has been enhanced to now display the prompt from the Xpath in a condition (COND.<x> authored in the .REQ file) if a note was not authored in the .REQ file. This prompt appears to right of the "+" / "-" sign in DocViewer.

DocViewer: Representative Entity behavior enhanced with overlay
Type: Enhancement Reference: PBI 751098
Summary: Users reported persistent issues existed with Representative Entity Xpaths not honoring suppression values defined at the first level when using an overlay. This behavior has been addressed: Representative Entity Xpaths are honored at all levels when using an overlay.

DocViewer: scrolling behavior updated
Type: Enhancement Reference: PBI 751112
Summary: Users reported that clicking on certain fields in the Data Entry drawer (left-hand pane) did not advance them to the corresponding location in the Document Display (body of the document in DocViewer). This behavior has been modified so that DocViewer now scrolls correctly to the correct location in the document

DocViewer: dash "-" removed with alpha percent masks
Type: Enhancement Reference: PBI 736797
Summary: DocViewer has been enhanced so that dashes ("-") are removed when working with alpha percent masks; for example "twelve and one-half" is now "twelve and one half." This behavior is consistent with other mask enhancements that have been made when working with SMART Docs.