# Expere Document Services Change Log Entries

The effective date for all products within the scope of this document for this release is August 11 for the CT environment and August 18 for the Production environment.

## Expere Document Service Incomplete transaction enhanced

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

It was reported that documents were not being returned for certain transactions in Expere Document Services. While Document Generation Services generated the documents, Expere Document Services displayed the status of the transaction as Incomplete. We have determined the timing of certain callbacks to Expere Document Services caused inaccurate transaction statuses.

This issue has been addressed; statuses are now returned as Complete for successful transactions.

## Expere Document Services logging enhanced for improved consistency

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

The Expere Document Services log files have been updated for consistency with Expere Document Services and allows for better parsing by our logging solutions.

The following enhancements have been implemented:

- RequestID has been eliminated and is now referred to as EDS ID.
- The DGS ID, EDS ID, User ID, and External ID fields are contained with brackets (for example: "[ ]"). For more information about External ID: see Generate.

The effective date for all products within the scope of this document for this release is July 14 for the CT environment and July 21 for the Production environment.

## eSignature and field support behavior enhanced

- Type: Enhancement
- Reference: PBI 392598
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Documentation: Using eSignature and Acroform fields, Select Generate and Deliver, Select And Generate, Generate.

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). This element will only pass XY coordinates for esignatures at this time. In a future release it will control XY coordinates for all fillable fields.

For more information, see the following:

- Using eSignature and Acroform fields
- Select Generate and Deliver
- Select And Generate
- Generate

## SignaturePointSet now populated in Response file

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

Previously, the `SignaturePointSet` element was set to "null" rather than contain signature field names and data.

The `SignaturePointSet` element has been enhanced to include the signature field name and data that appear on the form.

    "SignaturePointSet": {
     "Signer": [
     {
     "Id": "Signer",
     "Description": "Borrower, Borrower",
     "SignaturePoints": [
     {
     "IncludeDate": false,
     "PageNumber": 2,
     "PageOrder": "1",
     "Height": 36,
     "Width": 198,
     "SignatureText": "Jane eSignature",
     "XCoordinate": 36,
     "YCoordinate": 650,
     "Type": "Signature",
     "FieldName": "SIG_Borrower_2_Signer_false_1"
     },
     {
     "IncludeDate": false,
     "PageNumber": 2,
     "PageOrder": "1",
     "Height": 36,
     "Width": 50,
     "SignatureText": "Jane eSignature",
     "XCoordinate": 238,
     "YCoordinate": 650,
     "Type": "Date",
     "FieldName": "SIG_Borrower_2_Signer_false_1.eSigDate"
     }
     ]
     }

## GetGenerateResults API error messages enhanced

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

The messages used with the GetGenerateResults API have been updated to provide enhanced details if an error occurs during processing. These error messages now match those included with callbacks.

For example: a message like “Transaction is complete with errors” has been updated to state “No documents were supplied for assembly.” where applicable.

These error messages now match those included with callbacks.

## eSignature and AcroForm fields added

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

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.

The effective date for all products within the scope of this document for this release is June 23 for the CT environment and July 21 for the Production environment.

## Callback logic enhanced

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

Previously, we enhanced Document Generation callbacks for Expere Document Services to include a retry mechanism (PBI 382253); however, it was reported that five (5) retries occurred per request made in the CT environment. This occurred due to every request resulting in an exception on the callback acknowledgement even if an error did not occur.

We have made additional enhancements so that retries do not occur when a callback is successful. Retries now only occur when the thrown exception is “EndpointNotFoundException” or exception message contains words like “Listening” or “Timeout."

## PackageDocs now included in Response

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

After submitting a transaction in Expere Document Services, users will now receive a response file containing the Package Documents, which contain <DocCustomData/> elements in the packages.

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

Expere Response XML values:

    <r:DocCustomDataItems>
    <r:DocCustomDataItem DataItemName="">34453</r:DocCustomDataItem>
    <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>

The effective date for all products within the scope of this document for this release is June 9 for the CT environment and July 21 for the Production environment.

## PassthroughIdentifier update on Delivery-only request

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

Previously, when the Passthroughidentifier was not being passed on a Deliver request, Expere Document Services could not successfully return a Deliver callback status.

This issue has been corrected; now if the Passthroughidentifier is not provided in a Deliver request it will use the Passthroughidentifier from the SelectAndGenerate request of that transaction to complete the Deliver callback.

## Document generation callback retries added

- Reference: PBI 382253
- Compliance Impacts: This new feature is not a compliance or regulatory impact.
- Documentation: GenerateResponse, SelectAndGenerateResponse, SelectGenerateDeliverResponse

Document Generation callbacks have been enhanced for Expere Document Services; callback functionality includes a retry mechanism.

Expere Document Services reattempts a document generation callback in the following intervals:

- One (1) second
- Two (2) seconds
- Four (4) seconds
- Eight (8) seconds
- Sixteen (16) seconds

## First Page functionality available

- Reference: PBI 370563; original PBI 364319
- Compliance Impact: This enhancement is not a compliance or regulatory issue.
- Documentation: Using First Page Only Barcodes

In a previous release, we had released First Page Barcode functionality, albeit in limited functionality.

First Page Barcode is now fully functional in Expere Document Services for SelectGenerateAndDeliver, SelectAndGenerate and Generate methods.

The effective date for all products within the scope of this document for this release is May 12 for the CT environment and May 19 for the Production environment.

## Passthrough Identifier added to Deliver API

- Reference: PBI 380060
- Compliance Impacts: This new feature is not a compliance or regulatory issue.
- Documentation: DeliverIn

A new Passthrough Identifier parameter has been added to the Deliver API. The PassThroughIdentifier is an optional-user generated parameter that eliminates duplicate entries in Expere Document Services.

For more information, see DeliverIn.

## Scheduler Service enhanced to function with SQL

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

After the Expere Document Services database was migrated from Raven to SQL,the Scheduler Service has been enhanced to remove transactions older than seven days from Expere Document Services. Users will no longer be able to retrieve these transactions.

## ListDocuments API added

- Reference: PBI 373191
- Compliance Impacts: This new feature is not a compliance or regulatory issue.
- Documentation: ListDocuments.

The Expere ListDocuments API is now available through Expere Document Services.

The ListDocuments option calls a base or custom package of documents defined by the customer. The list of documents in the base or custom package is displayed for the end user to select and use for a given transaction.

The effective date for all products within the scope of this document for this release is April 14 for the CT environment and April 21 for the Production environment.
There were no external facing changes for this release
The effective date for all products within the scope of this document for this release is March 10 for the CT environment and March 17 for the Production environment.

## Callback implemented for SelectGenerateAndDeliver

- Reference: PBI 367132
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Documentation: SelectGenerateDeliver Callback Overview

Previously, the SelectGenerateAndDeliver API call only utilized the delivery callback service. As a result, if an error occurred when generating the documents in Document Generation Services, no callback was sent, and the integrator did not know if the transaction was successful.

Callback behavior has been enhanced; users are now alerted if an error occurred when generating documents in Document Generation Services.

See SelectGenerateDeliver Callback Overview for more information.

## First page only barcode option now available

Note: This feature is NOT fully functional and will be available in a future release.

- Reference: PBI 364319
- Compliance Impacts: This new feature is not a compliance or regulatory issue.
- Documentation: Using First Page Only Barcodes.

Summary: Users can now apply a barcode to the first or only page of a document. For detailed information on using this feature , see the Using First Page Only Barcodes webhelp page.

## Callback message enhancement

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

When passing an invalid URI, a URI for a nonexistant package, or request with an error in DGS or Expere, the callback indicates the following:

- The request resulted in an error
- Error description
- Error details in JSON output

## Delivery ID enhanced

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

Previously, the Delivery ID was not returned when using the Select and Generate and Delivery API's separately; as a result, users could not access the delivered image.

This issue has been addressed; the Delivery ID is returned when submitting a transaction with the Select and Generate and Delivery API's.

The effective date for all products within the scope of this document for this release is February 4 for the CT environment and February 18 for the Production environment.

## New API added to Expere Document Services

- Reference: PBI 358499
- Compliance Impacts: This new feature is not a compliance or regulatory impact.
- Documentation: GetRequestStatus

A new API, GetRequestStatus, has been added that allows you to request data on a single transaction or a group of transactions. The request can be based on one of the criteria or a combination of the criteria below:

- State
- API Call
- Delivery Status
- Delivery Date
- Created Date

For detailed integration information, see GetRequestStatus.

## PassThroughIdentifier enhanced

- Reference: PBI 357647
- Compliance Impacts: This enhancement is not a compliance or regulatory impact.
- Documentation: GenerateIn; SelectAndGenerateIn; SelectGenerateDeliverIn.

Previously, the Expere Document Services PassThroughIdentifier parameter was not case sensitive; it would not distinguish between a capital or lower case letter.

Due to customer requirements, the Expere Document Services database has been updated so that the PassThroughIdentifier now distinguishes capital and lower case letters.

See GenerateIn; SelectAndGenerateIn; SelectGenerateDeliverIn for more information on using the PassThroughIdentifier parameter.

The effective date for all products within the scope of this document for this release is November 23 for the CT environment and December 8 for the Production environment.

## Mailing Status times enhanced

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

Previously, our reporting application displayed the Created timestamp in Central time and other mailing status timestamps in UTC time.

This issue has been resolved; timestamps for all mailing histories now appear in Central time.

## Expere Document Services Now Using SQL

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

The Expere Document Services database has been converted from Raven to SQL. Note that there will be no change to the Transaction ID itself.

## Loan Number added to Expere Document Services API call

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

The loan number sent through the Deliver and Select, Generate, and Deliver API calls now appears in the Fulfillment Manager if included in the transaction data.

## Request reattempt enhanced

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

Request, or callback, functionality has been enhanced in Expere Document Services to automatically reattempt a failed request so the time to obtain a successful transaction is reduced.

Expere Document Services now reattempts a request in the following intervals:

- One (1) second
- Two (2) seconds
- Four (4) seconds
- Eight (8) seconds
- Sixteen (16) seconds

The effective date for all products within the scope of this document for this release is October 8 for the CT environment and October 14 for the Production.

## Duplicate packages functionality enhanced

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

Previously, duplicate packages were routed to Print Fulfillment. If the transaction ID was not returned immediately, another Select Generate & Deliver call was initiated with the same PassThroughIdentifier.

A table has been added to the SQL database that saves the transaction ID and PassThroughIdentifier immediately. Expere Document Services analyzes this table to determine if the PassThroughIdentifier already exists.

If the PassThroughIdentifier exists, the existing transaction ID is returned to the user details in the log file that a response was sent to the user. If the PassThroughIdentifier does not exist, a new transaction is created and a record saved in the Expere Document Services Raven and SQL table.

The new SQL contains the EDS Request Details, Date/Time Created, and RavenTransactionID (EDS Transaction ID).