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

These elements appear 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.

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

## DocInstances now returned individually for merged PDF

## 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
- Compliance Impact: This enhancement is not a compliance or regulatory issue.
- Documentation: DocInstance, DiscretePartyIDs

The `<DiscretePartyID/>` element is now available in the Expere 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>

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.

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

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

## ListDocuments API added

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

## First page only barcode option now available

- Reference: PBI 292273 / 364317
- 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.

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.

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.

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.