2016.3 Expere Engine and Tools Changelog Entries

• Type: Enhancement
• Reference: PBI 411599 / 410789
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: SignaturePoint, FillableCheckbox, FillableText

We have introduced a new <Sequencing/> element to the following field types in the Expere response file:

• Signature (SignaturePoint element)
• Date
• Initials
• FillableText
• FillableCheckboxes

This <Sequencing/> element is implemented for the Secure Document Exchange (SDX) product for those users who sign across documents. It also makes each field unique so Expere can merge PDF documents that use signature, date, initial, and fillable text fields.

If the "MergePDF=true" in the Expere response file, the Signature, Date, Initials, FillableCheckboxes and FillableText field types elements will contain sequencing in the <FieldName/> element using an incremental numbering system with an underscore.

<r:SignaturePointSet> 
<r:Signer> <r:Id>Homer</r:Id> 
<- Signer ID 
<r:Description>Borrower, Borrower</r:Description> 
<r:SignaturePoints> 
<r:Type>Initials</r:Type> 
<r:Sequencing>1</r:Sequencing> 
<r:FieldName>INI_Borrower_null_homer_false_1_SigField_1</r:FieldName> </r:SignaturePoint> 
<r:SignaturePoint> 
<r:IncludeDate>true</r:IncludeDate> 
<r:PageNumber>1</r:PageNumber> 
<r:SignatureText>Homer Simpson</r:SignatureText> 
<r:Type>Signature</r:Type> 
<r:Sequencing>2</r:Sequencing> 
<r:FieldName>SIG_Borrower_null_homer_false_1_SigField_2</r:FieldName> </r:SignaturePoint> 
<r:FillableFieldSet> 
<r:FillableText> 
<r:FieldName>FillableField_3</r:FieldName> 
<r:ToolTip>fill in here</r:ToolTip> 
<r:PageNumber>1</r:PageNumber> 
<r:Width>420.0</r:Width> 
<r:Height>72.0</r:Height> 
<r:XCoordinate>56.0</r:XCoordinate> 
<r:YCoordinate>100.0</r:YCoordinate> 
<r:Sequencing>3</r:Sequencing> 
</r:FillableText> <FillableCheckBox> 
<r:FieldName>FillableCheckBox_4</r:FieldName> 
<r:ToolTip>check here</r:ToolTip> 
<r:PageNumber>1</r:PageNumber> 
<r:Checked>false</r:Checked> 
<r:XCoordinate>22.0</r:XCoordinate> 
<r:YCoordinate>140.0</r:YCoordinate> 
<r:Sequencing>4</r:Sequencing> 
</FillableCheckBox> 
</r:FillableFieldSet> 

• Type: Enhancement
• Reference: PBI Number
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: Using eSignature and Acroform fields

In a previous release, we added a new element called eSignatureWKES, which allowed Wolters Kluwer Electronic Signature (WKES) users to initial documents with a fillable text field (Acroform). Please refer to changelog notes for PBI 408221 - Secure Document Exchange users initials can now render with Acroform fields for past work.

We have enhanced this functionality to now follow WKES (previously Secure Document Exchange) naming conventions for initial(s) and checkbox fields. The following behavior now applies:

• If the eSignatureWKES flag is set to "False," the following occurs:
  • Initials are rendered as esignable;
  • Current naming convention is used: <r:FieldName>INI_Borrower_null_homer_false_1_SigField_1</r:FieldName>;
• If the eSignatureWKES flag is set to "True," the following occurs:
  • WKES (previously SDX) naming conventions apply;
  • The <FieldName/> element applies eSignatures for "Initials," "Signature," "Date," and "Checkbox;"

• Type: Enhancement
• Reference: PBI 413765
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

Users may now select which fillable fields, including eSignature fields, appear or do not appear on documents based on a selected package. This functionality is accomplished by supporting an exclusion list per account in the content library which suppresses the fillable fields in any documents included in the list based on the package.

This exclusion list now resides in the .XML file in order to enable this functionality; the .XML file is stored in your custom content folder of the appropriate repository.

PKG.ABC PKGD.DOC1 PKGD.DOC2 PKG.DEF PKGD.DOC1 PKG.GHI PKGD.DOC1 PKGD.DOC3 

When requesting a transaction for PKG.ABC and that request generates PKGD.DOC1 or PKGD.DOC2, the fillable fields will be suppressed on those two docs, but will remain on all others with fillable fields. If the XML file is empty or the users requests a transaction for a package not in the list, all documents rendered that have fillable fields will be produced with fillable fields.

• Type: Enhancement
• Reference: PBI 414317
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

• Type: Enhancement
• Reference: PBI 410707
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: Applying OPPSA compatibility configuration changes

Previously, users had to modify transaction data sent to Document Generation Service with the Expere database values.

Users can now apply OPPSA compatibility configuration changes to their appropriate Expere distributed or hosted installation package through database updates. This allow their Expere instance to connect to the Expere OPPSA database to receive policy and organization data and FileSystem content.

• For Expere Engine installations, must enter the Expere database information in the bsi.properties file. See Applying OPPSA compatibility configuration changes for more information.
• For JBoss/Wildfly installations, add the database information to the standalone.xml file located in wildfly-10.0.0.Final\standalone\configuration\. See Applying OPPSA compatibility configuration changes - JBoss/Wildfly installations for more information.

• Type: Enhancement
• Reference: PBI Number
• Compliance Impacts: This new feature/enhancement is not a compliance or regulatory issue.
• Documentation Impacts: Signer, SignaturePoint

We have implemented the following enhancements to the <SignaturePointSet/> element:

• We have added a new <SignerEmail/> element to the <Signer/> element;
• We have enhanced the <FieldName/> element in the <SignaturePoint/> element to include the email address

These elements appear in the Expere response file when including the "eSignatureWKES" flag in the initial request. Sample code below:

<r:SignaturePointSet> 
<r:Signer> 
<r:Id>homer</r:Id> 
<r:SignerEmail>Joe.Doe@wolterskluwer.com</r:SignerEmail> 
<r:Description>Borrower, Borrower</r:Description> 
<r:SignaturePoints> 
<r:SignaturePoint> 
<r:IncludeDate>true</r:IncludeDate> 
<r:PageNumber>1</r:PageNumber> 
<r:PageOrder>1</r:PageOrder> 
<r:Height>72.0</r:Height> 
<r:Width>540.0</r:Width> 
<r:SignatureText>Homer Simpson</r:SignatureText> 
<r:XCoordinate>36.0</r:XCoordinate> 
<r:YCoordinate>396.0</r:YCoordinate> 
<r:Type>Initials</r:Type> 
<r:FieldName>INI_Borrower_null_homer_false_1_SigField_joe.doe@wolterskluwer.com</r:FieldName> 
</r:SignaturePoint> 
</r:SignaturePoints> 
</r:Signer> 
</r:SignaturePointSet>

• Type: Enhancement
• Reference: PBI 406462
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

As data requirements functionality is not supported in the Hosted Expere application, SCHEMA files are not required. However, missing schema files would cause unnecessary errors in the log files.

We have modified missing schema file requirements; when a document request is made for a document that does not have a corresponding schema file a message is now logged as a warning (WARN) instead of error (ERROR).

• Type: Enhancement
• Reference: PBI 406459
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

• No packageDocs were specified for processing
• No documents were supplied for assembly

These two responses should not be considered errors. These responses are simply indicating the transaction provided does not meet any of the document autoselection criteria, and therefore did not select any documents.

The log file has been enhanced to now display these two responses under a status of INFO status instead of an ERROR status when a SelectAndGenerate call is inititated but no documents are generated.

• Type: Defect
• Reference: PBI 376369
• Compliance Impacts: This defect correction is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

• In com.bankerssystems.expere.render.Signer.java signerNames could be overwitten by separate transactions when Expere processed multiple transactions.
• In com.bankerssystems.expere.render.AncillaryOutputServices.java a transaction could clear out the name of a different transaction.

• Type: Enhancement
• Reference: PBI 408221
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: Using eSignature and Acroform fields

<r:AncillaryOutputOption> <r:OutputType>ESignatureAndFieldSupport</r:OutputType> 
<r:ESignatureAndFieldSupport> 
<r:eSignatureTooltip/> 
<r:eSignatureInitialsTooltip/> 
<r:eSignatureCoordinatesOnly>false</r:eSignatureCoordinatesOnly> 
<r:eSignatureDateSupport>true</r:eSignatureDateSupport> 
<r:NonSignatureFieldCoordinatesOnly>true</r:NonSignatureFieldCoordinatesOnly> 
<r:eSignatureWKES>false</r:eSignatureWKES> 
</r:ESignatureAndFieldSupport> 
</r:AncillaryOutputOption>

• Type: Enhancement
• Reference: PBI 397414
• Compliance Impacts: This item is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

## Indicates whether 2D barcodes should use DPI or scaling 
## If these DPI values are commented out, then scaling will be used. 
## 2D Barcode Height and Width are in inches 
## 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 

• Type: Defect
• Reference: PBI 408584
• Compliance Impacts: This defect correction is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

• Type: Defect
• Reference: PBI 409994
• Compliance Impacts: This defect correction is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

• Type: Enhancement
• Reference: PBI 405389
• Compliance Impacts: This enhancement is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact

We have implemented code changes to honor requests containing non-default values for <Error Correction/>, <Rows/>, and <Columns/> element values.

• Type: Enhancement
• Reference: PBI 405248
• Compliance Impacts: This enhancement is not a compliance or regulatory issue.
• Documentation Impacts: No documentation impact