CKM-2196

Release Sets don't know their latest published revision under some circumstances

Release Sets don't “know” their latest published revision under some circumstances.

This can have the following consequences

1. A previously published release set that is now in REASSESS status shows the REASSESS status correctly as in the screenshot. However, unlike in the screenshot, it is NOT possible to directly switch to the LATEST PUBLISHED revision.

1. A PUBLISHED Release Set is displayed as published but a tooltip or other text may indicate that it is the LATEST REVISION (UNSTABLE).

CKM-2197

When opening the ADL tab of an Archetype directly from the context menu, the new tab remains empty

When opening the ADL tab of an Archetype directly from the context menu, the new tab remains empty instead of displaying the formatted ADL.

Steps to Reproduce:

1. Right-click on archetype in the left-hand concertina

2. Select ADL / XML

→ The CKM tab is opened, but shows nothing.

CKM-2207

Very small chance of a bogus error message claiming that the maximum number of concurrent users has been reached when a user tries to login

There is a very small chance of a bogus error message claiming that the maximum number of concurrent users has been reached when a users tries to login.

This may happen if the internet connection drops out exactly between two specific calls during the login process,

In this case, a StatusCodeException with code 0 is thrown. However, despite of the error message displayed, this then does NOT mean that all concurrent licence seats are taken, so this should not be adviced as such.

This is very unlikely due to the timing required which is nearly not reproducible but has indeed occurred in practice.

CKM-2221

CKM Dashboard: The news section does not display the name of the project/incubator for new/updated resources

In the CKM Dashboard, the News section does not display the name of the project/incubator for new/updated resources. Instead the project type (project or incubator) is repeated in capital letters.

CKM-2223

Wrong error messages when trying to commit archetypes as project editor or project translation editor

For archetype branches with content and translation changes, two issues have been identified when trying to commit the archetypes as a project editor or project translation editor, respectively:

1. For full Editors of the project, an error message is displayed stating that the user does not have all rights for all changed translation languages.
   Expected: There should not be an error message at all. The editor should be allowed to continue to commit the archetype.

2. Translation Editors that are not also full Editors of the project are correctly prevented from committing this branch, but the error message encountered is misleading.
   Expected: In this case, there should be an error message indeed, but it should be the more informative

CKM-2224

Status display does not change immediately after internalising an archetype

When internalising a referenced archetype its status is changed to Draft, which is correct.

In its revision history it correctly shows as Draft (or Initial if internalised into an incubator), however the headline of the archetype still show the status in its original CKM.

The archetype or CKM as a whole needs to be reloaded in order to display its new correct status.

While it is a minor problem, it can cause confusion whether the archetype is in its original status or has been changed, especially since even experienced editors typically only rarely use the ‘internalise’ functionality.

CKM-2225

Editor's Tasks: User Profile is not opened by clicking on the Creator of the Task

In the Editor’s Tasks List for a resource, the Creator of the task is displayed as follows:

Created by Firstname Lastname » (14-Dec-2023 13:15).

When hovering over the username, some more information about the user should pop up.

When clicking on the username, the creator’s user profile should be opened in a new tab.

CKM-2226

Change Requests and Editor Tasks: User Details/Profile of the Creator should not be available via hovering over or clicking on the description of the Change Request or Task

In the list of Change Requests for e.g. an archetype, the following happens:

• When hovering over the description of the Change Request, the User Details of the creator of the Change Request pop up.

• When clicking on the description of the Change Request, the User Profile of the Creator of the Change Request is opened in a new CKM tab.

Both actions should be restricted to where the details of the creator are displayed, e.g.: “Created by XYZ » (04-May-2024 07:28)”

This happens similarly for Editor Tasks - only that in this case the hovering and clicking in restricted to a single row.

CKM-2231

Template Related Resources Report: An archetype that is in an inactive state and us used by a template in its latest version should not be listed as "unstable", but rather as deprecated or rejected

In the Template Related Resources Report:

If a archetype is used in its latest version which also happens to be in an inactive state this should be indicated as such. Instead of "LATEST REVISION (UNSTABLE)", this should be stated as “LATEST REVISION (DEPRECATED)” or “LATEST REVISION (REJECTED)”, respectively.

One example is the Dosage archetype used by this template:

https://ckm.highmed.org/ckm/templates/1246.169.2322/7/relatedresources

Incorrect/Misleading (CKM 1.20.0):

Correct/Better (CKM 1.20.1):