Skip to main content

20.5.1 Release Notes

May 2020

Core: 26928.26928

Filing: 26928.26928

XBRL: 26928.26928

This is a CDM general incremental release that aims to enhance the existing product features and address a series of defects found on previous versions.

Features

XBRL

  • Removal of SEC alternate row shading option from HMRC/IE Revenue inline generation screen
  • Exporting reports with projects now also exports taxonomy files, if applicable
  • Generic Inline and XBRL 2.1 & Dimensional validation options have been merged into the XBRL 2.1, XBRL Dimensions 1.0, Inline XBRL 1.1 validation option
  • Projects no longer support the following characters in their names &, %, +, #. Projects that already use these characters must be manually updated to avoid issues.

Bug Fixes

Severity

ID

Title

Critical

185674

[Filing Packages] All Forms are generated/validated even if they are not present in the applied Custom Group

High

186499

Unable to roll forward reports using CDM clients without the XBRL plugin

Medium

186128

Images are missing from generic HD Generations for reports with names longer than 32 chars (non-EDGAR HTML and non-Inline)

Medium

186263

Cannot save Desktop Publishing generation as snapshot if the generation result contains images

Medium

185919

SEC (non-HD) Inline text blocks start at the end of previous page instead of at the top of the page

Medium

156020

Process for Validation/Generation with Validation appears as failed but re-entering CDM will change its status

Medium

156673

Unknown server error message when tagging project that has tags in custom groups not shown (addressed in 19.11.2)

Medium

147028

[Inline XBRL] Paragraphs breaking incorrectly when string tag is in the middle of a paragraph of a text block (addressed in 19.11.2)

Notable Known Issues

Severity

ID

Title

Medium

185878

When opening an inline generation from the processes window (using the folder icon), a permission error in a browser window appears instead of the ix-Viewer. The save functionality is not affected.

Workaround: Enable windows authentication on CDM Server.

Medium

186931

The facts are not loading in the ix-Viewer when opening the generation result from LRP using chromium browsers for non-SEC projects

Workarounds:

  • Use the Microsoft Edge that comes as a default windows component as the default browser
  • If you have inline XBRL viewer configured locally save the files locally and open them in the local viewer.

Installation

The CDM Client is now a 64-bit application, please contact support if a 32-bit client is required. Please do not install this package if client machines are using Windows 32-bit. This version can be deployed in the following ways:

Server

  • As a stand-alone fresh installation.
  • As a stand-alone installation by selecting Use existing databases or Empty databases, if you already have CDM database(s) from previous versions and a known encryption key. If you do not remember your encryption key, it can be obtained using the Get Encryption Key utility provided with this release being run on the previous version of CDM prior to uninstalling it.
  • As an upgrade from 20.1.1 or later.
  • Inline XBRL for SEC customers must deploy the XBRL Dependencies on the same box with the CDM Server which is provided alongside the CDM installers.
    • This build uses the same XBRL Dependencies as version 20.1.1, so an update is not required.

Client

  • As a stand-alone fresh installation.
  • As an update over previous versions of the Certent CDM Client.

ClickOnce

  • As a stand-alone fresh installation.
  • As an update over previous versions of the Certent CDM publishing server.
  • Due to the change from 32-bit to 64-bit of the Certent CDM Client, previously installed client via ClickOnce will not be automatically upgraded upon start up. The client must be removed and redeployed when upgraded from a version earlier than 20.3.1.
    1. Remove Certent CDM from Add/Remove Programs.
    2. Access the publishing server URL.
    3. Press the Install button.

Was this article helpful?

We're sorry to hear that.