Changelog entries - 2022
This help topic encompasses enhancements and defect corrections covering the DocViewer application.
Note: The DocViewer 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 Expere Document 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.
September
| DocViewer: Sequencing Behavior Enhanced |
|---|
|
| Summary: DocViewer has been updated to ensure that the number sequencing used within a list continues across separate lists where intended without restarting the numbering at 1. |
| DocViewer: Embedded PDF field behavior enhanced |
|---|
|
|
Summary: Users reported that when generating an embedded .PDF file
for viewing in DocViewer, some field text was misaligned: overlap occurred
in some fields while values appeared in the wrong fields. This behavior has been enhanced; field text is aligned properly and appears in the correct fields |
| DocViewer / Embedded .PDF: Fillable Field appearance enhanced |
|---|
|
| Summary: Users reported that the Product Technical Rule (PTR) from the original authoring document (.REQ) was appearing in fillable fields within an embedded .PDF file in DocViewer. The PTR is considered background information using during the authoring process and should not appear. This behavior has been enhanced; DocViewer has been updated so that the Product Technical Rule does not appear in a fillable field. |
| DocViewer: table rendering behavior enhanced |
|---|
|
|
Summary: DocViewer users reported that document display did not match
that of a .PDF output when a file contained tables with a different number
of columns defined for different row. As a result, columns had shifted, and
a middle column was narrower than expected. The output of these DocViewer documents now matches that of a .PDF output. |
DocViewer: EndSession timeout
extended |
|---|
|
Summary: Users reported that DocViewer timed out when the following
occurred:
This behavior has been enhanced; we have extended our timeout time
to five (5) minutes when calling the |
| DocViewer: eNotary information hidden |
|---|
|
| Summary: DocViewer has been enhanced to no longer display the eNotary section. This enhancement was implemented so that the eNotary display behavior matched that of Signature section. |
| DocViewer: Cross-Origin issue identified and addressed |
|---|
|
|
Summary: Users reported receiving a "401" error when attempting to
access DocViewer in the Hosted Expere CT environment. Internal analysis
determined that the root cause stemmed from a cross-origin issue (commonly
referred to as "CORS") within DocViewer. As a result, DocViewer was rolled back to a previous version during the July CT deployment. |
August
Note: The August CT and Production deployments of DocViewer have
been canceled. All work items slated for August have been moved to the September
deployment.
July
Note: The July CT and Production deployments of DocViewer have
been canceled. All work items slated for July have been moved to the September
deployment.
June
Note: The production deployment is June has been canceled; all
work items originally slated for June have been moved to the September
deployment.
May
| Support discontinued for Internet Explorer 11 (IE11) |
|---|
|
| Summary: As of June 15, 2022, Wolters Kluwer will no longer support Internet Explorer 11. Our recommended browsers for accessing Wolters Kluwers hosted applications will be Google Chrome and Microsoft Edge (Chromium-based, current two versions). Wolters Kluwer does not anticipate prevalent issues for users accessing the application(s) via IE11. However, Wolters Kluwer will no longer remediate problems that are specific to the IE11 browser. |
| Implementation Notes: This enhancement is available in the May release of DocViewer. |
| DocViewer: SignatureField and SignatureDateField display behavior enhanced |
|---|
|
Summary: Users reported that DocViewer displayed an error when
executing files containing a SignatureField and
SignatureDateField. These elements are used to author
signatures outside of a SignatureSection; with this change
DocViewer was updated to handle these fields appropriately. Users will no
longer see an error and the area for the SignatureField and
SignatureDateField will function identically to that of a
SignatureSection. |
| Implementation Notes: This enhancement is available in the May release of DocViewer. |
| DocViewer: eNotary information hidden |
|---|
|
| Summary: DocViewer has been enhanced to no longer display the eNotary section. This enhancement was implemented so that the eNotary display behavior matched that of Signature fields. |
| Implementation Notes: This enhancement is available in the May release of DocViewer. |
April
| Missing Party Names addressed |
|---|
|
| Summary: With this release, DocViewer has been enhanced to use the prompts for a container based on the working dictionary value, unless a prompt value is defined in an overlay file. |
| Implementation Notes: This enhancement is available in the April release of DocViewer and Hosted Expere / Expere Document Services. |
| EndSessions time outs behavior enhanced |
|---|
|
| Summary: With this release, the EndSession will only check if there is missing required data if SupportRequiredData is true and the DONE button was not selected during the session. When a user selects DONE in their session, the check for missing required data is already performed and does not need to be performed again when a user calls EndSession on the same session. |
| Implementation Notes: This enhancement is available in the April release of DocViewer and Hosted Expere / Expere Document Services. |
| Document display issue resolved |
|---|
|
|
Summary: Users reported that static documents did not display in
DocViewer due to such factors as the number and size of embedded
transactions and the presence of inline graphics. This behavior has been enhanced; DocViewer has been updated to better handle documents containing inline graphics and embedded transactions. |
| Implementation Notes: This enhancement is available in the April release of DocViewer. |
March
Note: There are no customer-facing changes included in the March
release of DocViewer.
February
| DocViewer: supported added for representative entity beneficiaries |
|---|
|
| Summary: A user reported that an error occurred in DocViewer when a representative entity element is included as child element of beneficiaries. We have enhanced DocViewer to accommodate this functionality. |
| Implementation Notes: This enhancement is available in the February release of DocViewer. |