# Change Log Entries

OctoberThe effective date for all products within the scope of this document for this release is October 10 for the CT environment and October 19 for the Production environment.

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

Tool Suite: Content URI Enhancement
Type: New Feature Reference: PBI 465901 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Content URI
Summary: Users will now be provided with the option to generate a Content URI by selecting from a list of aliases and packages that are pertinent to their account via a pop-up window that can be navigated to from the toolsuite. This is available in addition to the currently available option of entering their desired Content URI into a textbox in the form of an expression.
Technical Notes: The Generate button allows users to access a user interface from which users are able to select an alias and a package from which the application will generate a content URI to be used for the transaction.
Implementation Notes: See Content URI for more information.

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 requires a 2017.1 Expere Engine update.

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.

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

Attachment order functionality enhanced using `<BeginningOrEnd/>` element
Type: Enhancement Reference: PBI 442668 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Web Services: PDF
Summary: 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 `<BeginningOrEnd/>` element to specify the position of each individual PDF being attached, in relation to the Expere-generated documents.
Technical Notes: A sample request with this enhanced functionality would resemble the following:
    <c:ExternalPDFDocuments>
    <c:PDFs>
                 <c:PDF>
                        <c:InstanceDisplayName>ExternalDocONE</c:InstanceDisplayName>
                        <c:InstanceFileName>External_Document_Front_ONE</c:InstanceFileName>
                        <c:DocData>
                               <c:base64>base64 string goes here</c:base64>
                        </c:DocData>
                        <c:BeginningOrEnd>beginning</c:BeginningOrEnd>
                 </c:PDF>
    </c:PDFs>
    </c:ExternalPDFDocuments>
Implementation Notes: This feature is available in the July release of Document Generation 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 Document Generation Services.

Barcode enhancement: additional location options for integrators
Type: Defect/Enhancement Reference: PBI 440796 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Barcode
Summary: Document Generation Service 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 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 Document Generation Services.

New color element added
Type: New Feature Reference: PBI 445208 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: A new child element, `<ColoredPaper/>`, has been added to the `<DocInstance/>` element of the Document Generation Services Response. The new element `<ColoredPaper/>` will be included in the Document Generation 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 Document Generation Services response. Document Generation Services then passes this new element to Expere Document Services.
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, Account Holder, Account Holder, 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.

MayThe effective date for all products within the scope of this document for this release is May 9 for the CT environment and May 18 for the Production environment.

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

Logging levels updated
Type: Enhancement Reference: PBI 434757 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: major system outage or SQL exception. 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 431695 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.

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.

Document/transaction expiration behavior modified
Type: New Feature Reference: PBI 422666 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 SelectAndGenerateRequest and GenerateRequest API methods to support setting a number of days to retain if something other than the default is desired. Note: If interested in this functionality please contact your Professional Services representatives.

Ability to merge closing disclosures with addendum
Type: New Feature Reference: PBI 419537 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.