DMS- Release 2020.3

DMS FAQ
Articles in this section provide answers to frequently asked questions on the DMS appliance.

DMS Release Information
Articles in this section give release notes and links to see the product roadmap.

DMS Resource Centre

DMS Ideas Portal

Perspective Platform Resource Centre

DCMTALL-10 \ 41466

New Document Auto-Name Placeholder.

Support has been added for a new "AutoFormat" placeholder similar to the one for "{reference}"2. This is "{description}" and is the object description that the document is created for. This allows you to include more info in the document prefix such as the client name. As a part of supporting this, when creating a file name, we strip from the text any characters that are "non-file friendly" that would affect saving the file to disk. This includes slashes, etc.

e.g. For their project with reference/number: "03453" they have the project's Description field as "Smith / Jones"Consider an auto-name format for a Tender document as "{reference} - {description} - Tender"In this example, the resulting document would be "03453 - Smith Jones - Tender.pdf"1. the reference and description of the object now form part of the document name2. The non-file-friendly slash in the description field is stripped from the description/name.

DCMTALL-6 \ 41884

Download and View Actions on Notification Emails.

Improvements have been made to the way people can download documents for which they have received a notification regarding a document where direct access is allowed.

1. When defining a Notification to be sent for a Document Type, a new option to "Allow direct access to download the document" has been added.

2. Where direct cloud access to a file is supported (i.e. against the Document Type), AND this new setting is set to Yes in the notification config, the notification email has two buttons/actions:

   • “Download” button (green) - providing direct access to download from the cloud without going via the DMS, and

   • “View in DMS” button (blue) - requiring the user to access the document via the DMS.

3. When a Document Type Notification is defined:

   1. The label "Enable Related Object Type Specific Notification" has been changed to "Only Notify Contacts Linked to the Object (i.e. not all contacts in the role)".

   2. The label above the combo has changed from "Roles" to "Contact Roles".

   3. The autocomplete text in the combo has changed from "Select roles” to "Select contact roles..."

4. A complete review of managing notification has been done, and we've corrected the terminology to be "notification" and not the incorrect "notification role,"e.g. in messages.

DCMTALL-13 \42142

Tag issues with an ampersand.

Issues encountered, where tags used the ampersand character, have been resolved.

DCMTALL-7 \ 42145

Improvements to Tags List.

The page listing the tags used within Almirah has been improved.

1. All standard user interface standards for this type of page have been implemented.

2. There is now a filter available.

3. Pages now display 50 results per page.

DCMTALL-8 \42146

Tag view improvements.

It is now possible to see where and how tags are used.

1. The page now implements our View Page standards with

   1. The title is the object name, not "View Tag".

   2. The breadcrumb matches.

2. The page has a lazy load accordion"Document Types" that lists the document types that are tagged with this tag. The list:

   1. Has columns (as per the Document Types List page):

      1. Document Type (hyperlink).

      2. To the Document Type View page).

      3. Description.

      4. Structure.

      5. Tags.

   2. Has actions;

      1. "Delete tag" (i.e. remove this tag from the document type)

   3. Has standard paging.

   4. Has a standard filter.

3. The page has a lazy load accordion"Documents" that will list the documents that are tagged with this tag. Note: this is documents specifically/directly tagged, not documents of a type that is tagged. The list:

   1. Has columns (as per the Document Search page):

      1. Document (hyperlink to the Document View page).

      2. Version.

      3. Status.

      4. Structure.

      5. Reference.

      6. Tags.

      7. Related Object (hyperlink to the Object View page).

   2. Has actions:

      1. "delete tag" (i.e. remove this tag from the document type).

      2. Has standard paging.

      3. Has a standard filter.

DCMTALL-9 \42148

Archiving and restoring documents.

1. The Document View page has an Archive Action/Button, as the last button on the right, for a document that is Active. When used, this will change a document to being inactive/archived.

2. The Document View page has a Restore Action/Button, as the last button on the right, for an Inactive document (archived). When used, this will change a document to being active.

3. The Document Search page has a new option to "Include Archived ..."

   1. The default for the page does NOT include archived documents.

   2. The user's selection is remembered for when they search.

4. The Document Browse and Linked Files pages are unaffected by this change, and both Active and Inactive documents are always included when browsing objects' documents.

 DCMTALL-11 \42415

Object Browse (View) Improvements.

1. The Object Browse (View) Page has been updated to include the "Integration Subscriptions" accordion.

   1. Showing all subscriptions for the object,

DCMTALL-12\42412

Doc-Browse/Linked-Files Enhancements

1. The Add Document Button has been moved to be under the Object Name.

2. The documents list (when viewing by combined/separate structures has been made wider to show additional columns (as displayed on the Document Search page.

   1. Version

   2. Status

   3. Reference

   4. Tags

3. When viewing documents as "A List", the columns have been updated to show;

   1. Document

   2. Version

   3. Status

   4. Reference

   5. Tags

   6. Structure

4. All of the above changes have been applied to both the "Document Browse" and "Framework Linked Files" pages in WebUser.

DCMTALL-14 \42613

Improvements to merging tags

The merge action for tags was not intuitive. The merge page now displays instructions on what the user needs to do and what will happen.

37762

Implementation of Workflow/ eSigning of Documents