Changelog Entries (Octopus Deploy delivery) - 2023

Note: The information presented in each section is deployed on a monthly basis; work with your Professional Services liaison if you wish to consume this release.
Note: The Document Generation Services Changelog uses a dynamic URL to display the changelogs relevant to your version of the program, and as a result, the URL changes from release to release. For best results, always access the Changelog by clicking the hyperlink from the Document Generation Services landing page. If your desire is to bookmark the changelogs, we recommend bookmarking the landing page rather than the Changelog.

You may need to clear your cookies, data, and browsing history. Some users may notice that changelogs do not appear on this page. If that is the case, clear your cookies.

December

This release utilizes the following Nuget Packages:
  • Document Generation Services version: 22.2.0.4602
  • Expere Engine version: 23.4.0.5354
  • DocViewer version: 23.1.0.959
  • Document Generation Services Core version: 23.1.0.134
  • Document Generation Services Core DocViewer version: 23.1.0.134
  • Security Administration version: 6.1.0.1491
  • Expere Document Services: 22.2.0.2047
  • Expere Document Services Tool Suite: 22.2.0.2045
  • DocumentServices: 22.2.0.235
  • EZ Config:
    • EZConfig Packages and Packets version: 2023.10.0.3087
    • EZConfig Default Data version: 2023.10.0.562
    • EZ Config Service version: 2023.10.0.682
    • EZ Gateway version: 2023.10.0.680
  • Databases:
    • Document Generation Services Database version: 22.2.0.4602
    • Packages and Packets Database version: 2023.10.0.3087
    • Default Database version: 2023.10.0.562
    • Security Administration Database version: 6.1.0.1491
    • Expere Document Services Database version: 22.2.0.1981

Installation / Upgrade Notes

Note the following installation and upgrade changes in the December release:

  • Transform variable changes:
    • NA
  • Octopus variable changes:
    • NA
  • Installation and upgrade changes:
    • NA
  • WSDL Changes:
    • NA
Management Tool: ability to update multiple aliases behavior enhanced
  • Type: Enhancement
  • Reference: PBI 796823
Summary: Attempting to change the alias to point to updated content for a number of users did not function correctly; while the Alias Destination value updated, the EZConfig repost failed. This process is performed using the Update Alias by Library function within the Document Generation Services Management Tool.

This behavior has been enhanced so that the EZConfig reposts with the Update Alias by Library functionality.
Engine: Watermark processing flow updated for upcoming iText upgrade
  • Type: Enhancement
  • Reference: PBI 762647
Summary: Internal analysis has determined that an upcoming iText upgrade would impact the way watermarks function within the Expere Engine. As a result, watermark processing has been updated within Expere to accommodate an upcoming iText upgrade.
Note: This upgrade will not affect integrations or generated documents.
Engine: Document assembly behavior updated when using images with a Tagged PDF
  • Type: Enhancement
  • Reference: PBI 799727
Summary: It was reported that images failed to display on some generated Tagged PDF documents. After internal analysis was conducted, it was determined that Expere should be updated to fail transactions and not generate documents when images are not located and cannot be printed on the document.
Note: This enhancement will only affect those documents assembled with FOP 2.8.
DocViewer: Track Changes enhancement
Summary: DocViewer has been enhanced so that changes can be saved and accessed during a later session. Users may now pass in a changedDataPoints flag during a BeginSession, so that additional modifications may be applied to a new session.
Note: The record of changes appears after submitting documents or ending a current session on the End Session page within the Changed Transaction Data section. Users can continue to apply these same changes by selecting the Transfer changes to new session button on the End Session page then submitting a changedDataPoints flag during subsequent sessions.
DocViewer: PKGPKT.PackageName behavior enhanced with BeginSession
  • Type: Defect
  • Reference: PBI 800848
Issue: Users reported 404 issues when attempting to launch a BeginSession using an EZ Config PKGPKT.PackageName content URI. Internal analysis determined that the alias was not being passed when retrieving the package from EZ Config Packages and Packets when using a BeginSession.
Solution: This behavior has been enhanced so that a DocViewer BeginSession can be started using PKGPKT.PackageName.

November

This release utilizes the following Nuget Packages:
  • Document Generation Services version: 22.2.0.4577
  • Expere Engine version: 23.4.0.5295
  • DocViewer version: 23.1.0.948
  • Document Generation Services Core version: 23.1.0.123
  • Document Generation Services Core DocViewer version: 23.1.0.123
  • Security Administration version: 6.1.0.1483
  • Expere Document Services: 22.2.0.1981
  • Expere Document Services Tool Suite: 22.2.0.1989
  • DocumentServices: 22.2.0.226
  • EZ Config:
    • EZConfig Packages and Packets version: 2023.10.0.3081
    • EZConfig Default Data version: 2023.10.0.531
    • EZ Config Service version: 2023.10.0.666
    • EZ Gateway version: 2023.10.0.673
  • Databases:
    • Document Generation Services Database version: 22.2.0.4577
    • Packages and Packets Database version: 2023.10.0.3081
    • Default Database version: 2023.10.0.531
    • Security Administration Database version: 6.1.0.1483
    • Expere Document Services Database version: 22.2.0.2015

Installation / Upgrade Notes

Note the following installation and upgrade changes in the November release:

  • Transform variable changes:
    • EDSToolSuiteTransformVar
  • Octopus variable changes:
    • NA
  • Installation and upgrade changes:
    • New Expere Document Services Tool Suite installation step
      • Package ID: WoltersKluwerFS.EDS.ToolSuite.Installer
  • WSDL Changes:
    • NA
Octopus Deploy: new EDS Tool Suite transform variable added
Summary: As part of an internal Wolters Kluwer feature to modernize our existing Expere Document Services code base, we have created a new EDS Tool Suite transform variable (EDSToolSuiteTransformVar) that is part of the overall EDS installation process, including a new step in the overall Octopus Deploy installation procedure. See links above for more information.
Document Generation Services: WSDL updated to support SmartDoc element
  • Type: Enhancement
  • Reference: PBI 791593
  • User Impacts: Users must update their WSDL to accept this change.
Summary: The Document Generation Services (DocumentServices) WSDL has been updated to include a new SmartDoc element within the DocDescriptor container, which provides additional definition for the requested document; the SmartDoc element will contain a string of alphanumeric characters used to incidate the SmartDoc document version. The value should be "1.02." For more information, see Document Generation Services Web Services Guide > DocDescriptor.
OPPSA database tables, installation, and OD variables removed from Document Generation Services
Summary: As part of our feature to remove OPPSA functionality from Document Generation Services (see OPPSA functionality removed from Self-hosted Expere, Hosted Expere, and Documentation Generation Services applications below), we have removed references to all OPPSA database tables, installations, and OD variables.
DGS Tool Suite: SmartSign Web credentials issue resolved
  • Type: Defect
  • Reference: PBI 793453
Issue: It was reported that only the SmartSign Web MERS eVault Credentials and Non-MERS eVault Credentials sections groups were available for data entry in the Document Generation Services Tool Suite > SETUP page. The SmartSign Web Test on Demand and SmartSign Web Preview on Demand sections only displayed after data was entered into the former groups, saved, and SETUP page reopened for the same account.
Solution: This behavior has been addressed; all SmartSign Web sections are now available for a given account when accessing the SETUP page.
Expere: Engine updated to use Amazon Corretto Java 17 for use with WildFly
Summary: The Expere Engine has been updated to use Amazon Coretto Java 17 when using Wildfly.
DocViewer: new Support Required Data parameter added
Summary: DocViewer has been enhanced to determine if required documents should be available for viewing in the Document Drawer. This functionality is enabled when passing in a SupportRequiredData=yes parameter through BeginSessionRequest. When this parameter is passed in the request, only those documents that are considered "Required" are available for viewing in the Document Drawer.

October

This release utilizes the following Nuget Packages:
  • Document Generation Services version: 22.2.0.4497
  • Expere Engine version: 23.3.0.5274
  • DocViewer version: 23.1.0.940
  • Document Generation Services Core version: 23.1.0.113
  • Document Generation Services Core DocViewer version: 23.1.0.113
  • Security Administration version: 6.1.0.1462
  • Expere Document Services: 22.2.0.1943
  • DocumentServices: 22.2.0.218
  • EZ Config:
    • EZConfig Packages and Packets version: 2023.9.0.3066
    • EZConfig Default Data version: 2023.9.0.500
    • EZ Config Service version: 2023.9.0.626
    • EZ Gateway version: 2023.8.0.638
  • Databases:
    • Document Generation Services Database version: 22.2.0.4497
    • Packages and Packets Database version: 2023.9.0.3066
    • Default Database version: 2023.9.0.500
    • Security Administration Database version: 6.1.0.1462
    • Expere Document Services Database version: 22.2.0.1863

Installation / Upgrade Notes

Note the following installation and upgrade changes in the October release:

  • Transform variable changes:
    • NA
  • Octopus variable changes:
    • NA
  • Installation and upgrade changes:
    • NA
  • WSDL Changes:
    • NA
Expere: option to specify Barcode Height for transaction barcodes - additional updates
Summary: The Expere Engine has been enhanced to support a specified transaction barcode height through the use of a new "Height" element in the Requirements Editor. This new element value is modified in the Requirements Editor and can be used with Barcode PDF 417.
Note: A previous release included functionality for Barcode Inter 25, Barcode 3 of 9, and Barcode 128. QR Barcode is not supported with Transaction Barcodes.
Note: If changing the barcode height, it is recommended to test with scanning software to ensure readability.
Engine: Merging with duplicate feename behavior Additional enhancements
Summary: We previously enhanced the Engine to support duplicate account-level fees (see Expere: Merging with duplicate feename behavior enhanced). This behavior has been augmented to support the following:
  • Multiple accounts and their associated products (PBI 781761): if a minimum balance fee with the same /NameDesc and / or account fees with the same /FeeName are present in a policy, multiple accounts and their associated products (one product per account) now merge duplicate fees in the order specified in the policy.
  • When XPath data exists in Expere transaction (PBI 784661): Expere has been enhanced so that when data exists for the Xpath's below in the Expere transaction but also exists within incoming EZ Config data, the Expere transaction data will be present in the merged transaction and / or generated PDF.
    • /Txn/Deposit/Accounts/Account/Fees/
    • /Txn/Deposit/Accounts/Account/MinimumBalanceFees/
Expere: special characters supported in barcode value when applied by a mask in %docname%
  • Type: Enhancement
  • Reference: PBI 740517
Summary: It was reported that document generation fails when an ancillary barcode value utilizing %docname% (instance display name) contains a DTA with the "$1,234.50" output format. Analysis determined that special characters (i.e. “$”) being applied by the output format (i.e. “$1,234.50”) was not being handled properly. Expere has been enhanced so that ancillary barcodes containing special characters (i.e "$") being applied by an output format (i.e. “$1,234.50”) result in successful document generation with the appropriate barcode value.
Expere: option to specify Barcode Height for transaction barcodes - additional updates
Summary: The Expere Engine has been enhanced to support a specified transaction barcode height through the use of a new "Height" element in the Requirements Editor. This new element value is modified in the Requirements Editor and can be used with Barcode PDF 417.
Note: A previous release included functionality for Barcode Inter 25, Barcode 3 of 9, and Barcode 128. QR Barcode is not supported with Transaction Barcodes.
Note: If changing the barcode height, it is recommended to test with scanning software to ensure readability.
Engine: Apache FOP version in Adobe Acrobat displayed for merged PDF documents
Summary: Per user request, we have enhanced the Expere Engine to populate an Adobe Acrobat PDF properties with the Apache FOP version that was used to generate the PDF in a merged PDF document. The PDF Producer field accessible through Adobe Acrobat > Document Properties dialog box > Description tab displays the FOP version for individual PDF documents, for merged PDF documents, it displays the iText version.

Users can now view the FOP version used for merged PDF documents in the Document Properties dialog box > Custom tab; the FOP version will appear under the Value column for each document.

DocViewer: scrolling behavior updated
  • Type: Enhancement
  • Reference: PBI 772637
Summary: When clicking on the “Additional Appointment of Agents” field in the Data Entry drawer (left-hand pane), it did not advance to the corresponding location in the Document Display (body of the document in DocViewer). This behavior has been modified so that DocViewer now scrolls correctly to the correct location in the document.

September

This release utilizes the following Nuget Packages:
  • Document Generation Services version: 22.2.0.4497
  • Expere Engine version: 23.3.0.5176
  • DocViewer version: 23.1.0.933
  • Document Generation Services Core version: 23.1.0.113
  • Document Generation Services Core DocViewer version: 23.1.0.113
  • Security Administration version: 6.1.0.1454
  • Expere Document Services: 22.2.0.1896
  • DocumentServices: 22.2.0.218
  • EZ Config:
    • EZConfig Packages and Packets version: 2023.8.0.3043
    • EZConfig Default Data version: 2023.8.0.470
    • EZ Config Service version: 2023.8.0.620
    • EZ Gateway version: 2023.8.0.627
  • Databases:
    • Document Generation Services Database version: 22.2.0.4497
    • Packages and Packets Database version: 2023.8.0.3043
    • Default Database version: 2023.8.0.470
    • Security Administration Database version: 6.1.0.1454
    • Expere Document Services Database version: 22.2.0.1863

Installation / Upgrade Notes

Note the following installation and upgrade changes in the September release:

  • Transform variable changes:
    • NA
  • Octopus variable changes:
    • NA
  • Installation and upgrade changes:
    • NA
  • WSDL Changes:
    • NA
Expere: new Augment Transaction functionality supported
Summary: The Augment Transaction file provides the ability to author logic for setting an XPath value based on the transaction xml and have the transaction xml updated (augmented) prior to autoselection and document generation. For example: the value of /Txn/Notes/Note/NoteCommercialsStandardType can be set in the AugmentTransaction file based on other XPaths in the transaction xml. Then /Txn/Notes/Note/NoteCommercialsStandardType’s value can be referenced in PTRs verses repeating the logic defined in the Augment Transaction file in the numerous PTRs throughout the content. Expere can update, or "augment" an incoming request if the transaction xml contains an /Txn/AugmentTransactionInd = true element and value. When this value is provided, Expere resolves the XPath(s) in the related line of business Augment Transaction file based on the transaction XML and sets the XPath(s) in the transaction. Remaining autoselection logic is employed and documents are generated. This functionality can be utilized with content packages or EZ Config Packages and Packets’ Packages.
  • (PBI 775874) From an application standpoint, DocViewer has been updated to support this new Augment Transaction functionality using the logic outlined above. There is no setup required by the user.
Note: In order to utilize this feature, users must consume an updated base content package that supports this feature. The content used with this feature must have been built with version 23.3 or newer.
OPPSA references removed from Hosted Expere and Document Generation Services applications; user documentation updated for Expere On-Prem, Hosted Expere, and Document Generation Services
Summary: We have removed references to OPPSA-related components in our user documentation. Actual OPPSA references in our software code, including the WSDL, will be removed from our Expere On-Prem, Hosted Expere, and Document Generation Services products in the following releases:
  • Expere On-Prem: a future release
  • Hosted Expere, Document Service, and Document Generation Services: September 2023
Note: Expere has not supported OPPSA since Fall 2021.
Expere Testing System: Login, Fully Assembled XML, and Compare functionality removed
Summary: After analysis of the functionality usage within the Expere Testing System, the following tabs and corresponding functionality have been removed:
  • Login page
  • Fully Assembled XML
  • Compare
Expere: Electronic signings enhanced when Signer Name is unknown - all party types
Summary: The Expere Engine has been updated to set the value for <SignatureText> to an underscore ('_') in the Expere response when the party type does not have a Name value in the transaction request (and is not determined until the actual signing process; for example: a notary or witness).
Expere: option to specify Barcode Height added for transaction barcodes
Summary: The Expere Engine has been enhanced to support a specified transaction barcode height through the use of a new "Height" element in the Requirements Editor. This new element value is modified in the Requirements Editor and can be used with the following barcode types:
  • Barcode Inter 25
  • Barcode 3 of 9
  • Barcode 128
Expere: Dynamic documents enhanced when using radio buttons / GroupIDs with a merged PDF
Summary: When generating Dynamic documents into a merged PDF containing radio buttons (mutually exclusive checkboxes), fields were not named uniquely across the individual documents within the merged PDF. This behavior has been enhanced for Dynamic documents using radio buttons with GroupIDs. As a result, Expere now sets the GroupIDs uniquely between different document instances when a PdfMerge or MergeCopyPDF ancillary output is specified by appending "_#" to existing field names (UniqueName _#; for example: "OfferGroup_1").
Expere: Engine updated to use Amazon Corretto Java 8 for WildFly and Expere .NET
  • Type: Enhancement
  • Reference: PBI 787459
Summary: The Expere Engine has been updated to use the latest version of Amazon Coretto Java 8 (8.382.05.1 as of this release) when using either Wildfly or Expere.NET.
Engine: BSI.Properties acroformSupport property and eSignatureAndFieldSupport ancillary output behavior resolved
Issue: It was discovered during the course of testing a related issue that when the BSI.Properties acroformSupport property was set to "false" and the eSignatureAndFieldSupport ancillary output was not passed in a transaction request that certain field lines, checkboxes, and radio buttons would not appear in the resulting Dynamic PDF document.

Solution: This issue has been resolved: fillable fields, checkboxes, and radio buttons appear on Dynamic PDF documents when BSI.Properties acroformSupport is set to "false" and eSignatureAndFieldSupport is not passed in the transaction request.
Engine: Saxon component change
  • Type: Enhancement
  • Reference: PBI 786126
Summary: The Expere Engine uses Saxon as its XSLT processer. Internal analysis determined that a recent Saxon upgrade for use with the Expere Engine was unnecessary at this time. As a result, we have changed the version of Saxon used by the Expere Engine to 9.9.1-7.
DocViewer: Supports Mortgage content with additional customer organizations
  • Type: Enhancement
  • Reference: PBI 788486
Summary: DocViewer supports using Mortgage content and using two different customer organizations with the same base content.

August

This release utilizes the following Nuget Packages:
  • Document Generation Services version: 22.2.0.4458
  • Expere Engine version: 23.3.0.5100
  • DocViewer version: 23.1.0.926
  • Document Generation Services Core version: 23.1.0.113
  • Document Generation Services Core DocViewer version: 23.1.0.113
  • Security Administration version: 6.1.0.1421
  • Expere Document Services: 22.2.0.1847
  • DocumentServices: 22.2.0.216
  • EZ Config:
    • EZConfig Packages and Packets version: 2023.7.0.3030
    • EZConfig Default Data version: 2023.7.0.453
    • EZ Config Service version: 2023.7.0.590
    • EZ Gateway version: 2023.7.0.618
  • Databases:
    • Document Generation Services Database version: 22.2.0.4458
    • Packages and Packets Database version: 2023.7.0.3030
    • Default Database version: 2023.7.0.453
    • Security Administration Database version: 6.1.0.1421
    • Expere Document Services Database version: 22.2.0.1847

Installation / Upgrade Notes

Note the following installation and upgrade changes in the August release:

DGSCore and DGS Core DocViewer transform updates
Summary: As part of a Wolters Kluwer feature to utilize reference tokens, the DGSCoreTransformVar and DGSCoreDocViewerTransformVar transform variables have been updated to include the following properties:
  • <Property Id="DGSCORE.ApiResourceId" Value="wk-dgs-core" />
  • <Property Id="DGSCORE.ApiResourceSecret" Value="xxxxxxxxxxxxxxxxxxxxxxx" />
Tool Suite: scrubbed data enhancements
  • Type: Enhancement
  • Reference: PBI 778644
Summary: The Document Generation Services Tool Suite contains the ability to scrub certain information from a customer's transaction, such as social security numbers, email addresses, etc. The data that resides in a customer's transaction has been reviewed and updates made as of July, 2023.
Expere: Merging with duplicate feename behavior enhanced
Summary: It was reported that when duplicate fee names for /Txn/Deposit/Accounts/Account/Fees/Fee/FeeName and /Txn/Deposit/Accounts/Account/MinimumBalanceFees/MinimumBalanceFee/NameDesc existed in Expere EZ Config Default Data, a resulting merge into the Expere transaction only presented the last instance of the duplicated fee name / value. The expected behavior is that duplicate fee names should be present within a merged Expere transaction and in the order that they were entered in Expere EZ Config Default Data. Expere has been enhanced to support the present of multiple, duplicated fee names in a merged transaction.
Note: Fees are merged only if the Expere transaction does not contain these fees. If the Expere transaction does contain these fees, the fees will not merged with the Expere transaction.
Note:

This enhancement also resolved the following issue:

A product containing two stepped rates with identical terms resulted in only one of the stepped rates being merged with Expere transaction data.

User action: it is recommended that users resave the Default Data policy and reattempt the Default Data and Expere transaction data merge (It was determined that saving the policy added an index thus merging the data successfully).
DocViewer: caching protocol updated
  • Type: Enhancement
  • Reference: PBI 771907
Summary: DocViewer has been enhanced to only cache those documents that are autoselected, rather than all documents for a particular package.
DocViewer: date output format behavior enhanced
  • Type: Enhancement
  • Reference: PBI 770620
Summary: DocViewer has been updated to support additional date output formats to match the generated PDF document. For example, instead of a dd/mm/yyyy format as "07/06/2023," it appeared instead as "20230607."

July

This release utilizes the following Nuget Packages:
  • Document Generation Services version: 22.2.0.4434
  • Expere Engine version: 23.3.0.5071
  • DocViewer version: 23.1.0.921
  • Document Generation Services Core version: 23.1.0.110
  • Document Generation Services Core DocViewer version: 23.1.0.110
  • Security Administration version: 6.1.0.1398
  • Expere Document Services: 22.2.0.1831
  • DocumentServices: 22.2.0.216
  • EZ Config:
    • EZConfig Packages and Packets version: 2023.6.0.3017
    • EZConfig Default Data version: 2023.6.0.428
    • EZ Config Service version: 2023.6.0.569
    • EZ Gateway version: 2023.6.0.614
  • Databases:
    • Document Generation Services Database version: 22.2.0.4434
    • Packages and Packets Database version: 2023.6.0.3017
    • Default Database version: 2023.6.0.428
    • Security Administration Database version: 6.1.0.1398
    • Expere Document Services Database version: 22.2.0.1831

Installation / Upgrade Notes

Note the following installation and upgrade changes in the July release:

  • Transform variable changes:
    • NA
  • Octopus variable changes:
    • NA
  • Installation and upgrade changes:
    • NA
  • WSDL Changes:
    • Document Generation Services: See PBI 772862
Document Generation Services users / integrators: <LinkToSignerIdentifier/> mapped
Summary: Previously, we added a new <LinkToSignerIdentifier/> element to the DGS DocumentServices WSDL to be returned in the Expere Response file. The purpose of PBI 772862 is to map the element in order for Notary and Witness signers to be associated with a known party.
Integrators: OPTIONAL database encryption process updated
Summary: Document Generation Services (DGS) has been enhanced to support an updated optional database encryption process for those users interested in enabling or disabling encryption for Expere Document Services, DGS, DGSCore, and DocViewer.
DocViewer: Date display behavior addressed in DATA Entry drawer
  • Type: Enhancement
  • Reference: PBI 772700
Summary: Users reported that when entering date information in the DATA Entry drawer (left fly-out panel) using the calendar display, then clicking out of that calendar display and corresponding field, the value entered was not preserved. Note that this behavior was only exhibited when the Track XPath flag was enabled.

DocViewer has been enhanced so that the date is now preserved when using the calendar function.

Document Service: log file messaging enhanced
  • Type: Enhancement
  • Reference: PBI 774657
Summary: As part of a continued effort to improve our logging capabilities, the Account Number and ContentIdentifier have been added to the Elapsed time log entry; for example:
[INF] Elapsed time to complete generate-synchronous for EDSId 1163 (Account: 1, ContentIdentifier: BaseLibrary.PKG.Deposit): 00:00:02.8931185

June

This release utilizes the following Nuget Packages:
  • Document Generation Services version: 22.2.0.4412
  • Expere Engine version: 23.2.0.5043
  • DocViewer version: 23.1.0.919
  • Document Generation Services Core version: 23.1.0.107
  • Document Generation Services Core DocViewer version: 23.1.0.107
  • Security Administration version: 6.1.0.1387
  • Expere Document Services: 22.2.0.1828
  • DocumentServices: 22.2.0.207
  • EZ Config:
    • EZConfig Packages and Packets version: 2023.5.0.3013
    • EZConfig Default Data version: 2023.5.0.416
    • EZ Config Service version: 2023.5.0.514
    • EZ Gateway version: 2023.5.0.609
  • Databases:
    • Document Generation Services Database version: 22.2.0.4412
    • Packages and Packets Database version: 2023.5.0.3013
    • Default Database version: 2023.5.0.416
    • Security Administration Database version: 6.1.0.1387
    • Expere Document Services Database version: 22.2.0.1828

Installation / Upgrade Notes

Note the following installation and upgrade changes in the June release:

  • Transform variable changes:
    • NA
  • Octopus variable changes:
    • NA
  • Installation and upgrade changes:
    • NA
  • WSDL Changes:
Document Generation Services DocumentServices WSDL UPDATED with new <LinkToSignerIdentifier>
Summary: Expere has been enhanced to support associating Notaries and Witnesses with a known signer to make the entire signing process eSignable. As a result, we have added a new <LinkToSignerIdentifier/> element to the <SignaturePoint/> container in the DGS DocumentServices WSDL. The value in this new element will utilize the same value used in the <Signer/> > <ID/> element, which is the value of the signer ID.

Example response snippet below:


<r:SignaturePointSet>
    <r:Signer>
        <r:Id>null</r:Id>
        <r:Description>Notary</r:Description>
            <r:SignaturePoints>
                <r:SignaturePoint>
                    <r:IncludeDate>true</r:IncludeDate>
                    <r:PageNumber>26</r:PageNumber>
                    <r:PageOrder>1</r:PageOrder>
                    <r:Height>36.0</r:Height>
                    <r:Width>162.0</r:Width>
                    <r:SignatureText>_</r:SignatureText>
                    <r:XCoordinate>94.6</r:XCoordinate>
                    <r:YCoordinate>570.58</r:YCoordinate>
                    <r:Type>Signature</r:Type>
                    <r:FieldName>SIG_Notary_0___true_1</r:FieldName>
                    <r:Sequencing>42</r:Sequencing>
                    <r:SignatureRequired>true</r:SignatureRequired>
                    <r:SignatureUniqueIdentifier>NotaryBlockSection1</r:SignatureUniqueIdentifier>
                </r:SignaturePoint>
            </r:SignaturePoints>
        <r:LinkToSignerIdentifier>C1O1</r:LinkToSignerIdentifier>
    </r:Signer>
</r:SignaturePointSet>
Management Tool: additional validation when associating an alias
Summary: The Document Generation Services Management Tool has been enhanced to incorporate validation into the alias assigning process. As a reminder, an alias is a shorthand name path and is beneficial so that an API call does not need to understand the naming convention/URI that is used within Document Generation Services (DGS). An alias can be defined as a URL that is common to the requesting application’s language/configuration, and can then be re-interpreted to call the content library that they intend to call. The additional validation verifies the following criteria:
  • Determine whether the library exists
  • The alias destination value should contain a prepend of "expere://" (for example: 01266790.PKG.Mortgage2Closing
  • Should contain a "$"
  • Verify if the organization name is valid and is a valid library

If any of these conditions cannot be satisfied, an error message appears.
DocViewer: eSignature field behavior enhanced with Embedded PDFs
  • Type: Enhancement
  • Reference: PBI 768237
Summary: It was reported that the Product Technical Rules (PTR) used to generate certain data within an .REQ file were appearing in eSignature fields in DocViewer. This behavior has been enhanced so that no PTR code appears in the eSignature fields.
DocViewer: InstanceDisplayName behavior enhanced for Embedded PDF documents
  • Type: Enhancement
  • Reference: PBI 767182
  • Documentation Impacts: No documentation impact
Summary: It was reported that when viewing documents in DocViewer, the Form to View First dropdown did not display a form name, which is derived from the InstanceDisplayName in the requirements (.REQ file). As a result, DocViewer has been enhanced to display the InstanceDisplayName in the Form to View First dropdown.
DocViewer Integrators: Audit feature functionality added
Summary: As part of our EZ Config Audit feature functionality, DocViewer has been enhanced to include a new <Prompt> element in the EndSession response.
Note: This is an internal change and will not impact external users. No user action is required.
Hosted Expere / Document Services integrators: <LinkToSignerIdentifier/> mapped
Summary: As part of our feature to support associating Notaries and Witnesses with a known or unknown signer to make the entire signing process eSignable, we have enhanced the following API's (depending on SOAP or REST usage)
  • Hosted Expere (DocServices / SOAP, PBI 772872): Previously, we added a new <LinkToSignerIdentifier/> element to the DocServices WSDL to be returned in the Expere Response file. We have now mapped this new element in order to achieve complete functionality.
  • Hosted Expere (DocumentService / REST PBI 772873): we have updated the SignaturePoint property to include a new LinkToSignerIdentifer element that will be returned in the Expere Response file; no user action is required.
Hosted Expere integrators: DocServices WSDL UPDATED with new <LinkToSignerIdentifier>
Summary: Expere has been enhanced to support associating Notaries and Witnesses with a known or unknown signer to make the entire signing process eSignable. As a result, a new <LinkToSignerIdentifier/> element has been added to the <SignaturePoint/> container in the EDS DocServices WSDL. This element associates a known signer with a notary or witness and uses the same value as the in-scope signer ID.
Note: A corresponding content update is required in order to use this functionality. There is no user action at this time.

Example Notary response snippet:


<r:Signer>
	<r:Id>null</r:Id>
	<r:Description>Notary</r:Description>
	<r:SignaturePoints>
		<r:SignaturePoint>
			<r:IncludeDate>false</r:IncludeDate>
			<r:PageNumber>19</r:PageNumber>
			<r:PageOrder>1</r:PageOrder>
			<r:Height>36.0</r:Height>
			<r:Width>198.0</r:Width>
			<r:SignatureText>_</r:SignatureText>
			<r:XCoordinate>93.6</r:XCoordinate>
			<r:YCoordinate>190.44</r:YCoordinate>
			<r:Type>Signature</r:Type>
			<r:FieldName>SIG_Notary_0__true_1</r:FieldName>
			<r:Sequencing>2</r:Sequencing>
			<r:SignatureRequired>true</r:SignatureRequired>
			<r:LinkToSignerIdentifier>b1</r:LinkToSignerIdentifier>
		</r:SignaturePoint>
	</r:SignaturePoints>
</r:Signer>

Example Witness response snippet:


<r:Signer>
	<r:Id>b1-witness</r:Id>
	<r:Description>Witness</r:Description>
	<r:SignaturePoints>
		<r:SignaturePoint>
			<r:IncludeDate>false</r:IncludeDate>
			<r:PageNumber>19</r:PageNumber>
			<r:PageOrder>1</r:PageOrder>
			<r:Height>36.0</r:Height>
			<r:Width>198.0</r:Width>
			<r:SignatureText>_</r:SignatureText>
			<r:XCoordinate>93.6</r:XCoordinate>
			<r:YCoordinate>190.44</r:YCoordinate>
			<r:Type>Signature</r:Type>
			<r:FieldName>SIG_Witness_0_b1-witness_true_1</r:FieldName>
			<r:Sequencing>2</r:Sequencing>
			<r:SignatureRequired>true</r:SignatureRequired>
			<r:LinkToSignerIdentifier>b1</r:LinkToSignerIdentifier>
		</r:SignaturePoint>
	</r:SignaturePoints>
</r:Signer>
Engine: Barcode processing flow updated for upcoming iText upgrade
  • Type: Enhancement
  • Reference: PBI 762635
Summary: Internal analysis has determined that an upcoming iText upgrade would impact the way barcodes function within the Expere Engine. As a result, barcode processing has been updated within Expere to accommodate an upcoming iText upgrade.
Note: This upgrade will not affect integrations or generated documents.
Engine: Encryption behavior enhanced
Summary: Previously, a transaction using an Encryption ancillary output and containing a combination of RTF and PDF document options would fail as Encryption can only be applied to PDF documents. Expere has been enhanced so that while an Encryption ancillary output can still only be applied to PDF documents, the transaction will not fail and a document package can be generated.
Engine: Notary fillable field behavior enhanced
Summary: It was reported that despite the electronic signature ("eSignature") for a borrower being suppressed, and thus unable to be electronically signed, the fields in the Notary section within the same document appeared as fillable in the generated PDF. The expected behavior is that when signatures are "wet sign", the notary and all associated fields should not appear as fillable. Additionally, the presence of <SuppressESignature/> in a particular element (for example: a Notary section) within the .REQ file will result in those fields not appearing as fillable.

May

This release utilizes the following Nuget Packages:
  • Document Generation Services version: 22.2.0.4387
  • Expere Engine version: 23.2.0.4935
  • DocViewer version: 23.1.0.897
  • Document Generation Services Core version: 23.1.0.99
  • Document Generation Services Core DocViewer version: 23.1.0.99
  • Security Administration version: 6.1.0.1213
  • Expere Document Services: 22.2.0.1785
  • DocumentServices: 22.2.0.167
  • EZ Config:
    • EZConfig Packages and Packets version: 2023.1.0.2988
    • EZConfig Default Data version: 2023.1.0.373
    • EZ Config Service version: 2023.1.0.472
    • EZ Gateway version: 2023.1.0.569
  • Databases:
    • Document Generation Services Database version: 22.2.0.4366
    • Packages and Packets Database version: 2023.1.0.2988
    • Default Database version: 2023.1.0.373
    • Security Administration Database version: 6.1.0.1213
    • Expere Document Services Database version: 22.2.0.1785

Installation / Upgrade Notes

Note the following installation and upgrade changes in the May release:

  • Transform variable changes:
    • See PBI 763582 below.
  • Octopus variable changes:
    • See PBI 763582 below.
  • Installation and upgrade changes:
    • See PBI 763582 below.
WCAG 2.0: Expere Engine enhanced to support embedded and Tagged .PDF's - May
  • Type: Enhancement
  • Reference: PBI 760512, 768023, 729340, 765661, 764256, 767178
  • Documentation Impacts: See below for any pertinent links.
Summary: As a part of our continued effort to create WCAG 2.0 compatible documents we have updated the Expere Engine to now support the generation of Tagged .PDF documents. We will continue making enhancements to the Expere Engine for Tagged .PDF support, so check back for items being identified and corrected. As part of our continued work to support Tagged .PDF's, we have implemented enhancements to resolve the following WCAG 2.0-related changes in the May release:
  • Embedded PDF - Barcodes supported on multiple page Embedded PDF documents (PBI 760512): Expere has been updated to produce barcodes on multiple page embeddedPDF REQ files. The requested barcode (ancillary or transaction barcode) will be present on each page where the Form_Barcode[] fields are present. If no barcode is requested, the document generates without the barcode and Form_Barcode[] fields removed.
  • Embedded PDF - Enhanced Barcode/Cover Page functionality (PBI 768023): Expere has been enhanced so the Adobe Acrobat tag tree in the resulting Tagged PDF is correct and passes the Accessibility Check when using a barcode or barcode cover page.
  • Dynamic - linking enhancement (PBI 729340): Previously, Adobe Acrobat tag tree and reading order issues occurred when two locations utilized an "*" to link to additional text; only the first instance that used the "*" appeared as a tags in the tag tree. The second instance did not appear in the tag tree. Users should expect to see the following in the tag tree:
    • The text in the body of the tagged PDF document using a "*" and the linked text containing the footnote
    • Multiple instances of the aforementioned body text and linked text

    This behavior has been enhanced to now display multiple instances of text containing a "*" and the linked text in the Adobe Acrobat tag tree when the REQ is updated to name each of the linked text so that Expere can differentiate between two or more Linked texts with the same display value.

    Note:
    • Users must update their content libraries and files in order to utilize the new LinkName attribute.
    • For more information on linking text in the Requirements Editor, refer to the following help topic: Authoring Superscripts Using LinkText/LinkReference for PDF Tagging.
    • In order to use the new LinkName attribute, users should ensure they are using content stylesheet version 22.8 or later.
  • Dynamic - Tagged PDF updated to support PdfMerge and MergeCopyPDF (PBI 765661): Expere has been enhanced so that when generating a tagged PDF from multiple dynamic REQ files using the PdfMerge and MergeCopyPDF ancillary outputs, fillable fields appear in the tag tree in the order they appear in the merged PDF document.
  • Embedded PDF - fillable checkboxes checked by default (PBI 767178): it was identified that fillable checkboxes were selected by default when generating an Embedded PDF REQ document. The Engine has been enhanced so that when generating an Embedded PDF REQ document, a fillable checkbox is ONLY selected if the corresponding PTR in the REQ file results in PRINT "Checked:true;".
    Note: In the REQ file, a fillable checkbox PTR will contain the following syntax if a checkbox is checked by default when generating a document: PRINT "Checked:true;"; an unchecked checkbox will either contain no syntax or the following syntax: PRINT "Checked:false;".
Engine: fillable checkboxes checked by default with static documents
  • Type: Enhancement
  • Reference: PBI 767178
Summary: it was identified that fillable checkboxes were selected by default when generating a Static document. The Engine has been enhanced so that when generating a Static document, a fillable checkbox is ONLY selected if the corresponding PTR in the REQ file results in PRINT "Checked:true;".
Note: In the REQ file, a fillable checkbox PTR will contain the following syntax if a checkbox is checked by default when generating a document: PRINT "Checked:true;"; an unchecked checkbox will either contain no syntax or the following syntax: PRINT "Checked:false;".
Engine: SelectAndGenerate call behavior enhanced
  • Type: Enhancement
  • Reference: PBI 768197
Summary: A user reported that a transaction failed to generate and return documents with a SelectAndGenerate method. Internal analysis determined that an Expere assembly service incorrectly handled a unique ID that was present within the content library. Expere has been enhanced so that internally, any unique ID present in a document package is handled so that the package generates successfully.
Engine: Show dropdown / File Name behavior enhanced
  • Type: Enhancement
  • Reference: PBI 764341
Summary: It has been identified that when generating a dynamic document with the most recent version of FOP (2.8) as a standard PDF, Document Title value (found in Adobe Acrobat > Document Properties > Initial View > Show dropdown) is specified rather than the File Name value. Expere has been enhance to specify the File Name value when generating a standard PDF using the most recent version of FOP (2.8) from a dynamic REQ file.
Engine: Borrower element naming convention enhanced for SMARTDocs
Summary: To work more consistently with eOriginal workflows, Expere has updated the SignatureIDRef naming convention to use _RoleType's value plus _SignatureOrderNumber's value plus the text of 'SignatureLine' within the <SIGNATURE_MODEL> for each signer; for example: the SignatureIDREF="Borrower1SignatureLine", SignatureIDREF="Borrower2SignatureLine").
Expere: SmartSign Plus® Integration
Summary: As part of our feature to integrate Expere with eOriginal SmartSign Plus®, we have updated the Document Generation Services Tool Suite SETUP page so that checking a new checkbox in the SmartSign+ Credentials section enables the use of SmartSign+; unchecking this checkbox enables the use of SmartSign Web.

April

This release utilizes the following Nuget Packages:
  • Document Generation Services version: 22.2.0.4366
  • Expere Engine version: 23.2.0.4935
  • DocViewer version: 23.1.0.897
  • Document Generation Services Core version: 23.1.0.99
  • Document Generation Services Core DocViewer version: 23.1.0.99
  • Security Administration version: 6.1.0.1213
  • Expere Document Services: 22.2.0.1785
  • DocumentServices: 22.2.0.167
  • EZ Config:
    • EZConfig Packages and Packets version: 2023.1.0.2988
    • EZConfig Default Data version: 2023.1.0.373
    • EZ Config Service version: 2023.1.0.472
    • EZ Gateway version: 2023.1.0.569
  • Databases:
    • Document Generation Services Database version: 22.2.0.4366
    • Packages and Packets Database version: 2023.1.0.2988
    • Default Database version: 2023.1.0.373
    • Security Administration Database version: 6.1.0.1213
    • Expere Document Services Database version: 22.2.0.1785

Installation / Upgrade Notes

Note the following installation and upgrade changes in the April release:

  • Transform variable changes:
    • See PBI 763582 below.
  • Octopus variable changes:
    • See PBI 763582 below.
  • Installation and upgrade changes:
    • See PBI 763582 below.
Expere: SmartSign Plus® Integration
Summary: As part of our feature to integrate Expere with eOriginal SmartSign Plus®, we have updated the Document Generation Services Tool Suite SETUP page to accept SmartSign Plus® login credentals through the creation of a new SmartSign+ Credentials section.
OD installation process enhanced for use with STSv6
  • Type: Enhancement
  • Reference: PBI 763582
  • Documentation Impacts: see Document Generation Services OD Install Guide links below.
Summary: We communicated to users over the last several months that our authentication and authorization application, STS, was being upgraded to a new version. As part of this culmination, the following information related to STSv6 has been updated with the Document Generation Services Octopus Deploy (OD) process:
Management Tool: Copy Packages to child ORGs' option removed
Summary:As part of an overall effort to support "pre-built" (also referred to as "built") content in our Document Generation Services library deployment process, the Copy Packages to child ORGs' option has been removed from the Deploy Library page.
Tool Suite: Aliases & Packages List Order updated
Summary: The list of available Aliases and Packages accessible when clicking the Generate button in the Content Identifier section has been updated to display the aliases in ascending order chronologically, and packages in alphabetical order.
Tool Suite: scrubbed data enhancements
  • Type: Enhancement
  • Reference: PBI 741409
Summary:

The Document Generation Services Tool Suite contains the ability to scrub certain information from a customer's transaction, such as social security numbers, email addresses, etc. The data that resides in a customer's transaction has been reviewed and updates made for 2023.
DocViewer: overlay behavior enhanced
  • Type: Defect
  • Reference: PBI 768371
Issue: DocViewer users reported that when using an overlay, suppression was not honored resulting in additional fields available for data entry.
Solution: This issue has been resolved: suppression is now being honored when using an overlay.
DocViewer: tabbing order behavior enhanced with embedded PDF documents
  • Type: Enhancement
  • Reference: PBI 766572
Summary: DocViewer has been enhanced when using an Embedded PDF to honor the tabbing order. As a result, the user can populate the information in the correct order. In addition the sums are also calculated in the proper order.
DocViewer: XPath Attributes behavior enhanced
  • Type: Enhancement
  • Reference: PBI 751602
Summary: A user reported that adding a custom XPath attribute resulted in an "[object Object]" value to display in an editable field rather than the actual value. As a result, DocViewer has been enhanced to support the use of custom XPath attributes: "[object Object]" no longer appears in a corresponding dropdown.
DocViewer: underline special characters behavior enhanced
  • Type: Enhancement
  • Reference: PBI 757168
Summary: A user reported that a discrepany existed in the way an underlined word appeared in DocViewer compared to a standard PDF. For example: in the REQ, a "product technical rule" (PTR) is used to add business logic and rules to underline the last name of the parties for a particular state using HTML code &lt;u&gt;"./LastName "&lt;/u&gt in the PTR to produce the underline. When generating a PDF, the state was underlined correctly. However, when using DocViewer, the HTML Code &lt;u&gt;LastName&lt;/u&gt appeared instead.

This behavior has been modified so that DocViewer will no longer display the HTML code used to add underlines.

DocViewer: entry behavior in Document Drawer and Document Display page enhanced
  • Type: Enhancement
  • Reference: PBI 762557
Summary: Users reported that a value selected from a dropdown list of items (for example: a list of States) in the Document Drawer did not match the value displayed in the Document Display page; a different state appeared instead of the state selected from Document Drawer. This was caused by users using the up/down keys to quickly advance to the state compared to using the dropdown selection. This behavior has been enhanced so that values selected from the Document Drawer matches that of the Document Display page.

March

This release utilizes the following Nuget Packages:
  • Document Generation Services version: 22.2.0.4349
  • Expere Engine version: 23.1.0.4919
  • DocViewer version: 23.2.0.883
  • Document Generation Services Core version: 22.3.0.89
  • Document Generation Services Core DocViewer version: 22.3.0.89
  • Security Administration version: 6.1.0.1043
  • Expere Document Services: 22.2.0.1728
  • DocumentServices: 22.2.0.167
  • EZ Config:
    • EZConfig Packages and Packets version: 2023.1.0.2978
    • EZConfig Default Data version: 2023.1.0.348
    • EZ Config Service version: 2023.1.0.449
    • EZ Gateway version: 2023.1.0.564
  • Databases:
    • Document Generation Services Database version: 22.2.0.4349
    • EZConfig Packages and Packets version: 2023.1.0.2978
    • Default Database version: 2023.1.0.348
    • Security Administration version: 6.1.0.1043
    • Expere Document Services Database version: 22.2.0.1728

Installation / Upgrade Notes

Note the following installation and upgrade changes in the March release:

  • Transform variable changes:
    • None
  • Octopus variable changes:
    • None
  • Installation and upgrade changes:
    • None
Expere Engine: updated to use WildFly 26.1.3
  • Type: Enhancement
  • Reference: PBI 761958
  • Documentation Impacts: No documentation impact
Summary: The Expere Engine has been updated to use Wildfly version 26.1.3. No user action is required.
DocViewer: XPath Attributes behavior enhanced
  • Type: Enhancement
  • Reference: PBI 751602
Summary: A user reported that adding a custom XPath attribute resulted in an "[object Object]" value to display in an editable field rather than the actual value. As a result, DocViewer has been enhanced to support the use of custom XPath attributes: "[object Object]" no longer appears in a corresponding dropdown.
DocViewer: messaging behavior enhanced
  • Type: Enhancement
  • Reference: PBI 756574
Summary: Users reported that when attempting to close a document within DocViewer, an "Are you sure you want to leave this page?" message appeared, implying that the user made a change in DocViewer even if no change had been made. As a result, we have enhanced DocViewer so that no message will appear if changes have not been made.
DocViewer: latency issues addressed
  • Type: Enhancement
  • Reference: PBI 758965
Summary: Users reported that the Authority document experienced considerable delay when loading the document and selecting fields in DocViewer. Internal analysis revealed that an unnecessary overlay dictionary was stored in the session when the session state was stored in SQL. Whenever a change was made, DocViewer retrieved the overlay dictionary, storing it in the session cache. This issue has been resolved: latency issues have been resolved in DocViewer.
DocViewer: Condition Behavior addressed
  • Type: Enhancement
  • Reference: PBI 743075
Summary: DocViewer has been enhanced to now display the prompt from the Xpath in a condition (COND.<x> authored in the .REQ file) if a note was not authored in the .REQ file. This prompt appears to right of the "+" / "-" sign in DocViewer.
DocViewer: incorrect formatting behavior enhanced
  • Type: Enhancement
  • Reference: PBI 662167
Summary: When a value was entered in DocViewer that resulted in an invalid character error, the file that tracked the XPath changes saved the invalid value rather than the NULL or the previous value. This behavior has been enhanced so that when an invalid character error appears, DocViewer does not track the invalid characters but rather the the original value in the on the EndSession page.

February

This release utilizes the following Nuget Packages:
  • Document Generation Services version: 22.2.0.4307
  • Expere Engine version: 23.1.0.4864
  • DocViewer version: 23.1.0.868
  • Document Generation Services Core version: 22.3.0.84
  • Document Generation Services Core DocViewer version: 22.3.0.84
  • Security Administration version: 6.0.1.908
  • Expere Document Services: 22.2.0.1728
  • DocumentServices: 22.2.0.167
  • EZ Config:
    • EZConfig Packages and Packets version: 2023.1.0.2956
    • EZConfig Default Data version: 2023.1.0.297
    • EZ Config Service version: 2023.1.0.421
    • EZ Gateway version: 2023.1.0.559
  • Databases:
    • Document Generation Services Database version: 22.2.0.4307
    • EZConfig Packages and Packets version: 2023.1.0.2956
    • Default Database version: 2023.1.0.297
    • Security Administration Database version: 6.0.1.908
    • Expere Document Services Database version: 22.2.0.1728

Installation / Upgrade Notes

Note the following installation and upgrade changes in the September release:

  • Transform variable changes:
    • None
  • Octopus variable changes:
    • None
  • Installation and upgrade changes:
    • Document Generation Services / Expere Document Services updated to .NET Framework 4.8
Document Generation Services / Expere Document Services updated to .NET Framework 4.8
Summary: As part of a Wolters Kluwer feature to "modernize" certain applications by separating services, refactoring code, and preparing for future architectural enhancements, we have updated Document Generation Services and Expere Document Services to now use Microsoft .NET Framework verion 4.8.
Expere Engine: database installation no longer supported with WildFly
  • Type: Enhancement
  • Reference: PBI 726689
  • Documentation Impacts: Document Generation Services OD Install Guide
Summary: Recently, our OPPSA product was retired; when used with the Expere Engine, OPPSA utilized a database. WIth this retirement, Expere no longer supports the use of a database when used with Document Generation Services.
Note: There is NO user action required.

JanuaryExternal release date is January.

This release utilizes the following Nuget Packages:
  • Document Generation Services version: 22.2.0.4305
  • Expere Engine version: 23.1.0.4809
  • DocViewer version: 23.1.0.861
  • Document Generation Services Core version: 22.3.0.84
  • Document Generation Services Core DocViewer version: 22.3.0.84
  • Security Administration version: 6.0.1.760
  • Expere Document Services: 22.2.0.1728
  • DocumentServices: 22.2.0.167
  • EZ Config:
    • EZConfig Packages and Packets version: 2022.11.0.2947
    • EZConfig Default Data version: 2022.11.0.274
    • EZ Config Service version: 2022.11.0.417
    • EZ Gateway version: 2022.11.0.557
  • Databases:
    • Document Generation Services Database version: 22.2.0.4305
    • Packages and Packets Database version: 2022.11.0.2947
    • Default Database version: 2022.11.0.274
    • Security Administration Database version: 6.1.0.760
    • Expere Document Services Database version: 22.2.0.1728

Installation / Upgrade Notes

Note the following installation and upgrade changes in the September release:

  • Transform variable changes:
    • None
  • Octopus variable changes:
    • None
  • Installation and upgrade changes:
    • DGSCore updated to .NET version 6.0
    • Document Service updated to .NET version 6.0
DGS: Support Package Name in Content URI
Summary: Document Generation Services had been previously updated in December to process a request that specifies the EZ Config Packages and Packets' "Package Name" or "Package ID" in the Content URI. For example: BaseLibrary.PKGPKT.160011 or BaseLibrary.PKGPKT.DepositAccountOpening

For the January release, we have updated the Select method to now specify the EZ Config Packages and Packets' "Package Name" or "Package ID" in the Content URI.

This previous update affected the SelectSynchronous, Generate, SelectAndGenerate, and ListDocuments methods.
Note: Do not use duplicate Package Names wthin a given alias across Lines of Business.