# Archived Change Log Entries

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

## Callback information enhanced in Expere Document Services webhelp

- Reference: PBI 409886
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Documentation: Callback Overview, CallbackHandler, DeliveryResponse

We have enhanced the information around Callbacks in the Expere Document Services webhelp. For more information, see Callback Overview, CallbackHandler, and DeliveryResponse.

## Sequence fields functionality incorporated with MergePDF

- Type: Enhancement
- Reference: PBI 411604
- 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 Document Generation Services 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>

## InstanceFileName now supported in Expere Document Services request

- Reference: PBI 415025
- Compliance Impact: This enhancement is not a compliance or regulatory issue.
- Documentation: Attachment

Users may now use the `<InstanceFileName/>` element in the Attachment data type in SelectGenerateAndDeliver, SelectAndGenerate, and Generate requests. Previously, this element could not be passed in a request. Including the `<InstanceFileName/>` element in the request will allow the specified name to be returned in the response.

For example:

    <DisplayName>Good Faith Estimate (GFE) - VMP116F.pdf</DisplayName>
    <InstanceFileName>b11c853cb1c1431c9fc0028feaa014b7</InstanceFileName>

If the request does include a value for `<InstanceFileName/>`, Expere Document Services will return a "default" value.

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

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

- Reference: PBI 410080 / 410688
- Compliance Impacts: This new feature is not a compliance or regulatory issue.
- Documentation: Signer

We have added a new `<SignerEmail/>` element to the `<Signer/>` element.

This element appears in the Expere response file when including the "eSignatureWKES" flag in the initial request. Sample code below:

## Resubmit API now functions with Deliver call

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

The Resubmit API now functions with a Deliver call; in the event of an outage or other unforeseen service interruption, those transactions sent or included in a Deliver call can now be resubmitted without re-initiating the transaction submission process. There is no change to the Expere Document Services WSDL.

Note: Packages in a Mailed status cannot be resubmitted; users will receive a corresponding validation message.

## Insecure Direct Object Reference security finding

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

This security issue has been rectified; we have now implemented an additional permission check when viewing search results.

A critical insecure direct object reference vulnerability was found within Expere Document Services. Nettitude, an independent penetration testing vendor, was able to view sensitive transactional information intended for other users only by altering the accountId paramater in the POST request through the Expere Document Services tool suite.

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

## DiscretePartyIDs element added to GetGenerateResultsResponse

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

The `<DiscretePartyIDs/>` element is now included in the Expere Response to support the Discrete Party Feature. DiscretePartyIDs is a sibling to the `<InstanceDisplayName/>` element and a child element of `<DocInstance/>`.

    <Packet PacketName="Default" PacketFileName="Default.pdf">
     <DocInstances>
     <DocData>
     <base64>JVBERi0xLjQKJeLjz
    GFydHhyZWYKMjUxOTIKJSVFT0YK</base64>
     <text xsi:nil="true"/>
     <xml>
     <NotApplicable/>
     </xml>
     </DocData>
     <InstanceDisplayName>Business Debit Card Agreement - VISA(TM) CheckCard</InstanceDisplayName>
     <InstanceFileName>Default-Business_Debit_Card_Agreement_-_VISA_TM__CheckCard.pdf</InstanceFileName>
     <InstanceFormattingMetadata xsi:nil="true"/>
     <InstancePacketType xsi:nil="true"/>
     <InstancePacketName xsi:nil="true"/>
     <InstanceDocumentRef xsi:nil="true"/>
     <InstanceSequence xsi:nil="true"/>
     <InstanceBarcodeValue xsi:nil="true"/>
     <InstancePageCount xsi:nil="true"/>
     <DocFormat xsi:nil="true"/>
     <Copy xsi:nil="true"/>
     <SignaturePointSet xsi:nil="true"/>
     <DiscretePartyIDs>
     <DiscretePartyID >60593</DiscretePartyID>
     <DiscretePartyID >60594</DiscretePartyID>
     </DiscretePartyIDs>
     </DocInstances>

## PacketFileName and PacketName attributes added to Packet element in response file

- Reference: PBI 405759
- Compliance Impact: This enhancement is not a compliance or regulatory issue.
- Documentation: Packet Data Type

The `<Packet/>` now contains the following attributes:

- `<PacketName/>`
- `<PacketFileName/>`

These attributes are included in the `<Packet/>` element so users can create packets of documents.

## DocInstances now returned individually for merged PDF

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

Previously, Document Generation Services only returned one DocInstance when merging PDF documents. As a result, only one set of elements was returned, rather than multiple sets of elements determined by the number of DocInstances.

Document Generation Services now returns separate DocInstances when the merged PDF is set to "true" in the response file.

For more information, see the following:

- DocInstances
- AncillaryOutputOption
- AncillaryOutputType
- AncillaryOutputTypeEnum

## SelectGenerateAndDeliver merged PDF issue resolved

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

It was reported that documents were not being delivered as a merged PDF when the PDFMerge attribute was present on a SelectGenerateAndDeliver, or SelectAndGenerate followed by a Deliver call.

This issue has been resolved; SelectGenerateAndDeliver, SelectAndGenerate, and Deliver API calls once again deliver merged PDF documents.

The effective date for all products within the scope of this document for this release is November 9 for the CT environment.

## PDFMergeWithDocInstances ancillary output option added

- Reference: PBI 415649
- Compliance Impact: This enhancement is not a compliane or regulatory issue.
- Documentation: Ancillary Outputs (Post-Processing)

We have created a new ancillary output option called PDFMergeWithDocInstances to support returning DocInstances for each document in the package, when merged PDF is desired.

When this new ancillary option is included in the request, the response will include one Base64 merged PDF within the first `<DocInstance/>`. All additional `<DocInstance/>` entries within the response will contain elements that pertain to the specific document(s). For example: `<InstanceDisplayName>`, `<InstanceFileName>`, etc.

    <data:AncillaryOutputOptions>
     <data:OutputType>PdfMergeWithDocInstances</data:OutputType>
     </data:AncillaryOutputOptions>

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

## InstancePageSize now returned in Expere Document Services response file

- Reference: PBI 407720
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Documentation: DocInstance

We now return the `<InstancePageSize/>` element value in the Expere Document Services response file. Users can set the value for the `<InstancePageSize/>` element in the `DocInstance` data type.

Note: By default, the `<InstancePageSize/>` element value is set to "Null."

## DiscretePartyIDs element added to Expere Document Services WSDL

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

The `<DiscretePartyID/>` element is now available in the Document Generation Services WSDL within the complexType `DocInstance`. This change is implemented to support Discrete Borrower functionality, which will be included in a future release

WSDL Enhancement

    <xs:complexType name="DocInstance">
     <xs:sequence>
     ....
     <xs:element minOccurs="1" maxOccurs="1" name="DiscretePartyIDs" type="tns:DiscretePartyIDs"/>
     </xs:sequence>
     <xs:attribute name="DocIDRef" type="xs:string"/>
    </xs:complexType>

## Integrators: DiscretePartyID elements added to GetGenerateResponse

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

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

The `<DiscretePartyID/>` element is part of a future enhancement that will be introduced in a future Expere Document Services release.

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

## Watermark options added

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

The Expere Document Services Tool Suite has been enhanced to include the following watermark options for the Select, Generate, and Deliver, Select and Generate and Generate API's:

- Watermark location:
  - Top
  - Center
  - Bottom
- Rotate checkbox (rotates the Watermark)

For more information, see Select Generate And Deliver, Select and Generate and Generate.

## SelectGenerateDeliver callback issue resolved

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

Previously, callbacks for Delivery service were unsuccessful due to the callback URL and Username not being saved in the request

This issue has been resolved; submitting a SelectGenerateDeliver request with callback now contains the URL and user name in the Request Callback node.

Note: This issue was found in the Customer Test Environment and was never exposed to Production.

## Tool Suite: session timeout behavior modified

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

Previously, users were logged out of the Document Generation Services Tool Suite after 25 minutes, regardless of their activity. The expected behavior is that the Tool Suite only times out after 25 minutes of user inactivity.

The Tool Suite has been enhanced to only time out after 25 minutes of user inactivity.

## Generate recycle event log entry functionality now available

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

Previously, the application pools in the Osprey stack deployments were deleted and recreated during every deployment. Any configuration work performed by the ASM group, such as enabling the flags to generate recycle event log entries for a given application pool or adjusting the timing of recyle events, was deleted.

Now, all "Generate Recycle Event Log Entry" flags are set to "true" for all Osprey stack pools, for all environments. This allows ASM resources to analyze recycling information for a particular application pool.

## Expere Document Service Transaction Validation

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

Previously Expere Document Services allowed Select, Generate, SelectAndGenerate, or SelectGenerateDeliver requests to be passed to Document Generation Services when no transaction data was provided. The user then received a Transaction ID that never generated documents and only provided an error, due to the invalid transaction.

This has been corrected. Now when a request is submitted the transaction data is validated prior to Expere Document Services providing a Transaction ID and sending it on to Document Generation Services. In the future, if the transaction data is not provided in the request, the end user will not receive a Transaction ID and receive an error instead.

## Tool Suite: Get Generate Results issue resolved

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

Previously, users reported that after entering a Transaction ID on the Generate Results page, entering different ID's returned the original result. Expected behavior is that entering a subsequent, unique ID would return the .PDF and .ZIP files specific to that ID.

Now when a user enters the transaction ID and the PDF/zip file is generated, the user cannot re-enter another Transaction ID as the field is disabled until executing a new search. In addition the Check Status Request button is no longer available when the user generates their results with the transaction ID.

## Mapped Diagnostic Context (MDC) values set using logger extension class

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

Previously, Expere Document Services set the MDC values within the classes without calling the AssignRequest method. Rather than call the AssignRequest method, EDS set the MDC values separately.

EDS now calls the AssignRequest method to set MDC values. See example below:

    public static void AssignRequestItems(this ILogger logger, string requestId=null, string externalKey = null,
     string identityName=null)
     {

     log4net.MDC.Set("EDSID", requestId ?? "-");
     log4net.MDC.Set("ExternalID", externalKey ?? "-");
     log4net.MDC.Set("UserID", identityName ?? "-");
     }

     /// <summary>
     ///
     /// </summary>
     /// <param name="logger">Logger instance.</param>
     /// <param name="request">Request object that contains requestId, external key, and identity name infromation.</param>
     public static void AssignRequest(this ILogger logger, EDSRequest request)
     {
     if (request != null)
     logger.AssignRequestItems(request.Id.ToString(), request.PassthroughIdentifier, Thread.CurrentPrincipal.Identity.Name);

     }

The effective date for all products within the scope of this document for this release is August 18 for the CT environment and September 15 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 field Select And Generate, Generate

We have created a new `eSignatureAndFieldSupport` element to support returning XY coordinates for all fillable fields.

Note: XY coordinates for eSignature and fillable fields are not supported with the Merged PDF option.

## 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 Document Generation Services log files have been updated for consistency with Document Generation 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 DGS ID.
- The DGS 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 21 for the CT environment and August 4 for the Production environment.

## 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"
     }
     ]
     }

## Logging enhancement: FATAL level added

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

Previously, all errors in the Document Generation Services log files appeared simply as an ERROR. The log files have now been enhanced to include a new FATAL level whenever an environmental issue prevents execution.
Note: For example: "Expere runtime is unable to connect to the file system."

## Select API issue resolved

- Reference: PBI 392754
- Compliance Impacts: There are no compliance or regulatory issues with this defect correction.
- Documentation: No document impact.

We determined that the recent deployment of the latest AutoMapper caused a resulting issue with the Select API. These issues were discovered in both the Staging and CT environments.

The following error pertaining to the Select API issue appeared in the log file:

    ERROR 2016-06-24 12:46:16,975 DocServices.Services.Import.V2.EDocService - [(null)] [20046] [admin1] [] An exception occurred while processing a GetSelectResults for [20046]
    AutoMapper.AutoMapperMappingException: Missing type map configuration or unsupported mapping.

This issue has been resolved; Select API now works as expected.

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

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 Document Generation 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: SUPPORT Page

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 364255
- Compliance Impact: This enhancement is not a compliance or regulatory issue.
- Documentation: Select And Generate; Generate

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

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

## Expere Document Services upgraded to use AutoMapper 4.2.1

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

The previous version of AutoMapper was not thread-safe and caused problems when multiple threads ran.

AutoMapper 4.2.1 has been optimized to repair thread-related issues, when multiple requests are process simultaneously. Document Generation Services has been updated to use AutoMapper 4.2.1.

For more information, see http://automapper.org/.

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.

## Print Fulfillment Delay option implemented

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

Users can now delay packages routed to Print Fulfillment until the next day. The webconfig file allows users to delay their packages for ERP pickup and is configured by the AccountID.

## ListDocuments API added

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

The Expere ListDocuments API is now available through Document Generation 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. For detailed information on using this feature in the Document Generation Services Tool Suite, see List Documents.

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.

## Retries to Delivery Service Implemented

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

Previously, when a document package was created successfully in Document Generation Services but Expere Document Services failed at the initial attempt to send the package to Fulfillment, the package would never make it to delivery.

To correct this, EDS will now resubmit the package to Fulfillment up to five (5) times when the initial attempt fails. This has been implemented for the Deliver and SelectGenerateAndDeliver APIs.

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.

## GetDeliveredImages issue resolved

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

Previously, the GetDeliveredImages operation did not validate if a user had access to an account with associated images. Subsequently, users could access any images without restrictions.

This behavior has been restricted; users may now only access images in accounts to which they are assigned.

## PassThroughIdentifier added to SUPPORT Page

- Reference: PBI 369732
- Compliance Impacts: This new feature is not a compliance or regulatory issue.
- Documentation: SUPPORT Page

The SUPPORT Page has been enhanced to allow users to search for transactions by PassThrough ID within a single account. For more information, see SUPPORT Page.

## Resubmit Transaction call enhanced

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

Previously when using the Resubmit Transaction call on the SERVICES Page, the original request was sent with five (5) immediate retries resulting in six (6) submissions to Document Generation Services. On a SelectGenerateDeliver call this results in as many as six (6) packages sent to Fulfillment to print and mail.

When using the Resubmit Transaction call on the SERVICES Page, only one successful request is sent to Document Generation Services. If the original submission fails, up to five retries will be attempted until a successful request is made.

## Support Tool: First page only barcode option now available

- Reference: PBI 364255
- Compliance Impacts: This new feature is not a compliance or regulatory issue.
- Documentation: Select And Generate and Generate.

Summary: Users can now apply a barcode to the first or only page of a document. For detailed information on using this feature within the Document Generation Services Tool Suite, see the Select And Generate and Generate webhelp sections within the SERVICE Page.

## SUPPORT Page account and transaction issue resolved

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

Previously, certain accounts and transactions on the SUPPORT Page were not visible to users with SupportLine permissions; Expere Document Services only displayed accounts licensed for Document Generation Services.

This issue has been resolved; users with SupportLine permission can now view all licensed accounts and transactions on the SUPPORT Page.

## Support Tool: 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.

## Document Generation Service production logs enhanced

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

It was reported that the following error inadvertently appeared in the Document Generation Services (DGS) production log:

- "GetRequestByRequestId Failed System.Exception: Request ID: test does not exist."

This error message occurred when the Expere Document Services health check page inadvertedly called Document Generation Services.

The EDS health check has been enhanced and now does not call DGS. Any DGS CT or Production errors appear during the DGS health check.

## Select Synchronous call enhanced

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

Previously when using the Select Synchronous call, the original request was sent with five (5) immediate retries resulting in six (6) submissions to Document Generation Services.

When using the Select Synchronous call, only one successful request is sent to DGS. If the original submission fails, up to five retries will be attempted until a successful request is made.

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.

## Watermark Null Location enhanced

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

Previously, it was reported that submitted watermarks with a null location and rotation resulted in an error in Expere Document Services.

Requests submitted without watermark location or rotation values now default to a value of "None" and process normally.

## New SQL Table Indexes

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

The SQL database now contains indexes for increased search functionality. The database now contains the following parameters:

- AccountID
- DGS ID
- State
- Time/Date Stamps

## AffidavitType enhanced

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

Previously when an API request was submitted and no AffidavitType element passed in the call, the first available enumerator, "Unnotarized," was the default option. This behavior was not correct, as affidavits are not required.

This issue has been addressed; when an API request does not include the AffidavitType element, the type is now set to "None."

## Callback delete issue resolved

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

Previously when attempting to delete callback information for a particular account in the Expere Document Services Tool Suite, the information was not deleted.

This issue has been resolved; callback information is now permanently deleted for a particular account in the Expere Document Services Tool Suite.

## Callback exception issue resolved

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

Previously, an exception occurred in the Expere Document Services Tool Suite when the following conditions existed:

- Callback information was not created for the existing account.
- Performing a Select and Generate action and checking the Callback Required checkbox without entering a URL for the checkbox.

When clicking Submit, the Transaction ID appears blank; clicking Submit again displays the following message:

- There was an issue retrieving information for the specified transaction.

This issue has been resolved; requests are now processed and no callbacks are performed if the URL is not provided.

## Support Page updated to reconcile transactions

- Reference: PBI 354095
- Compliance Impacts: This enhancement is not a compliance or regulatory impact.
- Documentation: SUPPORT Page

Expere Document Services has been enhanced so users can compare submitted and delivered transactions. The search functionality on the SUPPORT Page now allows users to search through one of the following:

- State
- API Call
- Delivery Status
- Delivery Date

For detailed information, see c10082125.html#c10082125__v11735625 on the SUPPORT Page.

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

## Third party libraries updated

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

All third party libraries have been updated to the latest version.

## SUPPORT page enhanced: View button behavior

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

A SUPPORT page enhancement has been implemented when using the Tool Suite in Internet Explorer.

Previously, entering the Account ID and clicking Enter resulted in the Tool Suite immediately loading the transactions for that account. However, the transaction list did not appear for the specified account. Conversely, entering the Account ID and clicking View resulted in the Tool Suite displaying the transaction list for that account.

Now, either clicking View or Enter loads the transaction list for the specified account.

## Logging enhancements implemented

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

The following logging enhancements have been implemented in the Document Generation Services log file:

- External Key; this value originates from the calling application, such as Expere Document Services, DocPrep, or Mortgage.
- Request ID; this value could consist of the the Expere Document Services ID (EDS ID) or DocPrep Book Number.
- Username

## SUPPORT page Date/Time stamp enhanced

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

It was previously reported that the Date/Time stamp disappeared on the SUPPORT page after 130 transactions were submitted.

This issue has been addressed; the Expere Document Services Tool Suite database has been migrated from Raven to SQL. The Date/Time stamp now appears for all transactions submitted.

## Tool Suite enhanced for improved account access and search functionality

- Reference: PBI 351582 / 352874
- Compliance Impacts: This enhancment is not a compliance or regulatory issue.
- Documentation: SUPPORT Page, Select and Generate, Generate, Select, Select-Synchronous.

The following enhancments have been implemented on the SUPPORT, Select and Generate, and Generate, Select, and Select-Synchronous pages of the Document Generation Services Tool Suite:

- SUPPORT page: entering the account number displays the transactions for that account.
- Select and Generate, Generate, Select, and Select-Synchronous pages: entering the account number runs the API call for the specified account.
- Entering the account name or customer number displays the accounts in the account list based on the search terms entered.
- Selecting a transaction opens the Request Details in another internet browser tab.
- Entering a Request ID returns the specific transaction that matches the request ID for the identified account.
- Entering a date or date/time returns all transactions for a specified date range for the identified account.
- The account list is expanded; users can now scroll through the account list.

The SUPPORT, Select and Generate, Generate, Select, and Select-Synchronous pages contains detailed information on using this functionality.

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.

## Osprey common libraries updated

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

All Osprey common libraries have been updated to the latest version.

## Logging enhanced

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

Expere Document Services logging has been enhanced so the Generate EDS ID is now tied to the Deliver EDS ID. Previously, users specify the EDS ID to use with a SelectAndGenerate request; Expere Document Services then created a new Deliver request with a new EDS ID. The log file was not updated with the SelectAndGenerate request EDS ID.

## 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 15 for the CT environment and October 22 for the Production.

## Delivery Request issue resolved

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

It was reported that the Delivery Service was not properly handling any Delivery Request API calls; as a result, the packages did not reach print fulfillment.

This issue has been resolved; the Delivery Service now properly handles Delivery Request API calls, resulting in packages successfully reaching print fulfillment and displaying in Fulillment Manager. Correct callback and status information are facilitated from the Delivery Service to Expere Document Services, and Expere Document Services to the call initator.

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

## Document Generation Services ID issue resolved

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

Certain Expere Document Services transactions displayed a blank DGS ID value on the SUPPORT page when using the Select and Generate and Select, Generate, and Deliver actions. These transactions displayed a Successful status but did not pass the transaction to the Delivery Service for mailing or send a successful callback.

The DGS ID now always appears on the SUPPORT page when a transaction has been successfully processed in Document Generation Services and passed to the Delivery Service or returned through a callback.