# Change Log Entries

SeptemberThe effective date for all products within the scope of this document for this is September 12 for the CT environment and September 21 for the Production environment.

JSON access functionality updated in Tool Suite
Type: Enhancement Reference: PBI 465891 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: SUPPORT Page: Viewing JSON Data
Summary: We have recently modified the permission set for viewing JSON data for a particular transaction accessible from the SUPPORT Page.
Implementation Notes: This functionality change is available in the September release of Expere Hosted.

eSignature date behavior enhanced
Type: Defect Reference: PBI 463254 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Issue: It was reported that when only one borrower was present in a transaction, static forms were highlighting the eSignature date field for both the primary borrower and co-borrower, thus indicating that the co-borrower should enter a date. This is incorrect behavior.
Solution: This issue has been resolved; co-borrower eSignature and eSignature date fields are now only highlighted as esignable when a co-applicant or co-borrower is part of the transaction and eSignature fields are requested.
Implementation Notes: This feature is available in the September release of Expere Hosted.

AugustThe effective date for all products within the scope of this document for this release is August 8 for the CT environment and August 17 for the Production environment.

Callback timeout reduced to 15 seconds
Type: Enhancement Reference: PBI 455882 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: DeliveryResponse Overview: Additional information - failed transactions and timeouts
Summary: Callbacks previously timed out after one minute. However, after analysis it was determined that a majority of calls are completed in one to two seconds. Now, any call that exceeds 15 seconds results in the callback being retried and a warning being logged.
Implementation Notes: This enhancement is available in the August release of Expere Document Services.

SUPPORT Page: DGS ID and Callback Status column removed
Type: Enhancement Reference: PBI 463283 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: SUPPORT Page
Summary: We have removed the DGS ID and Generate / Delivery Callback Status columns from the SUPPORT Page search results table; however, users can still search for transactions by DGS ID and either Generate Callback Status or Delivery Callback Status.
Implementation Notes: This enhancement is available in the August release of Expere Document Services.

Tool Suite: Barcode justification dropdown value set to Right
Type: Enhancement Reference: PBI 459411 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Select Generate Deliver; Select And Generate; Select / Generate
Summary: Previously, the Barcode Justification dropdown option was set to "Left," however the default option was "Right" if users submitted requests without specifying a justification option. As a result, we have enhanced the Select Generate Deliver, Select And Generate, and Select / Generate pages in the Tool Suite to display "Right" as the default option in the Justification dropdown.
Implementation Notes: This enhancement is available in the August release of Expere Document Services. The Select Generate Deliver; Select And Generate; Select / Generate help topics have been updated to note that "Right" is the default option in the Barcode Justification dropdown.

Attachment order functionality enhanced
Type: Enhancement Reference: PBI 454593 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services: Attachments
Summary: Integrators: we have enhanced our PDF Attachment functionality to give users the ability to specify if they want each of their attached document(s) to be placed at either the “beginning” or “end” of the documents generated by Expere. Today, when attaching PDF(s) to be returned with the Expere generated documents, users are limited to specifying beginning or end for the assembled group of documents being attached. With the enhanced functionality, users can now use the `<AttachmentPosition/>` element to specify the position of each individual PDF being attached, in relation to the Expere-generated documents. For more information, see the `AttachementPosition` parameter in the Expere Document Services: Attachments data type. Tool Suite users: Users can specify whether to attach documents at the Beginning or End of Expere-generated documents on the Select Generate and Deliver and Select and Generate pages. See Select Generate and Deliver and Select and Generate for more information.
Technical Notes: A sample request with this enhanced functionality would resemble the following:
    <data:Attachments>
    <data:AttachmentDoc>JVBERi0xLg==</data:AttachmentDoc>
                   <data:DisplayName>Mustafa</data:DisplayName>
                   <data:AttachmentPosition>End</data:AttachmentPosition>
    </data:Attachments>
Implementation Notes: This feature is available in the July release of Expere Document Services.

MergedCopyPDF behavior resolved
Type: Defect Reference: PBI 459804 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Issue: It was reported that the Ancillary Output MergedCopyPDF option did not return single PDF's with merged PDF's.
Solution: This behavior has been resolved; now when using the Ancillary Output MergedCopyPDF option, both single and merged PDF's are returned.
Implementation Notes: This defect correction is available in the July release of Expere Document Services.

Tool Suite: Recipient Information dialog updated
Type: Enhancement Reference: PBI 455500 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Select Generate Deliver
Summary: We have updated the Recipient Information dialog on the Select Generate Deliver page, consisting of the following changes: CASS, Form 387, and Affidavit now appear in a separate groupbox called Additional Services below the Mail Type groupbox. The MailType groupbox has been renamed to Mail Type. If selecting only the CASS, Form 387, or Affidavit option without selecting a Mail Type option and then attempting to save, an error will appear highlighting the Mail Type groupbox and disallowing the parameters.
Implementation Notes: This enhancement is available in the August release of Expere Document Services.

Tool Suite: ability to re-arrange placement of individual attachments in relation to generated PDF's
Type: Enhancement Reference: PBI 442665 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Select Generate and Deliver, Select and Generate, Select / Generate
Summary: Users can now place documents before or after Expere-generated documents ("Expere Documents") in the Expere Document Services Tool Suite. This enhancement impacts the Select Generate and Deliver, Select and Generate and Select / Generate API's.
Implementation Notes: This enhancement is available in the August release of Expere Document Services.

JulyThe effective date for all products within the scope of this document for this release is July 11 for the CT environment and July 20 for the Production environment.

New color element added
Type: New Feature Reference: PBI 445207 Compliance Impacts: This item is a compliance or regulatory issue. Documentation Impacts: DocInstance
Summary: A new child element, `<ColoredPaper/>`, has been added to the `<DocInstance/>` element of the Expere Document Services Response. The new element `<ColoredPaper/>` will be included in the Expere Document Services response and set to ‘True’ when a selected form is authored with a color paper attribute. If the form(s) are not authored with the color paper attribute, the `<ColoredPaper/>` element will not be included in the Expere Document Services response.
Solution/Technical Notes: A sample response file could consist of the following:
    <r:DocInstance DocIDRef="PKGD.AuthorizationDocumentAccounts_Copy">
    		<r:SignaturePointSet>
    			<r:Signer>
    				<r:Id>S3</r:Id>
    				<r:Description>Account Holder</r:Description>
    				<r:SignaturePoints>
    					<r:SignaturePoint>
    					<r:IncludeDate>false</r:IncludeDate>
    					<r:PageNumber>2</r:PageNumber>
    					<r:PageOrder>2</r:PageOrder>
    					<r:Height>36.0</r:Height>
    					<r:Width>198.0</r:Width>
    					<r:SignatureText>S3</r:SignatureText>
    					<r:XCoordinate>37.0</r:XCoordinate>
    					<r:YCoordinate>341.5</r:YCoordinate>
    					<r:Type>Signature</r:Type>
    					<r:FieldName>SIG_Account Holder_S1_S3_true_2</r:FieldName>
    				       </r:SignaturePoint>
    				</r:SignaturePoints>
    			</r:Signer>
    		</r:SignaturePointSet>
    		<r:ColoredPaper>True</r:ColoredPaper>
    	</r:DocInstance>
Implementation Notes: This feature requires a June update of Expere Document Services.

Duplexing now available as Ancillary Output Option
Type: Enhancement Reference: PBI 446254 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: AncillaryOutputTypeEnum
Summary: A new`<OutputType/>` element has been added as an ancillary output type in the request. Expere scans .REQ files for a particular transaction to determine if the `<OutputType/>` element is set to "Blank," "Simplex," "Duplex," or "Does Not Exist." If set to "Duplex" and if the page total is set to "Odd," a blank page is inserted at the end of the document. If the request does not include "Duplex," no duplexing logic is applied.
Technical Notes:
    <AncillaryOutput>
                <AncillaryOutputOption>
                   <OutputType>Barcode</OutputType>
                   <Barcode>
                      <Type>barcode128</Type>
                      <Pattern>barcode</Pattern>
                      <UseCoverPage>true</UseCoverPage>
                      <FirstPageOnly>true</FirstPageOnly>
                   </Barcode>
                   <OutputType>Watermark</OutputType>
                   <Watermark>
                      <Text>Test PBI</Text>
                      <Rotate>true</Rotate>
                      <Location>center</Location>
                   </Watermark>
                   <OutputType>Duplex</OutputType>
                </AncillaryOutputOption>
             </AncillaryOutput>
Implementation Notes: This feature is available in the June release of Expere Document Services.

Tool Suite now available for our external users
Type: New Feature Reference: PBI 446023 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services Tool Suite
Summary: The Expere Document Services Tool Suite is now available for our external users.
Implementation Notes: This feature is available in the July release of Expere Document Services.

TM_INVALID_CHARACTER updated to WARN (previously ERROR)
Type: Enhancement Reference: PBI 442242 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: We have updated the TM_INVALID_CHARACTER ERROR to now be logged as a Warning (WARN), instead of an ERROR.
Implementation Notes: This feature is available in the July release of Expere Document Services.

Barcode enhancement: additional location options for integrators
Type: Enhancement Reference: PBI 443544 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Barcode
Summary: Expere Document Services users may now specify their barcode location in their request by selecting one of the following optional justification parameters using the `HorizontalAlignment` parameter: Left Center Right These barcode adjustment options affect the following API's: Select, Generate, and Deliver Select and Generate Generate
Technical Notes: If a barcode justification parameter is not specified in the request, the default location of the barcode will be set to the right of the page. 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 is available in the July release of Expere Document Services.

<DocIDRef> Available in Generate Results
Type: Enhancement Reference: PBI 440694 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact.
Summary: `<DocIDRef>` has been added to the `<DocInstance>` element for Generate results. This addition provides the ability to parse for documents and simplifies matching up Generate results to the Select results.
Implementation Notes: No user action is required.

JuneThe effective date for all products within the scope of this document for this release is June 13 for the CT environment and June 22 for the Production environment.

Scheduled task enhancement
Type: Enhancement Reference: PBI 439889 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: SERVICES Page; DeliveryResponse Overview
Summary: We have created a scheduled task that looks for any Expere Document Services transactions residing in an Incomplete status exceeding ten (10) minutes. This scheduled task runs in five minute intervals. Integrators should note that if a failed transaction includes a callback URL, a callback is sent to the user indicating that the transaction has failed; see DeliveryResponse Overview for more information.
Implementation Notes: This enhancement is available in the June release of Expere Document Services. Additionally, see PBI

Tool Suite: global interface change
Type: Enhancement Reference: PBI 449547 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services Tool Suite webhelp
Summary: We have implemented the following changes to the Expere Document Services Tool Suite: The header on each page has been updated to display as Expere Document Services ®. The Get Generate Results page is now the Generate Results page. The Get Select Results page is now the Select Results page. The Add Recipients dialog have been enhanced to display the Recipient and Mail Type information in a more readable format.
Implementation Notes: This enhancement is available in the June release; no user action is required. For more information, see the Expere Document Services Tool Suite webhelp.

Tool Suite: new roles and permissions implemented
Type: Enhancement Reference: PBI 437713 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Consult Administration webhelp for detailed information.
Summary: New Toolsuite Expere Document Services roles have been created for external Expere Document Services users, consisting of the following permissions: Toolsuite Access Permissions: allow access to the Tool Suite Deliver Call Access Permissions: allow access to the following API's: Select Generate and Deliver Delivered Images Delivery History Deliver
Implementation Notes: This enhancement is available in the June release.

OPPSA help topics and change log removed from Expere Document Services
Type: Enhancement Reference: PBI 443974 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Expere Document Services webhelp updated: http://documentation.wolterskluwerfs.com/Help/EDS/
Summary: We have removed the following OPPSA help topics from the Expere Document Services change log: Change log OPPSA user guide appendix Web services
Implementation Notes: No user action is required.

AprilThe effective date for all products within the scope of this document for this release is April 11 for the CT environment and April 20 for the Production environment.

OPPSA merge transaction issue resolved with Internet Explorer 11
Type: Defect Reference: PBI 433393 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Issue: Users were unable to download OPPSA merged transactions in Internet Explorer 11. Google Chrome users were unaffected.
Solution: This issue has been resolved; users can now download OPPSA merged transactions in Internet Explorer 11.
Implementation Notes: No user action is required.

Logging levels updated
Type: Enhancement Reference: PBI 434758 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact.
Summary: Previously, all exceptions that appeared in our log files were reported as errors. This did not reflect the nature nor severity of the exception being logged.
Technical Notes: We have modified our level of logging to consist of the following: Fatal: No user action is required. Error: system error that does not set off an alert; retries; ongoing system issue. Warning: transactions with invalid GUID format, permissions issues, invalid characters being passed in, invalid transaction xml, etc.
Implementation Notes: No user action is required.

MarchThe effective date for all products within the scope of this document for this release is March 9 for the CT environment and March 16 for the Production environment.

Implementation Strategies section added to webhelp
Type: Enhancement Reference: PBI 431602 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Implementation Strategies
Summary: To better enhance our users' webhelp experience, we have organized existing Ancillary Outputs (Post-Processing), RequestUCD flag - PDF/A, and MergeTRIDDocs flag - PDF help content into a new Implementation Strategies section.
Implementation Notes: No user action is required.

Document/transaction expiration behavior modified
Type: Enhancement Reference: PBI 422732 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: SelectAndGenerateRequest; GenerateRequest.
Summary: Users can now identify the number of days to retain transaction data and documents on a transaction by transaction basis or at an Account level; when the default (7 days) does not meet their needs.
Implementation Notes: We have repurposed the `<DaysToPersistInLongTermStorage/>` element in the SelectGenerateDeliverIn SelectAndGenerateIn and GenerateIn API methods to support setting a number of days to retain if something other than the default is desired.

Ability to merge closing disclosures with addendum
Type: New Feature Reference: PBI 428212 Compliance Impacts: This new feature is not a compliance or regulatory issue. Documentation Impacts: MergeTRIDDocs flag - PDF.
Summary: We have implemented a new `<MergeTRIDDocs/>` element that allows users to merge the following TRID documents through the request file: ClosingDisclosure ClosingDisclosureAddendum ClosingDisclosure-SellerOnly ClosingDisclosure-SellerOnly-Addendum
Technical Notes: With this enhancement, if the `<MergeTRIDDocs/>` flag is set to "true" in a Select and Generate or Generate request, the addendums above are merged with the associcated closing disclosure into a single standard PDF file. As a result, the closing disclosure, merged with the addendum, is returned in the response with the normal closing disclosure instance name and the addendum instance is removed from the response.
Implementation Notes: For more information, see MergeTRIDDocs flag - PDF.

FebruaryThe effective date for all products within the scope of this document for this release is February 9 for the CT environment and February 16 for the Production environment.

Webhelp enhancements - Request and Response samples enhanced
Type: Enhancement Reference: PBI 365494 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Appendix: Request and Response Samples
Issue/Summary: We have enhanced our request and response samples for the various DocServices API methods to contain actual data; this will replicate what users would see in their requests and responses.
Implementation Notes: No user action is required.

Webhelp enhancements - DocViewer
Type: Enhancement Reference: PBI 360045 Compliance Impacts: This enhancement is not a compliance or regulatory issue. Documentation Impacts: Getting Started, BeginSession, EndSession, and PreCachSession.
Issue/Summary: We have updated the Expere Document Services webhelp to reflect several enhancements, primarily around using the `SecurtiySessionSvc`; we have added a new Getting Started section that discusses using the WSDL and SOAP; we have also updated the the request and response samples for BeginSession, EndSession, and PreCachSession.
Implementation Notes: No user action is required.

Integrators: Callback statuses added to GetRequestStatus API
Type: Enhancement Reference: PBI 382260 Compliance Impacts: This enhancement is not a compliance or regulatory issue. Documentation: RequestStatusIn, RequestStatusOut, GetRequestStatus
Issue/Summary: The GetRequestStatus API now contains a `</CallbackStatus>` element that informs the user whether a callback was successful, failed, or not requested. This allows users to know the status of their transaction when submitted. See RequestStatusIn RequestStatusOut GetRequestStatus for more information.
Solution/Technical Notes: The list of callback statuses consists of the following: Successful Failed NotRequested
Implementation Notes: No user action is required.

Integrators: API updates to include OPPSA parameters
Type: Enhancement Reference: PBI 404746 Compliance Impacts: This enhancement is not a compliance or regulatory issue. Documentation: SelectGenerateAndDeliverIn, SelectAndGenerateIn, GenerateIn
Issue/Summary: This enhancement allows Expere Document Services to return OPPSA organization and production information to OPPSA users.
Solution/Technical Notes: We have added OPPSA Organization and OPPSA Product parameters to the following API's:
Implementation Notes: No user action is required.

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

Integrators: Callback statuses added to GetRequestStatus API
Type: Enhancement Reference: PBI 382260 Compliance Impacts: This item is/is not a compliance or regulatory issue. Documentation Impacts: RequestStatusIn, RequestStatusOut, GetRequestStatus
Summary: The GetRequestStatus API now contains a `</CallbackStatus>` element that informs the user whether a callback was successful, failed, or not requested. This allows users to know the status of their transaction when submitted. See RequestStatusIn RequestStatusOut GetRequestStatus for more information.
Technical Notes: The list of callback statuses consists of the following: Successful Failed NotRequested

Integrators: API updates to include OPPSA parameters
Type: Enhancement Reference: PBI 404746 Compliance Impacts: This item is/is not a compliance or regulatory issue. Documentation Impacts: SelectGenerateAndDeliverIn, SelectAndGenerateIn, GenerateIn
Summary: This enhancement allows Expere Document Services to return OPPSA organization and production information to OPPSA users.
Technical Notes:
Implementation Notes: We have added OPPSA Organization and OPPSA Product parameters to the following API's: SelectGenerateDeliver SelectAndGenerate Generate