# Expere Engine and Tools Archived Change Log Entries

- New Features
  - SignerEmail element and email address associated with FieldName element added to Expere response file
  - Secure Document Exchange users initials can now render with Acroform fields
- Enhancements
  - Error logging enhanced
  - SelectGenerate logging enhanced
  - Ability to configure DPI for PDF417 Ancillary Barcode
  - Barcode options to honor rows, columns, and error correction level
  - Script font enhancements
  - PDFMerge updated to use the latest version of iText
  - DiscretePartyID elements added to GetGenerateResponse
  - Expere Engine: ability to clear javascript cache
  - DocViewer release notes now available
  - Sequence fields functionality incorporated with MergePDF
  - eSignatureWKFS functionality enhancement
  - Ability to suppress fillable fields
  - DiscretePartyID enhanced for static documents
  - Configuration settings enhanced for OPPSA
- Defect Corrections
  - signerNames HashMap enhanced
  - Expere database enhancement
  - Invalid PDF syntax issue addressed through cover sheet generation

## Expere Engine 2016.3 Release

The 2016.3 release contains several enhancements, including a new `<SignerEmail/>` element; a new `</eSignatureWKES>` acroform field used with fillable text fields; logging enhancements; and the ability to configure DPI for PDF417 Ancillary Barcodes. For detailed information, see the Current Release Change Log Entries section below and Expere Engine and Tools Change Log Entries.

## *** Expere Engine 2016.2.2 Release ***

Important: This Expere Engine 2016.2.2 release impacts all users who received the Expere Engine release shipped on August 4th and September 1st. Users should install 2016.2.2 to implement the change outlined below.

The 2016.2.1 Expere Engine release update is reestablishing Expere processing of XML using XPath 1.0 compatibility mode. The 2016.2 Expere Engine release changed the processor to Xpath 2.0, this release update is to reintroduces the previous behavior that enabled XPath 1.0 compatibility mode and makes it the default. Users should install the 2016.2.2 Expere Engine release rather than the 2016.2. Expere Engine update provided on August 4th and September 1st.

The 2016.2.2 release also includes the latest version of the Organizational Policy and Product Setup Application (OPPSA).

## .NET Installation Enhancement

For .NET Expere Implementations, users must download and install `vcredist_x64.exe` available from Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package MFC Security Update before installing the Expere Engine and related components. After installing this file, users must restart IIS.

For more information, refer to Before Installing - .NET Users: Java 8 Requirement in the Expere Implementation Guide.

## ***Expere 2016.2 Engine Release - Important update regarding Java 8 and Saxon upgrade: DB and File System script process***

We have recently implemented Java 8, Saxon, and stylesheet upgrades; with these upgrades, users must run a script to remove duplicate imports for the database and file system.

Note: The following scripts are available on your release media in the Scripts folder. The supporting installation documents are available on our webhelp server; click the appropriate link for more information:

- `RemoveDuplicateImports.ps1`: for File System users using a Powershell script.
- Process-for-file-system-ps.pdf
- `RemoveDuplicateImportsOracle.ps1`: for Oracle SQL users who prefer to use a Powershell script.
- Process-for-Oracle-ps.pdf
- `RemoveDuplicateImportsOracle.sql`: for Oracle SQL users who prefer to use a SQL script rather than a Powershell script.
- `RemoveDuplicateImportsSQL.sql`: for Microsoft SQL server users who prefer to use a SQL script rather than a Powershell script.
- Process-for-SQL-scripts.pdf; this procedure applies to both Oracle and Microsft SQL server users.
- `RemoveDuplicateImportsSQL.ps1`: for Microsoft SQL server users who prefer to use a Powershell script.
- Process-for-SQL-ps.pdf

## Important update regarding the Expere Config Tool

It was reported that there is an issue with running Expere Config Tool utility. We are currently working on the fix and will make it available soon. In the meantime, the following Expere Config Tool utility configuration files can be updated manually using a text editor:

- bsi.properties: located at: "C:\inetpub\wwwroot\Expere\bin\bsi.properties"
- web.config.xml: located at "C:\inetpub\wwwroot\Expere\Web.Config"
- log4j.xml: located at "C:\inetpub\wwwroot\Expere\bin\log4j.xml"

To update the Database Settings, navigate to the bsi.properties file; update the following database settings:

- (Hostname) com.bankerssystems.expere.db.Host=""
- (Port) com.bankerssystems.expere.db.Port=""
- (Database) com.bankerssystems.expere.db.Sid=""
- (Username) com.bankerssystems.expere.db.User=""
- (Password) com.bankerssystems.expere.db.Pass=""

To update logging, navigate to log4j.xml file; update the following:

- (Filepath) <param name="File" value="Expere/ExpereIEServicesRequests.log"/>
- (Level) Uncomment out the following:

       <logger name="com.bankerssystems">
       <level value="info" />
       </logger>

  Available options for level value include:
  - info
  - error
  - fatal
  - debug
  Attention: Only one value can be set.

To update the Performance Options, navigate to web.config file, update the following:

- (Min JVM Heap Size - MB) <java.option value="-Xms256m" />
- (Max JVM Heap Size - MB) <java.option value="-Xmx512m" />:

Note: Max Cached Object is no longer applicable.

To update the following Certificate Settings, navigate to the bsi.properties.xml file; update the following settings:

- (Key Store Type) keystore.type=""
- (Key Store Provider) keystore.provider=""
- (Key Store URL) keystore.url=""
- (Key Store Password URL) keystore.password.url=""
- (Private Key Password URL) keystore.privatekey.password.url=""
- (Certificate Alias) tamperseal.certificate.alias=""

## Previous Release Notes

- Expere Release Notes 2015.2
- Expere Release Notes 2015.2.0.09
- Expere Release Notes 2015.2.0.3260
- Expere Release Notes 2015.2.1
- Expere Release Notes 2015.2.2
- Expere Release Notes 2015.2.3
- Expere Release Notes 2015.3
- Expere Release Notes 2015.3.0.10
- Expere Release Notes 2015.3.0.12

The effective date for all products within the scope of this document for this release is . This release utilizes Expere Engine version 2016.3.0.

## Sequence fields functionality incorporated with MergePDF

- Type: Enhancement
- Reference: PBI 41080
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Documentation: 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 can merge PDF documents that use signature, date, initial, and fillable text fields.

If the "MergePDF=true" in the 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.

Sequencing logic and format example:

    <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>

## eSignatureWKFS functionality enhancement

- Type: Enhancement
- Reference: PBI 410993
- Compliance Impact: This enhancement is not a compliance or regulatory issue.
- Reference: 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 change log 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;"

## Ability to suppress fillable fields

- Type: Enhancement
- Reference: PBI 413765
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Documentation:

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.

.XML structure:

    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.

## DiscretePartyID enhanced for static documents

- Type: Enhancement
- Reference: PBI 414317
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Documentation: No document impact.

Previously, DiscretePartyID's were only returned for dynamic documents. We have now enhanced the DiscretePartyID functionality to be returned with static documents.

## Configuration settings enhanced for OPPSA

- Type: Enhancement
- Reference: PBI 410707
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Documentation: 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 - .NET Installations 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.

## SignerEmail element and email address associated with FieldName element added to Expere response file

- Type: Enhancement
- Reference: PBI 410166
- Compliance Impacts: This new feature/enhancement is not a compliance or regulatory issue.
- Documentation: 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

This element appears 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>

## Error logging enhanced

- Reference: PBI 406462
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Documentation: No document 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).

## SelectGenerate logging enhanced

- Reference: PBI 406459
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Documentation: No document impact.

Previously, a `SelectAndGenerate` document request that did not select any documents resulted in the following errors:

- `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.

## signerNames HashMap enhanced

- Reference: PBI 376369
- Compliance Impacts: This defect correction is not a compliance or regulatory issue.
- Documentation: No document impact.

Previously, the signerNames HashMap variable was designated as "static;" as a result, the a potential for the following issues existed:

- 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.

This issue has been resolved by changing the way SignerName is stored in the Signer class; as a result, the signer name is assigned correctly on a per-transaction basis.

## Secure Document Exchange users initials can now render with Acroform fields

- Type: Enhancement
- Reference: PBI 408221
- Compliance Impacts: This new feature is not a compliance or regulatory issue.
- Documentation: Expere Developer's Guide: Using eSignature and Acroform fields

Wolters Kluwer Electronic Signature (WKES) users can now initial documents with a fillable text field (Acroform) using a new element called `</eSignatureWKES>`, as a child of the `</ESignatureAndFieldSupport>` element in the `</AncillaryOutputOption>`. If setting this element to "true," the initials render as a fillable text field on the document(s). By default, this element is set to "false" and renders as an eSignature field. In a future release, WKES users will be able to capture initials one time per signer and populate those initials to all the respective signer 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>

## Expere Engine: Ability to configure DPI for PDF417 Ancillary Barcode

- Type: Enhancement
- Reference: PBI 397414
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Documentation: No documentation update.

Users can now configure the DPI of PDF417 barcodes. This allows users more flexibility when scanning and imaging documents.

In the `bsi.properties` file, users can set the DPI for the X and Y values, as bolded below.

    ## 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

Note: By default, the X and Y values are commented out; uncomment these lines to set the DPI.

## Expere database enhancement

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

We had previously introduced a new JavaScript caching object that works with Expere file system servers; however, we did not create a similar database caching object for database-only servers. This resulted in users encountering errors accessing the database through the lack of proper authentication credentials.

A JavaScript object that works with Expere databases is currently in development. This enhancement adds authentication credentials to access the database.

## Invalid PDF syntax issue addressed through cover sheet generation

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

Previously when printing a document PDF package with a cover sheet, users reported an Adobe generation error. It was determined that this issue was caused by an invalid PDF syntax in the cover sheet generation method.

This issue has been resolved; a document PDF package with a cover sheet now prints without errors.

## Barcode options to honor rows, columns, and error correction level

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

It was reported that requests containing `<Error Correction/>`, `<Rows/>`, and `<Columns/>` element values, other than the default, were not honored.

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

Note: Only one of the `<Rows/>` and `<Columns/>` values is honored. If providing both, then the `<Rows/>` value is used, and the `<Columns/>` value is calculated by iText.

For example, in the following `<Barcode/>` configuration: The “`<Rows>10</Rows>`” is used, and the “`<Columns>5</Columns>`” is ignored.

    <exp:AncillaryOutput> <exp:AncillaryOutputOption> <exp:OutputType>Barcode</exp:OutputType> <exp:Barcode> <Type>barcode2D</Type> <UseCoverPage>True</UseCoverPage> <Pattern>577+BMHPF000000000024456+%BRCD%</Pattern> <Barcode2DConfigurationOptions> <ErrorCorrectionLevel>8</ErrorCorrectionLevel> <Columns>5</Columns> <Rows>10</Rows> </Barcode2DConfigurationOptions> </exp:Barcode> </exp:AncillaryOutputOption> </exp:AncillaryOutput>

## Script font enhancements

- Type: Enhancement
- Reference: PBI 405248
- Compliance Impact: This enhancement is not a compliance or regulatory issue.
- Documentation: No document impact.

Expere can now print a desired party name in the signature field with a script font type, Pinyon Script. The new script font is embedded into the .PDF document. Additionally, we have added the font to the `fonts.xsl` file to indicate that we now support Pinyon Script.

Note: No change was implemented to functionality that places a printed name under the signature line.

## PDFMerge updated to use the latest version of iText

- Type: Enhancement
- Reference: PBI 406306
- Compliance Impact: This enhancement is not a compliance or regulatory issue.
- Documentation: No document impact.

As a part of Discrete Party enhancements, we have updated to iText 7 to work with Merged PDF functionality. This enhancement will also allow support of merged PDF with fillable fields and eSignatures in a future release.

See DiscretePartyID for more information on using the `<DiscretePartyID/>` element.

## DiscretePartyID elements added to GetGenerateResponse

- Reference: PBI 405439/405760
- Compliance Impact: This enhancement is not a compliance or regulatory issue.
- Documentation: DocInstance, DiscretePartyIDs

The `<DiscretePartyID/>` element is now available in the Expere Document Services WSDL in the `DocInstance` complex type. It is a sibling to the `<InstanceDisplayName/>` element and a child element of `<DocInstance/>`.

    <DiscretePartyIDs> -
     <DiscretePartyID>x</DiscretePartyID>
     <DiscretePartyID>x</DiscretePartyID>
    </DiscretePartyIDs>

## Generate API enhanced for BRCD values

- Type: Defect Correction
- Reference: PBI 393786
- Compliance Impacts: This defect correction is not a compliance or regulatory issue.
- Documentation: No document impact.

It was discovered that .PKG rules were not identified in the Generate API; this resulted in packages having incorrect barcode values. For example: If I have PKG.ABC that has rules to print a value for the BRCD (25 for example), and PKG.XYZ has rules to print a BRCD value of 136, the Generate call applies the first BRCD value vs the PKG identified in the request.

The Generate API ignored the .PKG entered and only applied the data to the documents identified in the request.

The Generate now applies the PKG information to the call when BRCD values apply and subsequently ignore the AutoSelection rules as the documents are pre-identified.

## Expere Engine: ability to clear javascript cache

- Type: Enhancement
- Reference: PBI 401420
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Documentation: No document impact.

The Expere IE Cache Manager now allows users to reset the Javascript cache, which stores Javascript files the cache to improve performance.

## DocViewer release notes available in Expere Engine and Tools Change Log webhelp

Users can now access the DocViewer release notes ONLINE here.

The effective date for all products within the scope of this document for this release is . This release utilizes Expere Engine version 2016.2.0.

## Expere Engine: continued enhancement of eSignatureAndFieldSupport and SignaturePointSet elements

- Type: New Feature
- Reference: PBI 393921
- Compliance Impacts: This new feature is not a compliance or regulatory issue.
- Documentation: eSignature feature overview, Using eSignature and Acroform fields

Recently, we had implemented `SignaturePointSet` and `eSignatureAndFieldSupport` element changes in PBI's 382028 / 392582. With this continued focus we have implemented the following flags for the `eSignatureAndFieldSupport` element to return X/Y coordinates:

- eSignatureCoordinatesOnly - if set to "true," eSignature fields are suppressed on the form and X/Y coordinates are returned.
- NonSignatureFieldCoordinatesOnly - if set to "true," other Non-Signatures fillable fields (textboxes and checkboxes) are suppressed on the form and X/Y coordinates are returned.

For more information, see the eSignature feature overview section on the Using eSignature and Acroform fields page.

## Expere Engine: document generation enhanced

- Type: Defect correction
- Reference: PBI 395280
- Compliance Impacts: This defect correction is not a compliance or regulatory issue.
- Documentation: No document impact.

Previously, users reported slow performance and time out issues when generating documents. These issues occurred with custom organizations where images existed at a parent level.

When a missing image existed: the system scanned the entire organization tree instead of the requested hierarchy level and incrementally scanning the levels above the original level.

This issue has been resolved; we have addressed the issue above through code changes that have replaced the previous method.

## Expere Engine: SignaturePointSet and eSignatureAndFieldSupport element changes

- Type: New feature
- Reference: PBI 382028 / 392582
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Documentation: No document impact.

In an effort to support returning XY coordinates for all fillable fields we have begun the development work. The first step in supporting this feature is creating a new element (eSignatureAndFieldSupport).

## Java 8 and Saxon upgrade: DB and File System script process available

- Type: Enhancement
- Reference: PBI 376921
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Docmentation: Installation instructions; Powershell and SQL scripts available on your media release

Recently, Java 8, Saxon, and stylesheet upgrades have been implemented; with these upgrades, users must run a script to remove duplicate imports for the database and file system. The scripts are available on your release media at:

See Important update regarding Java 8 and Saxon upgrade: DB and File System script process for detailed information.

## .NET Runtime Required Installation Error resolved

- Type: Defect Correction
- Reference: PBI 380115
- Compliance Impacts: This defect correction is not a compliance or regulatory issue.
- Documentation: Expere System Requirements Guide

It was reported that when installing Expere Engine 2015.3.0.1355 on Windows Server 2012 R2, a .NET Runtime Required error appeared stating that .NET 4.0 was required. However, Windows Server 2012 includes .NET 4.5.1.

Users were instructed to either click OK on the error message or create the following folder: `C:\Windows\Microsoft.NET\Framework\v4.0.30319`, then remove the folder after completing the installation.

This issue has been addressed; we have removed the verification that checks the .NET version. Users can now complete the Expere Engine installation without seeing this error message or performing the workaround above.

## Expere Engine: Barcode cover sheet enhancement

- Type: Defect Correction and Enhancement
- Reference: PBI 378815
- Compliance Impacts: This defect correction/enhancement is not a compliance or regulatory issue.
- Documentation: No document impact.

When utilizing UseCoverPage with the Ancillary Barcode functionality, data within the Instance Display Name elements would overflow off the cover sheet when too long.

Note: Barcode cover sheets are added for TRID documents and static documents without space for barcodes.

This behavior has been enhanced. The Instance Display Name now wraps on the cover sheet. The following text was added to the cover sheet so recipients of the documents know to return the cover sheet with the document:

- “Please include the cover sheet with the associated document for proper processing, when document return is requested.”

## Expere Engine: Endpoint URL issue resolved

- Type: Defect Correction
- Reference: PBI 392807
- Compliance Impacts: This defect correction is not a compliance or regulatory issue.
- Documentation: No document impact.

When viewing the endpoint URL (Common/WSEndpoint) with NO transaction data, it was expected that Expere would return the results of the GetServiceInfo call; however, the SAXParser threw an exception due to the absence of data. This resulted in the GetServiceInfo call not occurring.

With the Expere 2016.1.3 hotfix, Expere now successfully returns the results of the GetService Info call when the endpoint is viewed with no transaction data.

## Expere Engine: Cash to Close calculated values provided

- Type: Enhancement
- Reference: PBI 385920 / 387587
- Compliance Impacts: This enhancement is a compliance or regulatory issue.
- Documentation: No document impact.
- User Impact: Users who rely on Wolters Kluwer Financial Services for computing totals under “Calculating Cash To Close” on the Loan Estimate are impacted. (“Txn/IntegratedDisclosuresUseExpereComputationsInd” schema point set to “True”.) Those values must be parsed and stored by the user; the stored values must be provided in the Expere transaction when calling for the Closing Disclosure to be used on Page 3 for the “Calculating Cash To Close” section.

The `ExpereResponse.xml` file now contains Cash to Close calculated values available in a new `<r:DocCustomDataItems/>` parent element and `<r:DocCustomDataItem/>` child elements. Each of these elements has a `DataItemName` attribute and number for the value.

The new Expere Engine stylesheet, `AddDocCustomDataItem.xsl`, adds these elements as `DocCustomDataItems`.

The new elements exist as children and grandchildren of the `<r:DocDescriptor/>` element. The `<r:DocCustomDataItem/>` elements contain the following `DataItemName` attribute values:

- /Txn/IntegratedDisclosuresLoanEstimateCashToCloseStoredValueAmount
- /Txn/IntegratedDisclosuresLoanEstimateClosingCostsFinancedStoredValueAmount
- /Txn/IntegratedDisclosuresLoanEstimateTotalClosingCostsStoredValueAmount

The following code snippet appears in the `ExpereResponse.xml` file:

    <r:DocDescriptor> <r:DocID>PKGD.LoanEstimate</r:DocID> <r:DocType>Dynamic</r:DocType> <r:DocDisplayName>Loan Estimate</r:DocDisplayName> <r:DocRootEntityName>INS.LoanEstimate</r:DocRootEntityName> <r:DocCustomDataItems> <r:DocCustomDataItem DataItemName="/Txn/IntegratedDisclosuresLoanEstimateTotalClosingCostsStoredValueAmount">34287</r:DocCustomDataItem> <r:DocCustomDataItem DataItemName="/Txn/IntegratedDisclosuresLoanEstimateClosingCostsFinancedStoredValueAmount">-34287</r:DocCustomDataItem> <r:DocCustomDataItem DataItemName="/Txn/IntegratedDisclosuresLoanEstimateCashToCloseStoredValueAmount">107815</r:DocCustomDataItem> </r:DocCustomDataItems> </r:DocDescriptor>

## Expere Engine: Special Character handling enhanced

- Type: Enhancement
- Reference: PBI 374746
- Compliance Impact: This enhancement is not a compliance or regulatory issue
- Documentation: No document impact.

Previously, hosted and non-hosted transactions that called the Expere Engine failed when using certain special characters on static documents.

We have enhanced the Expere Engine to support the following special characters:

Newly Supported:

- 8211: en dash
- 8212: em dash
- 8304: Degree sign
- 9472: Horizontal box

Existing (Previously Supported):

- 8216: left single quotation mark
- 8217: right single quotation mark
- 8220: left double quotation mark
- 8221: right double quotation mark

Note: Dynamic documents already support special characters.

## Foundation for future platform enhancement

- Type: Enhancement
- Reference: PBI 382928
- Compliance Impact: This enhancement is not a compliance or regulatory issue.
- Documentation: No document impact.

We have laid the ground work for a future enhancement to support additional hosted platforms. However, no customer-facing changes currently exist for this change. We will provide additional information as it impacts our users in a future release.

## Expere Engine: Enhanced logging for caching and file system repository

- Type: Enhancement
- Reference: PBI 381741
- Compliance Impact: This enhancement is not a compliance or regulatory issue.
- Documentation: No document impact.

Logging has been enhanced for the caching and file system repository to help track the progress of requests; these enhancements include the RequestID, OrgID, and PackageID. This enhancement is also a result of the changes made in PBI 382041 below.

Note: This change only impacts clients using the File System.

## Expere Engine: Improved File System indexing

- Type: Enhancement
- Reference: PBI 382041
- Compliance Impact: This enhancement is not a compliance or regulatory issue.
- Documentation: No document impact.

Changes were made to the file system repository to make the indexing process more efficient.

Note: This change only impacts clients using the File System.

## Expere Engine: eSignature and AcroForm fields enhanced

- Type: Enhancement
- Reference: PBI 381106
- Compliance Impact: This enhancement is not a compliance or regulatory issue.
- Documentation: Using eSignature and Acroform fields

Previously, users could not enable or disable eSignatures or AcroForm fields for transactions.

Users can now pass eSignature and Acroform values in the AncillaryOutput of a SelectAndGenerate, Generate, and SelectGenerateAndDeliver request. For detailed information on enabling or disabling eSignature or Acroforms, see Using eSignature and Acroform fields.

## Expere Config Tool enhanced

- Type: Enhancement
- Reference: PBI 379682
- Compliance Impact: This enhancement is not a compliance or regulatory issue.
- Documentation: No document impact.

Previously, an issue existed in the Expere Config Tool utility in the 2016.1 release (Important update regarding the Expere Config Tool). Users reported an error when launching the Expere Config Tool utility and as a result, could not update various fields.

The Expere Config Tool has been enhanced, consisting of the following:

- The error that prevented users from launching the Expere Config Tool utility has been resolved; users can now use this tool to update values within the configuration files above.
- The Max Cached Object field has been removed; with our recent upgrade to ehCache 2.10, users no longer need to specify how much cache needs to be allocated for a specific number of objects.

Users can access the updated Expere Config Tool utility here.

## Expere OPPSA package behavior enhanced

- Reference: PBI 195492
- Compliance Impacts: This defect is not a compliance or regulatory issue.
- Documentation: No document impact.

Previously, when a document was removed from base content, OPPSA stopped printing when it encountered the missing document. In some instances, the system stopped printing any remaining documents depending on where the document was located.

This behavior has been enhanced; when an OPPSA package includes a document that has been removed, an error appears stating which document must be removed from the specified package in the OPPSA product.

## Expere upgraded to Java 8 and Saxon

- Reference: PBI 302204
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Documentation: Windows Environment Software Requirements, Java Environment Software Requirements, Expere Authoring Tools.

Summary: Embedded versions of Expere .NET and Requirements Editor now utilize Java 8 and Saxon.

For more information, see the following Expere System Requirements Sections:

- Windows Environment Software Requirements
- Java Environment Software Requirements
- Expere Authoring Tools

## Java and .NET Implementation Guide consolidated

- Type: Enhancement
- Reference: PBI 372968
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Documentation: Expere Implementation Guide

We have recently consolidated the .NET and Java installation procedures to now reside in one webhelp implementation, available here: Expere Implementation Guide.

## Barcode spacing issue resolved

- Type: Defect correction
- Reference: PBI 355603
- Compliance Impacts: This defect is not a compliance or regulatory issue.
- Documentation: No document impact.

Issue: Previously, the Expere Engine reserved space for ancillary barcodes on dynamic documents even though the barcode element was not included in the .REQ file.

Solution: This issue has been resolved; when generating a dynamic document and selecting an ancillary barcode option, the document will no longer reserve space for the barcode if the .REQ file does not contain a barcode element.

This feature requires an Expere Engine update.