CKM Release 1.16.1
Date: February/March 2021
Bug Fixes
Key | Summary | Description |
---|---|---|
CKM-1420 | Archetype/Template/Termset Statistics: Quickly changing the Subdomain and/or project selected may lead to displaying the results for a previous selection | If changing the selected subdomains and or projects very quickly before results are displayed, it is possible that the second last selection is so much slower to yield a result than the last selection. In this case, the wrong result may be displayed in the end. For example: Select all projects and then quickly select All incubators as project selection. |
CKM-1423 | Archetype Revision History cannot be loaded if an archetype carries a syntactically invalid SemVer revision number in its revision field | Unable to load and display an archetype’s revision history if the archetype contains an invalid revision number (not SemVer, e.g. just “alpha”, instead of e.g. “0.0.1-alpha”) other_details = <
["revision"] = <
"alpha"
>
> |
CKM-1436 | In a new CKM with no archetype, general archetype statistics cannot be retrieved (for Dashboard and the general statistics) | In a new CKM with no archetype, the general archetype statistics cannot be retrieved. |
CKM-1437 | Avoid reloading of left hand panels after a resource status change if possible (i.e. if no new revision is required) | When a resource's status is updated, we should avoid reloading the left hand panels if possible. This is not possible for example if an archetype is (re-)published or set to reassess. If the status update of the resource does not require a new revision of the resouce, CKM does not need to reload the panel, it can just update the status icon for the resource in the trees. This is faster but it is also useful because it avoids losing any text filter applied on the resources etc in the left hand panels. |
CKM-1438 | Archetype display problem for DV_QUANTITY elements with a constrained unit, precision and magnitude | Given an archetype with a Quantity Element as follows ELEMENT[at0026] occurrences matches {0..*} matches { -- Severity rating
value matches {
C_DV_QUANTITY <
property = <[openehr::380]>
list = <
["1"] = <
units = <"1">
magnitude = <|0.0..10.0|>
precision = <|1|>
>
>
>
}
} the display of the archetype shows “Limit decimal places” before “Units” and without a linebreak, e.g.:
Limit decimal palces belongs to one individual unit and thus shold be displayed underneath the bullet point
As finetuning, if there is exactly one unit/magnitude/precision constraint (DV_QUANTITY_ITEM) (as in the example above), then the display can be further finetuned to avoid the bullet list completely:
|
CKM-1439 | NullPointerException displayed after deleting a branch template | After deleting a branch template, an error message is displayed in CKM with a NullPointerException stating that the Additional View cannot be displayed for the template. Steps to reproduce:
|
CKM-1440 | [INTERNAL] OET upload: The check for leading or trailing whitespace of renames is executed twice | On uploading an oet file for import or update, the check for leading or trailing whitespace as introduced by CKM-1353 in release 1.16.0 is internally executed twice. This has no effect (other than a minor speed decrease) on the uploader of the template. |
CKM-1442 | A value set referenced from an archetype that has designations without a use element may fail to display in the Details View | Provided: A value set referenced from an archetype and this value set contains designations in its expansion section that do NOT have a "use" element, for example: {
"code": "11833005",
"display": "Dry cough (finding)",
"designation": [
{
"language": "de-DE",
"value": "Trockener Husten"
}
]
} This value set is rendered fine inline in the Archetype's Simple View etc. |
CKM-1443 | Left Hand Panels: Correctly sort archetypes where the concept starts with a number when 'filtering' with a text, but tree filtering is turned off | Left hand archetypes panel: 1. Filter by - say - "ab" An archetype named "6 CIT Assessment" should be displayed _after _any archetypes that contain "ab" (which are displayed in bold). |
CKM-1444 | Left hand panel: In Firefox v85, the "Active", "Under review" and "Published" group does no longer fit in one row by default | In the Left hand panel, the "Active", "Under review" and "Published" group does no longer fit in one row by default, but "Published" is displayed in the next row. This is an issue that was introduced in a new version of Firefox, probably v85, without any change to CKM. |
CKM-1445 | Display of Select box for a new Resource Status is slightly off | On the Resource Status page for a resource (archetype, template), an editor can select a new status for a resource (e.g. TEAM REVIEW or PUBLISHED).
|
CKM-1446 | Log-in with umlaut in the username not successful | A login for user with an umlaut in their username (e.g. ö) may not be able to log into their CKM account. The session is created, but immediately expired and thus users are asked again and again to enter their password: The password dialog closes and is displayed again immediately. |
CKM-1447 | Login with a username with an ' in it succeeds but shows an error message stating that the user's activity cannot be retrieved | Login with a username with an ' in the username itself (e.g. kath.o’toole). |
CKM-1448 | When constructing the referenceSetUri for an external value set in the opt from a termQueryId constraint in oet, a terminologyId starting with // and the queryName should always be connected by a slash | When constructing the referenceSetUri for an external value set in the opt from a termQueryId constraint in oet, a terminologyId starting with // and the queryName should always be connected by a slash to avoid having to specify a slash at the end of the terminologyID or the beginning of the queryName. For example given the following oet extract: the constructed referenceSetUri in the opt should look like this: |
CKM-1450 | [Internal] Avoid occassional internal exceptions when resizing the Dashboard or closing/refreshing the SignedInDashboard on logout | Occassionally (depending on timing), internal exceptions could occur when:
|