2017.1 Expere Engine and Tools Changelog Entries

Expere Engine Release: 2017.1External release date is 10/3/2017. Expere Engine build number is: 2017.1.0.1425

New Features

Enhancements

Defect Corrections

Schema Changes

Expere Engine 2017.1 release schemas updated
  • Type: Defect
  • Reference: PBI 489137
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: With the 2017.1.0.4574 version of the Expere Engine some users were experiencing schema validation errors. It was determined that PacketType.xsd schema, shipped with the engine, contained invalid elements. As a result, we have updated all Expere Schemas for the 2017.1.0.4574 and have versioned them as 2017.1.1.0000.
Solution: As a result, we have updated all Expere Schemas for the 2017.1.0.4574 and have versioned them as 2017.1.1.0000.
Note: This change is only required for users whose tools/application complete schema validation.
Implementation Notes: This defect correction is available in the 2017.1 Expere Engine release. If you are interested in receiving the new schema files, please work your Wolters Kluwer Professional Services contact.
Duplex added as an ancillary output option
  • Type: Enhancement
  • Reference: PBI 446285
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: AncillaryOutputTypeEnum
Summary: A new <OutputType/> element for Duplex has been added as an option to the request. When <OutputType>Duplex</OutputType> is part of the request, Expere scans the .REQ file(s) for the given request to determine if a PrintOption setting has been set ("Simplex" or "Duplex") for the given document(s).
  • If <OutputType>Duplex</OutputType> is part of the request:
    • REQ collate attribute set to "Simplex:" blank pages are inserted after every page of the document(s) with this REQ setting. This ensures when the entire package is printed as "Duplex," the documents that are required print as Simplex are printed with blank pages on the back of every page.
    • REQ collate attribute set to "Duplex" (or "Blank" or "Does Not Exist"): if number of pages in the document is "Odd," a blank page is inserted at the end of the document, to keep the end of one document from printing with the beginning of the next.
  • If <OutputType>Duplex</OutputType> is NOT part of the request:
    • Documents are rendered as they are today. PDFs are created and Simplex/Duplex logic is not applied
Implementation Notes: This feature requires a 2017.1 Expere Engine update.
Attachment order functionality enhanced using <BeginningOrEnd/> element
  • Type: Enhancement
  • Reference: PBI 442670
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: Expere Developer Guide: PDF
Summary: We have enhanced our PDF Attachment functionality to allow users to indicate if they would like their attached document(s) to be returned at the “beginning” or “end” of the documents generated by Expere. Today, when attaching PDF(s) to be returned with the Expere generated documents, users are limited to specifying beginning or end for the group of documents being attached. With the enhanced functionality, users can now use the <BeginningOrEnd/> element to specify the position of each individual PDF being attached, in relation to the Expere generated documents.

Additionally, when working with multiple attachments, users can control the order of their attachments, at the beginning and end, by submitting them in their desired order in the request. Below is an example showing documents being attached with the <BeginningOrEnd/> element included in request and the PDF result:

Request order:

  • DocA - end
  • DocB - beginning
  • DocC - end

PDF Result:

  • DocB
  • Expere Generated Document(s)
  • DocA
  • DocC
Note:
  • If users do not include the <BeginningOrEnd/> element when attaching their own PDF(s), the PDF(s) will be placed at the end of the Expere generated documents.
  • The <BeginningOrEnd/> element is also supported with the MergedPDF Ancillary Output option.
Technical Notes: A sample request with this enhanced functionality would resemble the following:
<c:ExternalPDFDocuments>
<c:PDFs>
             <c:PDF>
                    <c:InstanceDisplayName>ExternalDocONE</c:InstanceDisplayName>
                    <c:InstanceFileName>External_Document_Front_ONE</c:InstanceFileName>
                    <c:DocData>
                           <c:base64>base64 string goes here</c:base64>
                    </c:DocData>
                    <c:BeginningOrEnd>beginning</c:BeginningOrEnd>
             </c:PDF>
</c:PDFs>
</c:ExternalPDFDocuments>
Implementation Notes: This feature requires a 2017.1 Expere Engine update.
Extra underscore added when email address is not present for WKES naming
Summary: We have enhanced WKES naming functionality to now include a two underscore placeholder if the signer does not have an email address.
Technical Notes: Note the following:
  • When an email is present: WKES_<Type>_<email>_<Sequence number>
  • When an email is not present: WKES_<Type>__<Sequence number> with two underscores between <Type> and <Sequence>
Implementation Notes: This enhancement requires a 2017.1 Expere Engine update. See Sequencing: WKES email address sequencing and naming behavior for more information.
Phase now optional in ListDocumentsRequest
  • Type: Enhancement
  • Reference: PBI 459009
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: Expere Developer Guide: Document
Summary: The ListDocumentsRequest has been updated to consist of the following enhancements: when a LineOfBusiness Phase is provided in the request the schema currently requires either a PackageID or a (LineOfBusinessID and Phase). This has been changed to make the Phase optional. Additionally, the ListDocumentResponse now includes the phase name in the appropriate document if the phase was not provided in the request.
Technical Notes: Sample request:
<ListDocumentsRequest xmlns="http://schemas.bankerssystems.com/2004/ExpereAPI/ExpereIEServices">
            <LOBPhase>
                <LineOfBusinessID>PHAS.MockLineOfBusiness</LineOfBusinessID>
                <Phase>Phase1</Phase>
            </LOBPhase>
            <Organization>
                <OrganizationID>00000000000000000000000000000000</OrganizationID>
            </Organization>
        </ListDocumentsRequest>
Sample response:
<ListDocumentsResponse xmlns="http://schemas.bankerssystems.com/2004/ExpereAPI/ExpereIEServices">
			<DocumentSet>
				<Document>
					<DocumentID>PKGD.Resignation</DocumentID>
					<StoredDocID>PKGD.Resignation</StoredDocID>
					<DisplayName>Mock Letter of Resignation</DisplayName>
					<Type>Dynamic</Type>
					<Phase>ClosingPhase</Phase>
				</Document>
			</DocumentSet>
		</ListDocumentsResponse>
Implementation Notes: This feature requires a 2017.1 Expere Engine update.
Package functionality updated to use packet order and remove default packet XML
Summary: Previously, we enhanced Select, SelectAndGenerate, and Generate to accept a fully resolved Package by allowing users to specify desired documents for a package using the Inline package option and then returning those documents in the response. Furthermore, we also enhanced the request file to accept ancillary options using Inline packages.

This work item enhances the default packet to remove the default package XML file if no documents exist and retains the original packet order in the response file.
Technical Notes: The Expere-generated default package will be placed at the end of the Inline package order.
Implementation Notes: This feature requires a 2017.1 Expere Engine update.
PDF bookmark / eSignature behavior enhanced
  • Type: Defect
  • Reference: PBI 444844
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: It was previously reported that bookmarks were appearing in PDF documents despite the eSignature Support option set to "false" in the bsi.properties file (com.bankerssystems.expere.render.eSignatureSupport=false). Expected behavior is that bookmarks should not appear in the PDF document when the eSignature option is disabled.
Solution: This issue has been resolved; bookmarks no longer appear when the eSignature Support option is set to "false" in the bsi.properties file.
Implementation Notes: This feature requires a 2017.1 Expere Engine update.
Expere Engine changelog updated with 2016.3, 2016.2, and 2016.1 schema information
Summary: We have updated our Changelog and Important Notifications page to note schema additions and updates for our 2016.1, 2016.2, and 2016.3 releases.
Implementation Notes: This feature is available in the 2017.1 Expere Engine release.
Barcode enhancement: additional location options
  • Type: Enhancement
  • Reference: 443543
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: Barcode
Summary: Expere Engine users may now select their barcode location in their request by selecting one of the following justification options using the HorizontalAlignment parameter:
  • Left
  • Right
  • Center
These barcode adjustment options affect the following API's:
  • Select and Generate
  • Select
  • Generate
Technical Notes: Sample request consists of the following:
<xs:element name="HorizontalAlignment" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Identifies how the barcode aligns within the form.  Possible values are "Left", "Right", or "Center".</xs:documentation>
          </xs:annotation>
          <xs:simpleType>
            <xs:restriction base="xs:string">
              <xs:enumeration value="Left">
              </xs:enumeration>
              <xs:enumeration value="Center">
              </xs:enumeration>
              <xs:enumeration value="Right">
              </xs:enumeration>
            </xs:restriction>
          </xs:simpleType>
        </xs:element>
Implementation Notes: This feature requires a 2017.1 Expere Engine update. For more information, see Barcode.
eSignature date behavior enhanced
  • Type: Defect
  • Reference: PBI 463254
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: It was reported that when only one borrower was present in a transaction, static forms were highlighting the eSignature date field for both the primary borrower and co-borrower, thus indicating that the co-borrower should enter a date. This is incorrect behavior
Solution: This issue has been resolved; co-borrower eSignature and eSignature date fields are now only highlighted as esignable when a co-applicant or co-borrower is part of the transaction and eSignature fields are requested
Implementation Notes: This feature requires a 2017.1 Expere Engine update.
SignerID issue resolved
  • Type: Defect
  • Reference: PBI 458310
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: It was reported that SignerID was being returned with no string value present, where in pervious versions they were either given a string or 'null' value. This caused corresponding breaking changes to related processes.
Solution: This issue has been resolved; SignerID now returns either a string or 'null' value in the Expere response file.
Implementation Notes: This feature requires a 2017.1 Expere Engine update.
Previously failing transactions now generate normally
  • Type: Defect
  • Reference: PBI 457641
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: An issue was identified that caused transactions to fail when using eSignature functionality. It was determined that a missing element existed in the base functionality.
Solution: This issue has been resolved.
Implementation Notes: This defect correction requires a 2017.1 Expere Engine update.
Expere Engine changelog updated with 2017.1 schema information
  • Type: New Feature
  • Reference: PBI 454098
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: Schema Changes
Summary: Our Expere Engine change now includes information regarding any schema additions and updates, allowing our users to identify schema changes between releases. We have created a new Schema Changes section on the Changelog and Important Notifications page for each release.
Implementation Notes: This new feature is available in the 2017.1 release.
Expere now updated to support latest versions of Microsoft Windows and SQL
Summary: The Expere Engine has been tested to validate that it functions properly with Windows Server 2016 and SQL 2016.
Implementation Notes: This feature requires a 2017.1 Expere Engine update. For more information, consult the Expere System Requirements guide: Windows Environment Software Requirements.
Package functionality added to Select, SelectAndGenerate, and Generate API's
Summary: We have enhanced the Select, SelectAndGenerate, and Generate API's to accept custom packages through a new <InlinePackage/> parameter within each of these API's. This allows users to create or modify one or multiple custom packages for a particular line of business or precedence unit by selecting documents from one or more package or autoselection rules.
Implementation Notes: Consider the following:
  • This enhancement requires picking up the Expere Engine 2017.1 release.
  • Users must select one of the following:
    • PackageID
    • LOBPhase
    • InlinePackage
eSignature Field Order enhancement
  • Type: Enhancement
  • Reference: PBI 444854
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: We modified the method for applying enumerated values to the <eSignature/> fields so that the sequencing method always assigns the highest value in the sequence of each signer to their respective <Type>Signature</Type> fields, hence making the Signature field the last field in the order.
Technical Notes: Here is an example response:
-<r:SignaturePointSet>
  -<r:Signer>
    <r:Id>null</r:Id>
    <r:SignerEmail>firstlast@test.com</r:SignerEmail>
    <r:Description>null</r:Description>
    -<r:SignaturePoints>
      -<r:SignaturePoint>
        <r:IncludeDate>true</r:IncludeDate>
        <r:PageNumber>1</r:PageNumber>
        <r:PageOrder>null</r:PageOrder>
        <r:Height>36.0</r:Height>
        <r:Width>198.0</r:Width>
        <r:SignatureText>null</r:SignatureText>
        <r:XCoordinate>36.0</r:XCoordinate>
        <r:YCoordinate>566.84</r:YCoordinate>
        <r:Type>Signature</r:Type>
        <r:FieldName>WKES_Signaturefirstlast@test.com_2</r:FieldName>
        <r:Sequencing>2</r:Sequencing>
      </r:SignaturePoint>
      -<r:SignaturePoint>
        <r:IncludeDate>false</r:IncludeDate>
        <r:PageNumber>1</r:PageNumber>
        <r:PageOrder>null</r:PageOrder>
        <r:Height>36.0</r:Height>
        <r:Width>50.0</r:Width>
        <r:SignatureText>null</r:SignatureText>
        <r:XCoordinate>238.0</r:XCoordinate>
        <r:YCoordinate>566.84</r:YCoordinate>
        <r:Type>Date</r:Type>
        <r:FieldName>WKES_Datefirstlast@test.com_1</r:FieldName>
        <r:Sequencing>1</r:Sequencing>
      </r:SignaturePoint>
    </r:SignaturePoints>
  </r:Signer>
  -<r:Signer>
    <r:Id>null</r:Id>
    <r:SignerEmail>_first_last@test.com</r:SignerEmail>
    <r:Description>null</r:Description>
    -<r:SignaturePoints>
      -<r:SignaturePoint>
        <r:IncludeDate>true</r:IncludeDate>
        <r:PageNumber>1</r:PageNumber>
        <r:PageOrder>null</r:PageOrder>
        <r:Height>36.0</r:Height>
        <r:Width>198.0</r:Width>
        <r:SignatureText>null</r:SignatureText>
        <r:XCoordinate>309.6</r:XCoordinate>
        <r:YCoordinate>566.84</r:YCoordinate>
        <r:Type>Signature</r:Type>
        <r:FieldName>WKES_Signature_first_last@test.com_2</r:FieldName>
        <r:Sequencing>2</r:Sequencing>
      </r:SignaturePoint>
      -<r:SignaturePoint>
        <r:IncludeDate>false</r:IncludeDate>
        <r:PageNumber>1</r:PageNumber>
        <r:PageOrder>null</r:PageOrder>
        <r:Height>36.0</r:Height>
        <r:Width>49.99997</r:Width>
        <r:SignatureText>null</r:SignatureText>
        <r:XCoordinate>511.6</r:XCoordinate>
        <r:YCoordinate>566.84</r:YCoordinate>
        <r:Type>Date</r:Type>
        <r:FieldName>WKES_Date__first_last@test.com_1</r:FieldName>
        <r:Sequencing>1</r:Sequencing>
      </r:SignaturePoint>
    </r:SignaturePoints>
  </r:Signer>
</r:SignaturePointSet>
Implementation Notes: This enhancement requires picking up the Expere Engine 2017.1 release. and setting the <eSignatureWKES/> option to "true."
WKES Sign Date Naming Convention
  • Type: Enhancement
  • Reference: PBI 442435
  • Compliance Impacts: This item iis not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: The WKES Sign Date fillable field naming convention has been updated from WKES_date to WKES_signdate.
Implementation Notes: No user action is required.
eSignature Enhancements
  • Type: Defect
  • Reference: PBI 440808
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue:

We have updated the field name elements for the eSignature and eSignatureDate within the PDF and ExpereResponse file as part of the SignaturePointSet element.

The eSignature field name has been updated to no longer include the borrower name, additionally, the eSignatureDate field name for Static content has been updated to be consistent with Dynamic content.
Solution:

The specific changes to the eSignature and eSignatureDate field names are captured below.

Before:

eSignature Field Name: SIG_Borrower_1_1_true_1_BobbyBorrower_BW1Name.eSig

eSignatureDate Field Name: BW1Name.eSig.eSigDate

After:

eSignature Field Name: SIG_Borrower-1_1_true_1_BW1Name.eSig

eSignatureDate Field Name: SIG_Borrower_1_1_true_1_BW1Name.eSig.eSigDate
Implementation Notes: No user action is required.
EnableEsignatureManifest Added to BSI.Properties
  • Type: Enhancement
  • Reference: PBI 440811
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: As a means to enable or disable the esignature manifest file we have added a flag, EnableEsignatureManifest, to BSI.Properties. With the default of FALSE, Expere does not look for the esigmanifest file as part of the content. When set to TRUE, the esigmanifest file is expected to be in the content repository.
Implementation Notes: No user action is required.
Version Number Added to Schemas
  • Type: Enhancement
  • Reference: PBI 442215
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No external-facing tools user documentation; all Expere request and response schemas.
Summary: We have included a version number in all Expere request and response schemas, such as ApiTypes.xsd and PackageAndDocSet.xsd; this will help users identify the version of schema with which they are working.
Note: The schema version number is synonymous with the Expere Engine version number.
Technical Notes: A sample version number resembles the following (see version= below): 
<xs:schema 
xmlns="http://schemas.bankerssystems.com/2004/ExpereAPI/ExpereIEServices" 
xmlns:xs="http://www.w3.org/2001/XMLSchema" 
targetNamespace="http://schemas.bankerssystems.com/2004/ExpereAPI/ExpereIEServices" 
elementFormDefault="qualified" attributeFormDefault="unqualified" 
version="17.1.0.4255">
Implementation Notes: No user action is required.
New ApplyPoliciesAndReturnTransaction API introduced
  • Type: New Feature
  • Reference: PBI 432140
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: ApplyPoliciesAndReturnTransaction
Summary: The ApplyPoliciesAndReturnTransaction API has been implemented to update the provided transaction with the provided Product information. This allows users to pass the updated returned transaction (which includes the Product information) into our DocViewer application, as well as the ability to use Select, SelectAndGenerate, or Generate API's to generate documents with product data.
Implementation Notes: See ApplyPoliciesAndReturnTransaction for detailed information on using this new API.
Expere Engine: Pinyon Script added to JetFonts.xml
  • Type: Enhancement
  • Reference: PBI 437588
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: We have added Pinyon Font to the jetfonts.xml file within our Expere Engine. This will allow users to generate a static document with a script font.
Implementation Notes: No user action is required.
Text string area message enhanced
  • Type: Enhancement
  • Reference: PBI 406465
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: Previously if a <Text/> element's text string contained more characters than what was allowed, an error message was logged. We have updated the logging level for this message to be WARN instead of ERROR.
Implementation Notes: No user action is required.
Logging levels updated
  • Type: Enhancement
  • Reference: PBI 432256
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: Previously, all exceptions that appeared in our log files were reported as errors. This did not reflect the nature nor severity of the exception being logged.
Technical Notes: We have modified our level of logging to consist of the following:
  • Fatal: major system outage or SQL exception
  • Error: system error that does not set off an alert; retries; ongoing system issue
  • Warning: transactions with invalid GUID format, permissions issues, invalid characters being passed in, invalid transaction xml, etc
Implementation Notes: No user action is required.
Fillable Fields now support XML special characters
  • Type: Enhancement
  • Reference: PBI 429006
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: Users reported an issue when sending a transaction data value containing a special character in a pre-populated fillable text field. As a result, the document would not assemble due to the special character.
Summary: Fillable fields and Signature Point Set's now support XML special characters (as long as they are escaped) and render the PDF and the XML response file properly. The list of XML 1.0 special characters consist of the following:
  • quot: "
  • amp: &
  • apos: '
  • lt: <
  • gt: >
Implementation Notes: No user action is required.
<SaveInDatabase/> behavior modified
  • Type: Defect Correction
  • Reference: PBI 423040
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: We have enhanced the <SaveInDatabase/> element behavior for Select API calls.
Technical Notes: We have changed the default value from "true" to "false" for the <SaveInDatabase/> element in Select API calls. With this change, Select requests by default are no longer saved in the database.
Implementation Notes: Users should change the <SaveInDatabase/> element value to "true" to save Select requests in the database.
eSequence fields behavior enhanced
  • Type: Enhancement
  • Reference: PBI 424154
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: Expere Developer Guide: Sequencing
Summary: We have enhanced the behavior of sequencing fillable fields and signature points, to ensure that sequencing is implemented when the PDF is being merged or if the XML contains duplicate Names.
Implementation Notes: A combination of the <WKES/> element <MergePDF/> element settings determine sequencing behavior. The Expere Developer Guide: Sequencing contains extensive details on this enhanced sequencing behavior.
Expere Engine: ability to merge closing disclosures with addendum
  • Type: Enhancement
  • Reference: PBI 416499
  • Compliance Impacts: This enhancement is not a compliance or regulatory issue.
  • Documentation: MergeTRIDDocs flag - PDF
Summary: We have implemented a new <MergeTRIDDocs/> element that allows users to merge the following TRID documents through the request file:
  • ClosingDisclosure
  • ClosingDisclosureAddendum
  • ClosingDisclosure-SellerOnly
  • ClosingDisclosure-SellerOnly-Addendum
Technical Notes: With this enhancement, if the <MergeTRIDDocs/> flag is set to "true" in the Expere request, the addendums above are merged with the associcated closing disclosure into a single standard PDF file. As a result, the closing disclosure, merged with the addendum, is returned in the response with the normal closing disclosure instance name and the addendum instance is removed from the response.
Implementation Notes: For more information, see MergeTRIDDocs flag - PDF in the Expere Developer Guide
Caching database organizations configurable
  • Type: Enhancement
  • Reference: PBI 423298
  • Compliance Impacts: This enhancement is not a compliance or regulatory issue.
  • Documentation: No document impact.
    Important: This enhancement impacts those users who utilize OPPSA organizations.
Summary: Previously, all organizations were cached together, including OPPSA organization. This presented an issue when multiple Expere instances were used, including the hosted OPPSA application. Expere cleared the AllOrganizationsList object from the database whenever OPPSA changed, but this was insufficient.
Technical Notes: We have implemented an enhancement to our database caching capabilities: com.bankerssystems.database.organization.caching was added to the bsi.properties file.
## When set to false the organization structure from the database, which includes the OPPSA organizations won't be cached.
## Set this to false if there will be more than one Expere server in an OPPSA environment
## The default is true if this key isn't found
com.bankerssystems.database.organization.caching=true
Implementation Notes: By default the value is set to "true" but should be set to "false" when Expere installed with Document Generation Services. Users can modify the <ENABLE_ORGANIZATION_CACHE/> element within the transform.xml file.
Expere Engine: Ability to produce merged disclosures for either PDF or PDF/A documents
  • Type: Enhancement
  • Reference: PBI 416499 / 420185 / 421946 / 427156
  • Compliance Impacts: This enhancement is a compliance or regulatory issue.
  • Documentation: RequestUCD flag - PDF/A
Summary: Previously in PBI 416188, we enhanced Expere to support the following documents in PDF/A format:
  • ClosingDisclosure
  • ClosingDisclosureAddendum
  • ClosingDisclosure-SellerOnly
  • ClosingDisclosure-SellerOnly-Addendum
Technical Notes: The request file contains a new <RequestUCD/> element that, when set to "True," produces the documents below in a PDF/A format, and if the addendum is produced, merges it with its respective closing disclosure. The merged document is returned in the response as the closing disclosure instance and the addendum instance is removed. If not setting the flag, documents are produced using the standard PDF format and the documents are not merged.
Implementation Notes: For more information, see RequestUCD flag - PDF/A in the Expere Developer Guide.
PDF Merge enhanced to include SignaturePointSet
  • Type: Enhancement
  • Reference: PBI 421260
  • Compliance Impacts: This enhancement is not a compliance or regulatory issue.
  • Documentation: No document impact.
Summary: We recently included support for PDF Merge functionality with Expere whereby a </SignaturePointSet> element is now returned in the response when at least one document has fields and PdfMerge is requested.
Implementation Notes: No user action is required.

January - Expere Engine 2016.3.0.3995External release date is December 22, 2016.

PDF/a now available in Expere
  • Type: New Feature
  • Reference: PBI 416188
  • Compliance Impacts: This new feature is not a compliance or regulatory issue.
  • Documentation: RequestUCD flag - PDF/A
Summary: Expere users can now produce the following documents in PDF/A format:
  • ClosingDisclosure
  • ClosingDisclosureAddendum
  • ClosingDisclosure-SellerOnly
  • ClosingDisclosure-SellerOnly-Addendum
Technical Notes: The request file now contains a new <RequestUCD/> element that, when set to "True," produces the documents above. If not setting the flag, documents are produced using the standard PDF format.
Implementation Notes: What is PDF/A format? It is an ISO 19005 compliance PDF file used for archiving and long-term preservation of electronic documents. For more information, see the following:
BSI.properties file updated to include new eSignature PDF Merge flag in Expere installer
  • Type: Enhancement
  • Reference: PBI 422704
  • Compliance Impacts: This enhancement is not a compliance or regulatory issue.
  • Documentation: No document impact.
Summary: We have updated the BSI.properties file for the Expere Wildfly installer to include the following lines:
## Indicates whether the ESignatures and MergePDF output is enabled
com.bankerssystems.expere.model.ESigPdfMerge=true
This enables eSignature and PDF Merge functionality for Expere.
Implementation Notes: No user action is required.
Fillable field checkboxes behavior enhanced for all documents
  • Type: Enhancement
  • Reference: PBI 420627
  • Compliance Impacts: This enhancement is not a compliance or regulatory issue.
  • Documentation: No document impact.
Summary: In a previous release, we implemented enhancements that return XY coordinates for all fillable fields (Expere Engine: continued enhancement of eSignatureAndFieldSupport and SignaturePointSet elements; Expere Engine: SignaturePointSet and eSignatureAndFieldSupport element changes). In this release, checkboxes associated with fillable fields now appear on all documents even if requesting X/Y coordinates. Note the following guidelines:
  • When X/Y coordinates is "True" in a request, the fillable field checkboxes are rendered on the form but are not fillable checkboxes; the fillable field checkboxes appear on the form as an empty checkbox (with no blue shading).
  • When X/Y coordinates are not requested, fillable field checkboxes are rendered on the form with blue shading designating it is a fillable field and appear as a checked checkbox.
Implementation Notes: For more information, see Using eSignature and Acroform fields.