2018 Release One (1) Expere Engine and Tools Changelog

Expere Engine Release: 2018 Release One (1)External release date is 4/6/2018. Expere Engine build number is: 2018.1.1.4753 .

New Features

  • See Features page for more information

Enhancements

Defect Corrections

Multiple product support behavior enhanced for OPPSA
  • Type: Enhancement
  • Reference: PBI 495811
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: Expere Developer Guide: Oppsa.
Summary: The following API requests now support an unlimited number of OPPSA products when passed into Expere:
  • SelectAndGenerate
  • Generate
  • CreateTransaction
  • Select
  • SelectAndGenerateTestDocuments

The optional OppsaProductName parameter within Oppsa has been updated to select zero (0) to any number of products.

Implementation Notes: This feature is available in the Expere Engine 2018.1 release.
Ancillary barcodes now honor bottom margins for recordable documents
  • Type: Enhancement
  • Reference: PBI 490310
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: We have adjusted the static placement of the ancillary barcode for documents where margin requirements have been authored. It was determined that certain documents contained barcodes; in some cases, those documents are recordable which causes issues when formally recording with the county or state. This behavior has been enhanced: the ancillary barcode now honors the bottom and side margins so users can record their documents with any county or state. Note the following:
  • If a dynamic .REQ file is authored with bottom, left, or right margins and contains selected justification, the margin is then honored when applying an ancillary barcode.
  • If a dynamic .REQ file is not authored with margin requirements, then the default of .5" margin is honored when applying an ancillary barcode.
Implementation Notes: This feature is available in the 2018.1 release of the Expere Engine. No user action is required.
PrintingOption (Duplexing) element moved to InstanceProperties
Summary: As part of a continued effort to implement the Single State Delivery feature, we have updated the Expere response by moving the <PrintingOption/> element from <DocInstance/> to <InstanceProperties/>. Moving <PrintingOption/> element to <InstanceProperties/> element allows for easier grouping when working with the various elements used for handling state specific printing requirements. The following options are available using the <PrintingOption/> element:
  • Simplex: Inserts blank pages after every page of the document
  • DuplexLong or DuplexShort: analyzes the number of pages; if page total is Odd, blank page inserted at end of document
  • NotSpecified: blank pages not applicable; this is the default setting.
Implementation Notes: This feature is available in the 2018.1 Expere Engine release.
Discrete Party logic updated
  • Type: Enhancement
  • Reference: PBI 472915
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: Expere Developer Guide: DiscreteParties and DiscreteParty
Summary: As part of a continued effort to implement the Single State Delivery feature, we have added a new element called <DiscreteParties/>. Within <DiscreteParties/>, <DiscreteParty/> elements include the following new elements:
  • ID
  • Name
  • BusinessName
  • AddressLine1
  • AddressLine2
  • City
  • State
  • ZipCode
  • CountryCode
  • MailingMethod

This allows those users implementing WK E-Sign or other print fulfillment services to track mailings using additional data.

Note: Additionally, Expere will continue to accept the <DiscretePartyID/> element when authored on content.
Technical Notes: Sample request below:
<r:DocInstance DocIDRef="PKGD.Preforeclosure">
            <r:DocData>...</r:DocData>
            <r:InstanceDisplayName>Document A - John Doe</r:InstanceDisplayName>
            <r:InstanceFileName>Document A - John Doe.pdf</r:InstanceFileName>
            <r:InstanceFormattingMetadata/>
            <r:InstanceSequence>999</r:InstanceSequence>
            <r:InstancePageCount>2</r:InstancePageCount>
            <r:InstanceRecordableFlag>false</r:InstanceRecordableFlag>
            <r:InstancePageSize>Letter</r:InstancePageSize>
            <r:DocFormat>PDF</r:DocFormat>
            <r:DiscretePartyIDs>
		<r:DiscretePartyID>1425</r:DiscretePartyID>
	    </r:DiscretePartyIDs>
            <r:DiscreteParties>
              <r:DiscreteParty>
                <r:ID>1425</r:ID>
                <r:Name>John Doe</r:Name>
                <r:BusinessName />
                <r:AddressLine1>12345 Main St.</r:AddressLine1>
                <r:AddressLine2></r:AddressLine2>
                <r:City>Anywhere</r:City>
                <r:State>MN</r:State>
                <r:ZipCode>12345</r:ZipCode>
                <r:CountryCode>USA</r:CountryCode>
                <r:MailingMethod>First Class</r:MailingMethod>
              </r:DiscreteParty>
            </r:DiscreteParties>
          </r:DocInstance>
Implementation Notes: This feature is available in the 2018.1 Expere Engine release.
Expere Testing System: FileSystem repository supported
  • Type: Enhancement
  • Reference: PBI 485148
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: Expere Testing System User Guide
Summary: In an effort to allow FileSyetem testing through the Expere Testing System we have updated the API calls for AssembleDocumentRequest, AssempleDocumentSet, and AutoSelectionRequest, to no longer require a Database. As a result, the Expere Testing System now uses GenerateRequest, SelectRequest, and SelectandGenerateRequest API calls when working with Autoselection & Assembly, Autoselection, and Assembly. The details behind what API call is used for each is outlined below.

The following Testing System menu options have been updated:

  • Autoselection & Assembly now uses Select for autoselection and Generate for assembling the documents. However, when an OPPSA organization is provided, AutoSelectRequest is used for autoselection, and AssembleDocumentsRequest is used for assembly.
  • Autoselection now uses SelectRequest but will continue using AutoSelectRequest when an OPPSA organization is provided. Additionally, we have removed the option to receive results in DocList or XML format.
  • Create Document Group has been removed from the main menu.
  • Assembly now uses GenerateRequest but will continue using AssembleDocumentsRequest when an OPPSA organization is provided. Additionally, Assembly Options for SMART Doc has been removed.
  • Multi Assembly has been removed from the main menu.
Implementation Notes: This enhancement is available in the 2018.1 Expere Engine release. For detailed information, see the Expere Testing System user guide.
FillableFieldSet order behavior modified
  • Type: Defect
  • Reference: PBI 483243
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: An issue had been identified with Expere .NET when validating the element order of FillableFieldSet and PageSize in the Expere Response. Specifically, the Java version of Expere, as well as schema validation, expects PageSize to be before FillableFieldSet. Where Expere .NET had the opposite order, with FillableFieldSet before PageSize.
Solution: For Expere .NET, the Packet.cs has been updated to return the elements in the same order as it does for Expere Java. As a result, you will see an update to the Expere response (.NET only) with PageSize first, then FillableFieldSet.
Implementation Notes: This defect correction is available in the 2018.1 Expere Engine release.
PDFMerge fillable fields behavior modified
  • Type: Defect
  • Reference: PBI 483572
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: Previously in a request containing PDFMerge with eSignatureCoordindatesOnly set to "true," the resulting PDF document displayed the corresponding fields as fillable. This was incorrect behavior.
Solution: This issue has been resolved; PDFMerge with eSignatureCoordindatesOnly set to "true" does not produce fillable fields on the resulting PDF document.
Implementation Notes: This feature is available in the 2018.1 Expere Engine release.
Generation behavior modified for multiple instances of same document
  • Type: Enhancement
  • Reference: PBI 484981
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: When a request is made to Expere with multiple rule sources in a package, currently Expere will generate the duplicate documents multiple times for each rule source. This is due to Expere's behavior or requiring that PKGD files from different packages be named differently. To mitigate this issue, we have modified Expere's behavior whereby, a Select or SelectAndGenerate request will generate a document only once, even if the request has packages that contain multiple rule sources.
Implementation Notes: This feature is available in the 2018.1 Expere Engine release.
Testing System installation section updated in Expere Implementation Guide
Summary: We have updated the Testing System installation section in the Expere Implementation Guide to reflect the following changes:
  • Prerequisites: we have modified a reference to editing the ExpereTestingSystem.properties file; this property file can be edited using a plain text editor.
  • Installation with Apache Tomcat: we had previously referenced Apache Tomcat version 5.5; users are not restricted to a specific version.
  • Installation with Wildfly: we have added an example of an Expere Endpoint to step 4.
  • Installation with WebSphere: we have changed this section to reflect that WebSphere users will now install the Testing System using the ExpereTestingSystem.war file. Previously, users installed the Testing System using an .ear file.
Implementation Notes: This feature is available in the 2018.1 Expere Engine release.
New build content provided for use with Linux and AIX on file system
Issue: We identified an issue where users of the File System repository on UNIX-based systems received a ‘FileNotFound’ exception when trying to generate documents. This was a result of the content.manifest file being created in a format which Linux and AIX could not read. To correct this issue changes were made to Expere, as well as the content builder.
Solution: Expere can now use the same content.manifest file for File System or Database (requiring minor edits to the BSI.Properties for File System users), as a result of the changes made to the content builder.
Implementation Notes: This defect correction is available in the 2018.1 Expere Engine release. As stated above, File System users will need to uncomment specific lines on the BSI.Properties file to take advantage of this change and no longer receive the ‘FileNotFound’ exception. This change will also require content to be rebuilt, (using the updated content builder) and deployed. For detailed information, see Setting up BSI.Properties for File System.

Upgrade to iText 5.5.12
  • Type: Enhancement
  • Reference: PBI 480070
  • Compliance Impacts: This item is/is not a compliance or regulatory issue.
  • Documentation Impacts: Expere Developer Guide: Sequencing
Summary: Previously, Expere did not merge PDF's correctly when a set of documents contained more than one fillable field with the same name. For example, if you merged two PDF's that had a field named the same on each of those PDF's, Expere did not preserve both fields. Expere will now preserve both fields and link them together; thus, if you change the value of one instance of the field the other instances are automatically updated. Upgrading from iText 5.5.9 to 5.5.12 resolves this issue. Additionally, we will no longer sequence IssuedDatefields when using Merged PDF ancillary output options; our Expere Engine Developer Guide contains detailed information on sequencing.
Implementation Notes: This feature is available in the 2018.1 Expere Engine release.
InstanceDisplayName and InstanceFileName logic updated for safe truncation
Summary: The bsi.properties file has been updated to allow truncation of the <InstanceDisplayName/> and <InstanceFileName/> element values when either exceed 250 characters. This ensures that errors will not occur when field name lengths exceed what Microsoft Windows supports. As a result of this change, the first 21 characters appeared following by a "_" and 32 character hash value.
Technical Notes: Sample <InstanceFileName/> value here:
<r:InstanceFileName>fileNameTempfileNameTempfileNameTempfileNameTempfileName
TempfileNameTempfileNameTempfileNameTempfileNameTempfileNameTempfileNameTempfileName
TempfileNameTempfileNameTempfileNameTempfileNameTempfileNameTempfileNameTempfi
_956DF38376C34F9BA6186A4D87113D16.pdf</r:InstanceFileName>
Implementation Notes: See Expere Implementation Guide: Truncating InstanceDisplayName and InstanceFileName for detailed information. This feature is available in the 2018.1 Expere Engine release.
Components updated to newer versions
  • Type: Enhancement
  • Reference: PBI 466863
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: Due to an application assessment, we determined Jaxen 1.1.3 in the ExpereIEServices.ear folder on the release media required updating.
Implementation Notes: This feature is available in the 2018.1 release of the Expere Engine.
Inline package functionality enhanced to use Expere autoselection with Select API requests
  • Type: Enhancement
  • Reference: PBI 478455
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: Previously when a Select API requests contained an inline package that was submitted to Expere, the Select request did not adhere to Expere autoselection rules.

This behavior has been modified; all Select API calls that contain inline package requests now use Expere autoselection rules when determining if a document can be generated with the provided transaction data.

Implementation Notes: This feature is available in the 2018.1 Expere Engine release.
Inline Packages now support metadata
Summary: The <DocCustomDataItem/> element in <InlinePackageDoc/> contains the metadata used for an inline package. The Custom Data Items defined in the .REQ file will no longer be honored with an inline package request.
Technical Notes: Sample request with new <DocCustomDataItem/> element:
<InlinePackageDocs>
			<InlinePackageDoc>
				<PackageDocName>PKGD.NoticeRegardingInaccurateInformation</PackageDocName>
				<SourcePackageName>PKG.DepositAccountOpening</SourcePackageName>
				<DocCustomDataItems>
					<DocCustomDataItem DataItemName="Data Item Name1">Data Item Value 1</DocCustomDataItem>
					<DocCustomDataItem DataItemName="Data Item Name2">Data Item Value 2</DocCustomDataItem>
				</DocCustomDataItems>
			</InlinePackageDoc>
			<InlinePackageDoc>
				<PackageDocName>PKGD.TermsAndConditions</PackageDocName>
				<SourcePackageName>PKG.DepositAccountOpening</SourcePackageName>
			</InlinePackageDoc>
		</InlinePackageDocs>
Implementation Notes: This feature is available in the 2018.1 Expere Engine release.
Acroform fillable fields enhancement
  • Type: Enhancement
  • Reference: PBI 469845
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact.
Summary: Previously if a fillable text field passed from a custom .REQ file contained an underline, it would not print on the corresponding document when XY coordinates were requested.

We have enhanced the acroform field logic to accept and print underlines when XY coordinates are requested.
Implementation Notes: This feature is available in the 2018.1 Expere Engine release.
Wildfly Linux deployment issue resolved
  • Type: Defect
  • Reference: PBI 442789
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: Previously, deploying Wildfly on Linux platforms using File System content resulted in a FileNotFound exception when attempting to read the content.manifest file. This issue occurred due to an incorrect path separator.
Solution: This issue has been resolved; Wildfly now operates normally on Linux using File System content.
Implementation Notes: This defect correction is available in the 2018.1 Expere Engine release.
Archived Changelog topics enhanced
Summary: We have enhanced the Expere Engine and Tools Archived Changelog Overview and Important Notifications section so that each set of 2016 changelogs now reside on a separate page.
Implementation Notes: This enhancement is available in the 2018.1 Expere Engine release.
InlinePackage behavior enhancement
  • Type: Enhancement
  • Reference: PBI 457943
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: Previously, a transaction containing an inline package was failed if the request referenced a package that did not exist. This behavior has been revised whereby the transaction will continue to be processed even if an inline package references a package that does not exist. Expere will skip processing the package that is absent and log a warning pertaining to the transaction with the name of the package. Furthermore, if all packages referenced in the request do not exist, Expere will dispatch a failed error back to the calling entity.
Technical Notes: Sample code below: 
<c:InlinePackageDocs>
		<c:InlinePackageDoc>
		   <c:PackageDocName>PKGD.AccountAgreementModificationWI</c:PackageDocName>
		   <c:SourcePackageName>PKG.DepositAccountOpening</c:SourcePackageName>
		</c:InlinePackageDoc>
</c:InlinePackageDocs
Implementation Notes: This feature is available in the 2018.1 Expere Engine release.
Inline package functionality enhanced to support Expere autoselection
  • Type: Enhancement
  • Reference: PBI 467065
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact.
Summary: Previously when a document was requested through the <InlinePackageDoc/> element, it disregarded autoselection but still appeared in the <PackageDocName/> element as part of the package document set. It was determined that in some cases, a document was specified in the <InlinePackageDoc/> element that caused Expere to generate the document despite the lack of transaction data needed to fully generate the document.

Now, all inline package requests that reference documents utilize Expere autoselection rules when determining if the document could be generated with the provided transaction data.
Technical Notes: Sample request: 
<c:InlinePackageDocs>
                    <c:InlinePackageDoc>
                        <c:PackageDocName>PKGD.BorrowersAcknowledgment</c:PackageDocName>
                        <c:SourcePackageName>PKG.MockContent</c:SourcePackageName>
                    </c:InlinePackageDoc>
</c:InlinePackageDocs>
Sample response:
<r:PackageDocs>
	      <r:PackageDoc PackageDocID="PKGD.AuthorizationDocumentAccounts_Copy">
		  <r:DocDescriptor>
		     <r:DocID>PKGD.BorrowersAcknowledgment</r:DocID>
		     <r:DocType>Dynamic</r:DocType>
		     <r:DocDisplayName>Borrowers Acknowledgment</r:DocDisplayName>
		     <r:DocRootEntityName>INS.BorrowersAcknowledgment</r:DocRootEntityName>
		  </r:DocDescriptor>
		  <r:DocWorkOrder>
		     <r:DocPrepare>true</r:DocPrepare>
		     <r:DocAutoselected>true</r:DocAutoselected>
		     <r:DocSuggested>false</r:DocSuggested>
		     <r:DocFormat>PDF</r:DocFormat>
		     <r:DocStyle>WKFS_StyleGuide</r:DocStyle>
		  </r:DocWorkOrder>
		</r:PackageDoc>
</r:PackageDocs>
Implementation Notes: This feature requires a 2018.1 Expere Engine update.
Documentation feedback feature available in Expere Engine webhelp
  • Type: Enhancement
  • Reference: PBI 469893
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact.
Summary: To gather your feedback, we have implemented documentation feedback forms on our Expere Engine webhelp. The feedback you provide will go directly to our SupportLine staff and will allow us to consider your suggestions to improve our documentation.
Implementation Notes: This feature is available on every page of your Expere Engine changelog webhelp, Developer's Guide, Implementation Guide, and Testing System User Guide.
Barcode enhancement: additional location options
  • Type: Enhancement
  • Reference: PBI 443543
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: Expere Developer Guide: 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 2018.1 Expere Engine update. For more information, see Barcode.
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 2018.1 Expere Engine update. See Sequencing: WKES email address sequencing and naming behavior for more information.