# Document Generation Services Change Log Entries

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.

MergedCopyPDF behavior resolved
Type: Defect Reference: PBI 455321 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 Document Generation Services

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 allow users to indicate if they would like their attached document(s) to be returned at 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 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. Additionally, when working with multiple attachments, users can control the order of their attachments, at the beginning and end, by submitting them in their desired order in the request. Below is an example showing documents being attached with the `<BeginningOrEnd/>` element included in request and the PDF result: Request Order: DocA - end DocB - beginning DocC - end PDF Result: DocB Expere-Generated Document(s) DocA DocC Note: If users do not include the `<BeginningOrEnd/>` element when attaching their own PDF(s), the PDF(s) will be placed at the end of the Expere generated documents. The `<BeginningOrEnd/>` element is also supported with the MergedPDF Ancillary Output option.
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.

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

Barcode enhancement: additional location options for Tool Suite users
Type: Enhancement Reference: PBI 442223 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Select and Generate, Generate
Issue/Summary: Tool Suite users can now customize the justification parameters of the generated ancillary barcode by placing the barcode at a desired location within the reserved barcode area in the lower margin of documents. This applies to Select and Generate and Generate requests whereby users can select from one of the following justification options: Left Right Center
Implementation Notes: This feature is available in the July release of Document Generation Services. For more information, see the following: Select and Generate Generate

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.

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

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.

Contract updated for DocViewer
Type: Enhancement Reference: PBI 449380 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Background: A need existed for Document Generation Services (DGS) to consume the new DocViewer contracts so ComplianceOne® mortgage could call DGS and pass the new parameters to DocViewer through a new service call. This new contract, WoltersKluwerFS.DocViewerInterface.Contracts, contains the DocViewer data and operation contracts.
Summary: WoltersKluwerFS.DocViewerInterface.Contracts has been updated in DGS and is now available for use.
Implementation Notes: This enhancement is available in the June release of Document Generation Services; no user action is required.

Management Tool: Stack trace error when updating aliases has been resolved
Type: Defect Reference: PBI 449079 Compliance Impacts: This item is/is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Issue: It was identified that updating a group of aliases to point to a new library version that was not previously deployed or does did not exist, triggered a stack trace error that was not user friendly.
Solution: Users are now presented with a user friendly message with direction on how to rectify the error. "Before updating a group of aliases to a new library version, the new library with the new version must be deployed. Please validate the library version you have entered is correct and try again.
Implementation Notes: This enhancement is available in the June release.

New Ancillary Output Type of Duplex
Type: Enhancement Reference: PBI 446253 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: AncillaryOutputOptions, Select and Generate and Generate
Summary: A new Ancillary Output Type of Duplex has been added to the Expere Request. The AncillaryOutputOptions under the Document Services API has been updated. The new Duplex checkbox has also been added under Ancillary Outputs on the SERVICES Page for both Select and Generate and Generate in Tool Suite.
Implementation Notes: This enhancement is available in the June release.

Management Tool: message now appears when alias group is updated
Type: Enhancement Reference: PBI 449079 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: Previously, the following enhancements were implemented in the Management Tool: The number of aliases being updated to point to a new library version and The number of aliases that were impacted with the update. We have found, if you try to update a group of aliases to point to a new library version that has not been deployed or does not exist, you get a stack trace error.
Technical Notes: Verify when attempting to update a group of aliases to a new library version that has not been deployed, you receive the new message (stack trace error is no longer given) in the Management toolsuite
Implementation Notes: This enhancement is available in the June release.

Tool Suite: file attachment issue resolved
Type: Defect Reference: PBI 442443 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Issue: It was reported that users able to complete the attach file function but the end result did not include the attachedment when using the Attachment and Merged PDF features with the Select Generate and Deliver, Select and Generate, and Generate API's.
Solution: Tool suite users can now successfully attach files and submit transactions using Attachment and Merged PDF features for the Select Generate and Deliver, Select and Generate, and Generate API's.
Implementation Notes: This defect correction is available in the June release.

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.

There were no external-facing changes for this release.

Alias update enhancement
Type: Enhancement Reference: PBI 442306 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Updating the Version Number for an Alias Group
Background: Previously, internal personnel were required to manually maintain and run specific scripts before and after each update to alias version numbers.
Summary: We have enhanced the Document Generation Services Management Tool so that scripts now run as a background process through the Manage Alias / Update Group of Aliases page.
Implementation Notes: See Updating the Version Number for an Alias Group for more information.

Document Generation Services update to accommodate OPPSA IntegrationService methods
Type: Enhancement Reference: PBI 440820 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Issue/Summary: We have updated Document Generation Services to accommodate a security enhancement to the following OPPSA IntegrationServices methods: GetOrganizations GetProductsForOrgGuid MergeProductData
Technical Notes: The OPPSA Integration Service now uses `HTTPS` with https://labw6408hvm981.wkmnlab.net/OPPSA/IntegrationService.svc.
Implementation Notes: Users will need to update the URL to the OPPSA Integration Service.

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.

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.

Help Button Added to Tool Suite
Type: Enhancement Reference: PBI 317364 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact.
Summary: A Help button has been added to the user interface.
Technical Notes: The Help button allows users to access the webhelp for the DGS Tool Suite. When the Help button is clicked, the webhelp displays in a new tab.

Generate Results messaging enhanced
Type: Enhancement Reference: PBI 431748 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: We have enhanced Generate Results for a transaction to display a message when using a service against a transaction that has been deleted from Document Generation Services.
Technical Notes: When a user enters a Transaction ID that has been previously deleted, the response is returned in the Status Description that states the following: "There was an error while trying retrieve the request status for a document request. No requests found for RequestID af0f63f1-9b3b-4ed6-a425-a6cf00f6ae99, as a result no documents could be returned."
Implementation Notes: No user action is required.

Management Tool: Library page enhancements
Type: Enhancement Reference: PBI 437910 / 437911 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Manage Libraries
Summary: We have implemented the following enhancements to the Manage Libraries page: The library list now appears in table form, most recent deployed libraries appearing first. This allows for ease of use and sortability. To view Undeployed or Removed libraries, select the applicable Library Status from the dropdown. Date of Deployment has been added as a column to the new table. Selecting a library row in the table opens the Details page for that library in a new browser tab. The Details button has been removed.
Implementation Notes: For more information, see Manage Libraries.

Management Tool: Library notes enhancement
Type: Enhancement Reference: PBI 267496 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Deploying New Libraries
Summary: The Deploy Library page now contains a Note(s): field that allows users to enter any notes for a specific library. Upon deploying the library, the notes are preserved for future viewing.
Implementation Notes: For more information, see Deploying New Libraries.

Management Tool: Library Version Numbering
Type: Defect Reference: PBI 425251 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Deploying New Libraries
Issue: When creating a new library using the DGS Management Tool, if a library version number greater than 2147483647 is entered, it is being converted by the program to zero.
Solution:A version number greater than 2147483647 should not be used when deploying a new library. If it is a validation message will be displayed requesting a smaller number be entered. Entering a decimal into the version number will also trigger a validation error message.
Implementation Notes: For more information, see Deploying New Libraries.

Transform file updated with new variables
Type: Enhancement Reference: PBI 432057 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Appendix: Sample Transforms.xml file
Summary: We have added Document Generation Services variables from the `Transforms.xml` file into OctoDeploy for all environments. Variable changes can now be made via OctoDeploy without needing to create a new build to update the `Transforms.xml`. We’ve created a `Sample_Transforms.xml` file that will be included in each DGS build as a reference and will be updated as new Properties are added. The original `Transforms.xml` is still included in the build, but will be adjusted or removed in the future.
Implementation Notes: For more information, see Appendix: Sample Transforms.xml file.

Document Generation Services installer option added to include Expere
Type: Enhancement Reference: PBI 433706 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Configuring Transforms.xml and creating/installing the Document Generation Services components
Summary: Users can now select whether or not to install Expere when installing Document Generation Services. The Document Generation Services .msi installation file now includes a checkbox to either include or not include Expere.
Implementation Notes: See Configuring Transforms.xml and creating/installing the Document Generation Services components for more information.

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.

Loan Number added to SUPPORT page
Type: Enhancement Reference: PBI 425505 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: SUPPORT Page
Summary: Users can now view and search for transactions based on the loan number on the SUPPORT Page. We have implemented a new column called Loan Number.
Implementation Notes: No user action is required; for more information, see the SUPPORT Page.

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.

Internal tool suite webhelp enhanced
Type: Enhancement Reference: PBI 431697 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Document Generation Services Tool Suite User Guide
Summary: We have enhanced the internal Document Generation Services webhelp to contain a dedicated Tool Suite section. Previously, the help topics existed separately and were not organized in a consistent fashion.
Implementation Notes: See Document Generation Services Tool Suite User Guide for more information.

Document Generation Services Installer enhanced for Wildfly uninstall
Type: Enhancement Reference: PBI 429204 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: Internal users noted that Wildly would not terminate in a timely fashion when using the DGS installer. As a result, the DGS installer crashed. Previously, we had instituted a temporary script that reduced the issue; however it still attempted to execute a file that did not exist after a failed installation which ensured a failed installation.
Solution: We have incorporated the above enhanced temporary script into the DGS installer to ensure all executed commands exist.
Implementation Notes: No user action is required to run the script.

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: SETUP Page; Select And Generate; Generate; .
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: To specify a unique number of days to retain this data at an Account level (all transactions submitted under the account will be impacted) the Days to Expire field under the SETUP page should be used. If the default (7 days) is applicable there is no need to update/visit the SETUP page. To specify a unique number of days to retain this data by transaction, the Select And Generate, and Generate pages have been updated with a Days To Expire field. Lastly 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.

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 Select and Generate; Generate.
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. In the Tool Suite, selecting the TRID Merge checkbox on either the Select and Generate or Generate page merges the above the documents.
Implementation Notes: For more information, see MergeTRIDDocs flag - PDF. Internal users should also consult Select and Generate and Generate in the Document Generation Services webhelp.

Tool Suite: ability to call MergeProductData Method
Type: New Feature Reference: PBI 418074 Compliance Impacts: This item Is not a compliance or regulatory issue. Documentation Impacts: OPPSA Merge Product Data
Issue/Summary: We have identified a need to assist in troubleshooting and testing the MergeProductData OPPSA integration method.
Solution/Technical Notes: We have added a new action on the Document Generation Services Tool Suite SERVICES page, titled OPPSA Merge Product Data. Upon accessing this action, users will enter their OPPSA login credentials and submit a transaction .xml file to call the `MergeProductDataUI` integration method.
Implementation Notes: For detailed information on using this new action, see OPPSA Merge Product Data.

Management Tool: Alias enhanced
Type: Defect Correction Reference: PBI 421566 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Issue/Summary: Previously, it was noted that when using special characters in the alias name, the Document Generation Services Management Tool could not validate any of the characters after the special characters. As a result, the following validation warning appeared: "The original value already exists for account #####." Based on this behavior, it was determined to prohibit the use of special characters in the alias name.
Solution/Technical Notes: We have enhanced this behavior; if attempting to use special characters when creating an alias, the following warning message now appears: "Special characters are not allowed." The Add button is also disabled.
Implementation Notes: With this enhancement, users can only use 0-9 and A-Z / a-z alphanumeric characters.

Tool Suite Timeout Resolved
Type: Defect Correction Reference: PBI 422536 Compliance Impacts: This defect correction is not a compliance or regulatory issue. Documentation: No Document impact.
Issue/Summary: Previously, users received an error message when submitting an API call in the Tool Suite after 25 minutes of user the tool suite.
Solution/Technical Notes: Users no longer receive an error message when submitting any API call related activity after 25 minutes of using the tool suite.
Implementation Notes: No user action required.

Management Tool Enhancements: field label changes
Type: Enhancement Reference: PBI 352496 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: Management Tool: Assigning Aliases
Issue/Summary: A need existed to name field labels consistently for the Document Generation Services Management Tool.
Solution/Technical Notes: We have made the following field label modifications: We have modified the NewValue label on the Add an Alias page to now display as Destination Value. Additionally, we have increased the Destination Value field length so users can see the entire path in most instances. We have changed the OrigValue label to Original Value.
Implementation Notes: For more information, see Management Tool: Assigning Aliases.

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.

Management Tool: undeployed orphaned aliases enhanced
Type: Enhancement Reference: PBI 384385 Compliance Impacts: This item is not a compliance or regulatory issue. Documentation Impacts: No documentation impact
Summary: In a previous release we had introduced enhancements to the Management Tool to formally remove accounts and aliases associated to a library when the library is being un-deployed (see previous Change Logs for PBI's 404166 & 382509). Prior to those changes, when un-deploying a library, aliases associated to those libraries (that were un-deployed) would become an ‘orphan’ in the database and would still show in the Account list.
Implementation Notes: With this release we performed a ‘clean up’ to remove all orphaned aliases, for un-deployed libraries, from the database and the Account list.