2018 Release Two (2) Expere Engine and Tools Changelog

Expere Engine Release: 2018 Release Two (2)External release date is 6/27/2018. Expere Engine build number is: 2018.2.0.4867 .

Content used for testing:

  • April 26, 2018: 2018060818.2.0.4867-J20180426Y

New Features

  • See Features page for more information.
Enhancements

Defect Corrections

  • None
bsi.properties file enhanced with additional information
  • Type: Enhancement
  • Reference: PBI 504552
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: It was identified that some settings within the bsi.properties file are unclear on what they are intended for and what functionality they impact. We have reviewed through the bsi.properties file and added comments to various settings, identifying their intended use.
Technical Notes: Comments were added to the following settings:
  • com.bankerssystems.expere.render.EnableEsignatureManifest=false
  • ## com.bankerssystems.expere.model.DpiX=200
## com.bankerssystems.expere.model.DpiY=200
## com.bankerssystems.expere.model.2DBarcodeWidth=2.42
## com.bankerssystems.expere.model.2DBarcodeHeight=0.41
  • com.bankerssystems.expere.model.ESigPdfMerge=true
Implementation Notes: This enhancement is available in the Expere Engine 2018 Release Two (2).
Support for multi-line fillable fields with underlines now available for static and dynamic documents
  • Type: Enhancement
  • Reference: PBI 500183 / 500256
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: Expere Developer Guide: FillableText
Summary: Expere now supports fillable fields with multiple lines when utilizing the <eSignatureAndFieldSupport/> element in the request. Those documents that contain multiple line fillable fields will print multiple lines of text with underlines to easily identify fields which were manually completed.

Additionally, the Expere response will include a new <MultiLine/> element within <FillableFieldSet/> is set to "true." As a result, a fillable field is generated on a document that supports multiple line of texts, and the text entered in the fillable field appears and prints on the line starting in the top left corner of the field.
Technical Notes: A sample response consists of the following:
<r:FillableFieldSet>
       <r:FillableText>
             <r:FieldName>Lender.FullNameStreetCityStateZip_1</r:FieldName>
             <r:ToolTip>Lender.FullNameStreetCityStateZip_1</r:ToolTip>
             <r:Width>203.22</r:Width>
             <r:Height>40.96997</r:Height>
             <r:XCoordinate>39.98</r:XCoordinate>
             <r:YCoordinate>905.7</r:YCoordinate>
             <r:Sequencing>1</r:Sequencing>
             <r:FontName>Courier</r:FontName>
             <r:FontSize>10.0</r:FontSize>
             <r:NumberOfCharacters>0</r:NumberOfCharacters>
              <r:FieldText>This is just some text</r:FieldText>
             <r:HorizontalAlignment>Left</r:HorizontalAlignment>
             <r:Underline>false</r:Underline>
             <r:PageNumber>1</r:PageNumber>
             <r:MultiLine>true</r:MultiLine>
       </r:FillableText>
</r:FillableFieldSet>
Implementation Notes: This enhancement is available in the Expere Engine 2018 Release Two (2).
Expere Engine upgraded for use with Oracle 12c R2
Summary: The Expere Engine has been upgraded for use with Oracle 12c R2.
Implementation Notes: This enhancement is available in the 2018 Release Two (2) of the Expere Engine.
WKES prefix and email address added to fillable field and fillable checkbox field name
  • Type: Enhancement
  • Reference: PBI 500175
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: Previously, we only provided the WK E-Sign (WKES) prefix on signature, signature date, and initials. We have enhanced Expere to now support completing fillable fields and checkboxes through WKES by providing the WKES standard prefix. In addition to adding the WKES prefix to other remaining fillable fields, we also included an 'O' for Optional or 'M' for Mandatory indicator to the end of the field name for fields that are not signature, signature date, or initials.

Now when a request includes an indicator for <eSignatureAndFieldSupport/> with WKES (eSignatureAndFieldSupport ="true" in the request transaction), the following AcroField Naming convention is followed:

  • signatures, signature date, initials fields, checkboxes, name, numeric, alphanumeric , and multi-line alphanumeric fields: 
    WKES_FieldType_UserEmail_FieldOrder
  • checkboxes, name, numeric, alphanumeric, and multi-line alphanumeric fields: 
    WKES_FieldType_UserEmail_FieldOrder_O 
WKES_FieldType_UserEmail_FieldOrder_M
Implementation Notes: This enhancement is available in the Expere Engine 2018 Release Two (2).
Note: This enhancement will not change the appearance of the final printed documents.
DocInstance now identifies documents as NoSignatures, InkSign, or ESign
Summary: The Expere response now includes InstanceSigningInstructionsType as part of the DocInstance. InstanceSigningInstructionsType identifies the document as being eSignable, ink sign, or no sign. The response will specifically identify each document as NoSignatures, InkSign, or ESign.
Technical Notes: If documents are not authored to support eSignatures or if ESignatureAndFillableFieldSupport is NOT requested, all documents will be identified as InkSign, or NoSignatures.
Implementation Notes: This enhancement is available in the Expere Engine 2018 Release Two (2).
eSignature Document indicator honored for use with signature fields
Summary: A recent change allows Expere to honor a new eSignature Document indicator in the Document Properties dialog of the Requirement Editor. With this change, the Expere response will include a new child element, ESignatureDocument, within the DocDescriptor element, indicating “True” if the document is esignable or “False” if the document is not esignable.
We have added the following configuration option within the bsi.properties file, and set it to 'false' to disable this feature until a future date:
  • com.bankerssystems.expere.render.EnableSigningInstructions=false 
Implementation Notes: This enhancement is available in the Expere Engine 2018 Release Two (2).