# Document Generation Services Change Log Entries

The effective date for all products within the scope of this document for this release is July 21, 2016 for the CT environment and TBD for the Production environment. The latest version of Document Generation Services uses the following:

- Expere Engine version 16.2.03624; see the Expere Engine and Tools Change Log for detailed information on the 2016.2 release.
- Content Admin Tool version 15.3.3.8154.

## Document Generation Services logging enhanced for improved consistency

- Reference: PBI 386860
- 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.

## 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 fields, , Select And Generate, Generate.

In an effort to support returning XY coordinates for all fillable fields we have begun the development work. The first step in supporting this feature is creating a new element (eSignatureAndFieldSupport). This element will only pass XY coordinates for esignatures at this time. In a future release it will control XY coordinates for all fillable fields.

## SignaturePointSet and eSignatureAndFieldSupport element changes

- Reference: PBI 388966
- Compliance Impacts: This new feature is not a compliance or regulatory issue.
- Documentation: Using eSignature and Acroform fields

In an effort to support returning XY coordinates for all fillable fields we have begun the development work. The first step in supporting this feature is creating a new element (eSignatureAndFieldSupport). This element will only pass XY coordinates for esignatures at this time. In a future release it will control XY coordinates for all fillable fields. See the Using SignaturePointSet and eSignatureAndFieldSupport section in Using eSignature and Acroform fields for details on these two elements.

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

## First Page functionality available

- Reference: PBI 370563; original PBI 364255
- Compliance Impact: This enhancement is not a compliance or regulatory issue.
- Documentation: Using First Page Only Barcodes

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.

Note: The release date for this functionality has yet to be determined.

## eSignature and AcroForm fields added

- Type: Enhancement
- Reference: PBI 379704, 379926
- Compliance Impact: This enhancement is not a compliance or regulatory issue.
- Documentation: Using eSignature and Acroform fields

Users can now pass eSignature and Acroform values in the AncillaryOutput of a SelectAndGenerate or Generate request. For detailed information on enabling or disabling eSignature or Acroforms, see Using eSignature and Acroform fields.

The effective date for all products within the scope of this document for this release is April 14, 2016 for the CT environment and April 21, 2016 for the Production environment.

The latest version of Document Generation Services uses the Expere Engine version 2015.4. See the Expere Engine and Tools Change Log for detailed information on the 2015.4 release.

There were no external facing changes for this release

## ListDocuments API Added

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

The Expere ListDocuments API is now available through DGS.

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.

The effective date for all products within the scope of this document for this release is March 10, 2016 for the CT environment and March 17, 2016 for the Production environment.

## SQL Scripts enhanced

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

SQL scripts used with the Document Generation Services tables have been enhanced to remove any records older than seven (7) days. The scripts now remove the records on a nightly basis.

## First page only barcode option now available

Note: This feature is NOT fully functional and will be available in a future release.

- Reference: PBI 364255
- 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, 2016 for the CT environment and February 18, 2016 for the Production environment.

There were no external facing changes for this release.

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

## Certficate process updated

- Reference: PBI 357332
- Compliance Impacts: This enhancement is not a compliance or regulatory issue.
- Documentation: SelectAndGenerate Request, Callback, CallbackAuthentication.

Document Generation Services now utilizes a certificate when calling the callback service. The callback object now includes an authentication object, which consists of a username, password, and client certificate name.

Integrators should consult SelectAndGenerate Request, Callback, and CallbackAuthentication for detailed information on using certificates.

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

## Management Services API available for cloning/copying aliases

- Reference: PBI 347356
- Compliance Impacts: This new feature is not a compliance or regulatory issue.
- Documentation: Management Services: Manage Libraries API.

A new Management Services checkAliasesinAccount API is now available that determines whether custom content from a source account should be applied to a new account when using the Copy Aliases function in the Document Generation Services Management Tool.

For detailed information, see checkAliasesinAccount.

## Aliases now needed only for custom content

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

Document Generation Services now automatically allows access to base content; users are now no longer required to create an alias for base content in the Management Tool.

An alias is now required only if a library is pointing to custom content. When pointing to base content, the library will incorporate "Mortgage" into the alias.

The effective date for all products within the scope of this document for this release is October 8, 2015 for the CT environment and October 14, 2015 for the Production environment.

## ManageLibraries API added to Document Generation Services

- Reference: PBI 339602
- Compliance Impacts: This new feature is not a compliance or regulatory issue.
- Documentation: Management Services: Manage Libraries

A new API called ManageLibraries has been added to create a new alias and add account permissions to a library when cloning accounts.

The ManageLibraries API consists of the following operations:

- CloneAccount: copies an existing account's alias for a new account. Permissions for the new account is added to any library to which the sibling account has access
- DeployLibrary: deploys the library containing the cloned account information

See Management Services: Manage Libraries for detailed information on integrating with the ManageLibraries API.

## Callback reattempt enhanced

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

The callback functionality has been enhanced in Document Generation Services to automatically reattempt upon a failed callback to the calling application.

Document Generation Services now reattempts a callback in the following intervals:

- One (1) second
- Two (2) seconds
- Four (4) seconds
- Eight (8) seconds
- Sixteen (16) seconds

## Logging enhanced

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

Logging enhancements have been implemented for Document Generation Services to include the duration for a request to complete and wait times. This will provide Wolters Kluwer with more information to analyze environments

The effective date for all products within the scope of this document for this release is October 8, 2015 for the CT environment and October 14, 2015 for the Production environment.
There were no external facing changes for this release