Bugs fixes
The following defects have been corrected in this major ConSol CM version 6.18.2.
6.18.2.0
#662008 - Missing asterisk for required fields in activity forms
The asterisk marking a field as required in an activity form in the Web Client was missing when the field next to the required one spanned several rows. This problem has been resolved, and all required fields have a red asterisk now.
#662308 - Person and company variables did not work in contact templates
Errors occurred when using person or company as variables to access the contact object in some display templates. This problem has been solved and the variables work correctly now in all contact display templates.
#664718 - Contact and resource comments not sorted by date
In the Web Client, when sorting comments in the Comments and attachments section on contact and resource pages by date, the comments were incorrectly sorted as text rather than by actual date, leading to an incorrect order. This problem has been resolved, and comments are now correctly sorted by date for both contacts and resources.
#665201 - Links removed for retried emails
When retrying an email on the Failed incoming emails page of the Web Admin Suite, links with a link text were removed, even when settings allowed to display links from incoming emails. Only the link text as plain text was shown. This issue has been resolved and links are now shown if permitted regardless of the entry channel.
#666119 - Fields belonging to other contacts visible in activity form
Contact fields which belonged to the main contact were visible to additional contacts in activity forms even when the setting Only allow access to own data (system property restrict.unit.access.to.own.data) was set to true. This problem has been solved to ensure that contacts are not able to see and modify other contacts' fields.
#666142 - Queue without contacts not shown for case creation
During case creation in the Web Client, selecting a contact filtered out queues that do not allow contacts, making it impossible to switch to such queues. This problem has been solved and queues without contacts are available for selection now regardless of previously selected contacts. If a user switches to a queue without contacts, any previously selected contact will be removed.
#666293 - Wrong open position of enumerated list
When quickly reopening an enumerated list with autocomplete display in the Web Client, especially on a slow network, the dropdown would open in the upper left corner of the page, detached from the field. This problem has been solved, and the dropdown now opens in the correct position regardless of network speed or quick reopening actions.
#666320 - HTML content from plain text emails rendered as HTML code
HTML tags contained in plain text emails sometimes interfered with the feature to render only certain links in emails in the case history of the Web Client, causing layout problems. This issue has been resolved and HTML is never rendered for plain text emails now.
#666346 - Editing enum list directly on fields page not possible if category contains a minus character
In the Web Admin Suite, it was not possible to edit enumerated lists directly from the data field details if the list category contained a minus character. This problem has been solved, and it is now possible to edit enumerated lists directly in this situation.
#666375 - Missing translation when importing a scene
During a scene import in the Web Admin Suite, the German translation for the spinner Processing scene was missing, displaying the English label instead. This problem has been solved and the text is now displayed in German as Szenario wird verarbeitet.
#666484 - Enum autocomplete values sorted by technical name in CM/Track V3 and REST API
The values of autocomplete enum fields were sorted by the technical names in CM/Track V3 and the REST API. This problem has been solved, and the enum values are now correctly sorted by localized names.
#666625 - Excessive space between delete icon and other icons
The space between the delete icon and other action icons in tables in the Web Admin Suite was too big, resulting in an inconsistent display. This problem has been solved by removing the unneeded spacing.
#666648 - Technical names of enums shown for case creation after queue change
In the Web Client, when creating a case and changing the queue, data fields of the type Enumerated list displayed technical names instead of localized names if the previous queue had the same field. This issue has been resolved, and now the localized names are consistently displayed for enum fields after changing queues during case creation.
#666647 – Accessibility issues on the case creation page of CM/Track
Some ID attributes and aria labels were missing on the case creation page of CM/Track reducing accessibility. This problem has been solved by adding the missing elements.
#666702 - Broken display of selector icons
The arrow and x icons for selectors in the case, contact and resource data in the Web Client were not displayed correctly in some browsers, resulting in a broken display of the selectors. This problem has been solved and the selector icons are now displayed correctly in all supported browsers.
#666705 - Not possible to remove assigned condition script
When selecting a condition script for a web form on the CM/Forms page of the Web Admin Suite and updating the form, it was not possible to remove the condition script anymore because it was automatically reassigned after saving. This problem has been solved, and condition scripts can now be successfully removed and remain unassigned after updating the form.
#666706 - Theme styles not loaded last in edit mode
The styles from the theme defined in the resources folder of the data directory were not loaded last when a case was in edit mode, so that custom styling was not applied. This problem has been solved and the theme CSS files are now always rendered last.
#666708 - Not possible to scroll to the last table entries
On the CM/Forms page of the Web Admin Suite, it was not possible to scroll to the last two forms when the details panel was opened. This problem has been solved, and users can now access all forms even when the details panel is open and the filters above the table occupy two rows.
#666839 - Duplicate workflows shown in workflow filter
On the Activity forms page of the Web Admin Suite, all versions of a workflow were displayed in the workflow filter, resulting in multiple identical entries for each workflow version. This problem has been solved, and now each workflow is shown only once in the filter.
#666862 - Layout problem with long list labels in CM/Track V3
When using a list to group case creation tiles in CM/Track V3, the tiles were squeezed if the list items had long labels. This problem has been solved by reserving more space for the tiles in such situations.
#666906 - Copied time trigger at activity loses setting
When copying an activity with a time trigger on the Workflows page of the Web Admin Suite, the setting Set time manually was not retained in the copied time trigger. This problem has been solved, and the time trigger settings are now correctly preserved when copying activities.
#666945 - Adding nodes to an existing hierarchical list breaks DWH updates
When adding a new node to a hierarchical list in the Web Admin Suite, the DWH live mode and DWH update failed due to duplicate entries. This issue has been resolved, and adding nodes to a hierarchical list now works correctly when the DWH is enabled.
#666965 - Unneeded history entries for activity executions
The case history in the Web Client showed duplicate history entries about activity executions and restores when the workflow contained triggers causing interrupts. This problem has been solved and only the last restore operation is now logged in the case history. In addition, when the visibility in history of an activity is set to Hide on all detail levels, this now applies to restore operations as well.
#666966 – Lazy loading not respecting visibility setting for activity restores
When lazy loading is enabled for the case history in the Web Client, history entries referring to activity restores that are configured to be visible only on the high detail level incorrectly appear in medium and low detail levels, exposing information that should be hidden. This problem has been solved and lazy loading now respects the visibility settings of the ACTIVITY_RESTORE log type.
#666980 - Strange behaviour when double-clicking a list item in the case creation tiles
When the user double-clicked a list item in the case creation tiles in CM/Track V3, the selection unexpectedly switched to the first item without focus. This problem has been solved, and now a second click on the same list item does not cause any unintended behavior.
#667057 - Code completion did not work for OperationResponseBuilder
When using the client variable in the script editor in the Web Admin Suite, no suggestions for methods were shown. This problem has been solved and code completion is now available when typing client.
#667114 – Missing edit button for users with change participants permission
When a user in the Web Client was granted the Change participants permission but not the Edit data permission, the Edit button was missing, preventing any modification of additional participants. The problem has been solved and the Edit button is now displayed. It opens the case with all fields except for the additional participants grayed out, allowing users to edit additional participants only.
#667156 - Email could be resent twice
When sending a manual email from a case in the Web Client failed, and the email was resent first from the Web Client, it was possible to also resend it from the Failed outgoing emails page of the Web Admin Suite. This problem has been solved, and the Web Admin Suite now immediately reflects the successful resend from the Web Client, preventing duplicate email sends.
#667187 - Error when removing outdated notification
An error was written to the log files when a background process tried to remove outdated notifications. This problem has been resolved and outdated notifications are removed correctly now.
#667200 – Wrong fallback for allowed attachments in rich text templates
On the Rich text templates page of Web Admin Suite, the allowed attachments were limited to images only when the system property cmas-core-server, attachment.allowed.types was unset. In addition, users with Manage templates permissions could only upload images. These problems have been solved, and all file types are now allowed if the property is empty, aligning the behavior with the Web Client for both regular administrators and template administrators.
#667204 - Templates not shown in portal settings
When accessing the Global portal settings page of the Web Admin Suite for the first time after login, all templates were displayed correctly in the Credentials tab, but upon changing the page and returning, the template selections appeared empty until the page was reloaded. Additionally, invalid template types were shown when opening the template in a modal window. This problem has been solved, and now the template selections remain always visible, and the correct template types are displayed in the template modal.
#667242 - Missing error message when entering a non-unique value in struct list
When attempting to create a case in CM/Track V3 with a non-unique value in a data field belonging to a list which had the Unique setting applied, the system failed to provide immediate feedback to the user, logging the error instead. This issue has been resolved by implementing a toast message that informs the user about the non-unique field.
#667287 - Exception during PDF generation
Using the method contentFileTemplateService.generatePDFDocumentFromWord in a script caused an exception. This problem has been solved by updating the underlying docx4j library.
#667292 - Typo in history section
When using the Web Client in German, there was a typo in the header of attachment entries in the case history. This problem has been solved, and the label now correctly displays Attachment hinzugefügt von.
#667310 - Wrong error message when submitting an activity form with non-unique values
In CM/Track V3, when submitting an activity form with non-unique values in data fields which had the Unique setting applied, an incorrect error about changes performed in the meantime was displayed. This problem has been solved, and now a message about non-unique values is shown in activity forms.
#667337 - Incorrect validation for unique fields in activity forms
When a field belonging to a list or table was configured to be unique and non-unique values were entered in different rows in an activity form in the Web Client or CM/Track, the validation message that there were non-unique fields was still displayed after removing the affected rows. This problem has been solved and the unique validation now works correctly for child fields of lists and tables in activity forms.
#667338 - Wrong language availability in portal configurations
On the Portal configurations page of the Web Admin Suite, users could only set translations for system languages in the case creation tiles and news widgets, even if translations for other languages existed in the JSON files. This issue has been resolved, and now all languages present in the JSON files are available. The languages are sorted alphabetically by their localized names and translate icons are shown where applicable.
#667363 - Irrelevant results in quick search
When entering a search term starting with a letter and ending with numbers in the quick search of the Web Client, many irrelevant results were returned due to the phonetic encoding process. This issue has been resolved, and the phonetic search is not applied anymore to terms including numbers.
#667428 – Detail search fails for enum criteria of contact
When using an enum field belonging to a contact object as a search criterion in the details search of the Web Client, an error occurred when searching for cases. This problem has been solved, and searching for cases by a contact enum field now works correctly.
#667433 - Duplicate password icons in Edge
When entering a new password for user or email configurations in the Web Admin Suite using the Microsoft Edge browser, two icons to toggle the password visibility were shown. This problem has been solved, and now only a single password visibility icon is displayed across all browsers.
#667435 – Customer group criterion not applied in detail search
When using the search criterion Customer group in a detail search for cases in the Web Client, the selected customer group was ignored and cases whose main contact belongs to another customer group were shown in the search results. This problem has been solved and the customer group criterion is now correctly applied, limiting search results to cases belonging to the selected customer group.
#667549 – Unique field value validations not handled correctly in contact and resource action forms
When a user edited a contact or resource via an action form and set a field defined as unique to a duplicate value, no validation message was shown and nothing happened when submitting the form. This problem has been solved, and non‑unique values are now validated instantly in both contact and resource action forms, with error messages displayed next to the fields.
#667592 – Small layout problem in additional participants modal
In the Web Client the focus border of all elements in the Additional participants modal was cropped at the bottom, so users could not clearly see which field had focus. The issue has been resolved by restoring the full focus border.
#667616 – Button text too big
The text of buttons with an arrow to expand additional options in the object headers of the Web Client was too big. This problem has been solved, and now all the text of all buttons has the standard font size.
#667649 – HTML lang attribute always set to English in CM/Track
When a user with a non‑English browser language uses CM/Track, the HTML lang attribute remains en instead of reflecting the browser's language, which hampers accessibility and localisation. This issue has been resolved, and the lang attribute now follows the browser's language when a corresponding localisation exists, otherwise it falls back to English.
#667651 – Styling issue in attachments section
When a long list of allowed attachment types is defined in the system property allowed.attachment.types, the attachments list was still displayed on a single line on the Rich text templates and Error reports pages of the Web Admin Suite, causing overflow and unreadable formatting. This problem has been solved and the attachment types are now rendered with proper line‑wrapping and spacing, providing a clean and readable display.