2020 Release Two (2) Expere Engine and Tools Changelog
Expere Engine Release: 2020 Release Two (2)External release date is July 2020. Expere Engine build number is: 2020.2.0.3138.
Content used for testing:
- July 8, 2020: 2020070820.2.0.3138-N20181223N
New Features
Enhancements
Defect Corrections
| New NotaryStamp options added |
|---|
|
Summary: The Expere schema has been updated with new FieldTypeEnum value of NotaryStamp. This new enum value is being added in anticipation of Expere content updates to support eNotary. Adding this value will allow integrators to use the Expere response to determine what field(s) on the document are intended for notary use. Electronic signing partners will then be able to appropriately assign signer roles based on the FillableFieldType. Additionally, we have added a new SignatureUniqueIdentifier element that is used to asssociate the FillableField to the applicable SignatureField. |
| Implementation Notes: This feature is available in the 2020 Release Two of the Expere Engine. |
| EnableEsignatureManifest method behavior enhanced |
|---|
|
Summary: Previously in PBI 607893, content had been updated to indicate eSign in the
.REQ file replacing the ESignature manifest file previously
stored with the content. As a result, the ESignature
manifest file and its bsi.properties setting was no longer
needed. Expere bsi.properties was updated to default the
com.bankerssystems.expere.render.EnableEsignatureManifest
setting to “false.” We recommended that you update your content to use the
new ESignature indicator within the .REQ file if your content used the old
ESignature manifest file. A new ESignature
setting has been implemented in the .REQ file. and the
|
| Implementation Notes: This enhancement is available in the 2020 Release Two (2) of the Expere Engine. |
| Fillable fields in FooterNotice not applied to subsequent middle pages |
|---|
|
Issue: It was reported that Initials fields did not appear as fillable fields in pages between the first and last pages of a PDF document. When authored as fillable fields with a MiddlePages attribute in a FooterNotice element, the fillable fields appeared only on the second page of the document; all subsequent pages with the exception of the last page do not display fillable fields in the FooterNotice. |
Solution: Fillable fields in FooterNotice are applied to additional middle pages, specifically the Initials fields.  |
| Implementation Notes: This defect correction is available in the 2020 Release Two (2) of the Expere Engine. |