Skip to main content
Version: 6.19

Bugs fixes

The following defects have been corrected in this major ConSol CM version 6.19.0.

6.19.0.0​

#666766 – Technical view name shown in user profile​

The user profile of the Web Client showed the technical names of the views in My view characteristics under General settings. This problem has been resolved and the user profile now correctly displays the localized view names.

#667442 – Error when using tabs in contact search template​

When inserting tab characters in the Contact search in case creation template in the Web Admin Suite, it was not possible to select a contact on the case creation page of the Web Client. The issue has been resolved, and tabs are now correctly escaped in templates, restoring normal contact search functionality.

#667674 - Readonly fields not overwritten by default values script​

When switching queues during case creation in the Web Client and the default values script of the new queue sets a value to a read-only field, the previously entered field value was not overwritten. This problem has been solved and default values scripts now correctly overwrite readonly fields.

#667684 - Validation errors not removed correctly in activity forms​

When filling out a list or table in an activity form in the Web Client, validation errors for required fields remained visible after the user corrected the input, and it was possible to submit the form regardless the displayed error. This problem has been solved and validation messages belonging to tables (structs) or lists are now properly cleared when fields are fixed or rows are removed.

#668088 – Case-sensitive matching of email addresses​

The email address check for the text class option Only emails (incl. email attachments) with the customer as a sender or recipient are visible to the customer was case‑sensitive, so emails whose address differed in case from the email saved in the contact data were not displayed in CM/Track for the contact. The problem has been resolved by changing the comparison to case‑insensitive, ensuring that all emails are now correctly shown in CM/Track.

#668115 - Historization of autocomplete field change writes technical name​

When modifying an autocomplete field in a case in the Web Client, the case history incorrectly displayed the field's technical name instead of the localized one. This problem has been solved, and the case history now correctly displays the localized name of modified autocomplete fields.

#668165 - Not possible to add comment with only an image​

If the option FroalaEditor.ENTER_BR is used for the rich-text editor in the Web Client, inserting a single image into a comment via the Insert image icon and saving the comment resulted in a validation error and the image disappeared. This problem has been solved and comments that contain only an inserted image can now be saved correctly.

#668253 - Filling and autocomplete field in CM/Track with an asterisk as search string causes whitescreen​

When creating a case in CM/Track and entering an asterisk (*) as a search string in a scripted autocomplete field, the application displays a whitescreen. This problem has been solved and the autocomplete field now correctly handles asterisks as valid search strings.

#668264 - Broken layout in tables in activity forms​

When selecting a long value in an enum or hierarchical list field inside a table (struct) in an activity form in the Web Client, the dropdown arrow overlapped the chosen text, breaking the layout. This problem has been solved, and the dropdown arrow now correctly displays without overlapping the selected value.

#668448 - Missing task IDs in bulk operations​

When using multiple tasks for large batch operations, exceptions due to missing task IDs occurred sporadically. This problem has been solved by loading task descriptors in a single SQL statement together with their parent tasks.

#668624 - Changing source resource type of a resource relation does not work​

When editing a resource relation on the Resource relations page of the Web Admin Suite, it was possible to edit the Source resource type field but after saving and refreshing the new type was not persisted. This problem has been solved by disabling the ability to modify the source resource type for existing relations.

#668677 - Attachment not automatically selected when forwarding emails​

When forwarding an email with an attachment in the Web Client with lazy loading enabled or a low history detail level, the attachment was not auto-selected, requiring manual selection. This problem has been solved and the attachment is now automatically selected when forwarding the email.

#668836 - Not possible to attach XLSM file in the Web Client​

When attaching an XLSM file in the Web Client, the ConSol CM server incorrectly identified the MIME type as application/zip and blocked the upload. This problem has been solved and XMLS files are now correctly recognized by the server and can be attached successfully. If a user tries to upload a file whose extension is allowed but the MIME type does not match, a corresponding error message is shown in the Web Client.

#668908 - Unneeded stacktraces for expected REST errors​

When the ConSol CM REST API was called to retrieve a non-existing object, a warning message with a large unneeded stacktrace was written to the log files. This problem has been solved and the stacktrace is no longer included in the log files when trying to retrieve a non-existing object via REST API.

#669149 - Not possible to upload HEIC attachments​

Uploading HEIC files via the Web Client or importing email with HEIC files as attachments failed due to a MIME type mismatch. This problem has been solved by properly registering the image/heic MIME type, so HEIC files are now correctly processed.

#668954 - Wrong display of autocomplete suggestions​

When using scripted autocomplete fields in CM/Track with dark mode, the suggestion list appeared with a transparent background, making the text unreadable. This problem has been solved and the suggestion background is now explicitly styled with a solid color, ensuring clear visibility in dark mode.

#669092 - Custom export not possible​

When trying to export all data related to a queue on the Custom export page of the Web Admin Suite on a large system, a timeout could occur while gathering the entities for export. This problem has been solved by optimizing the entity collection.

#669384 - Error when changing file name on portal configuration page​

When renaming the public.json file in the Files tab of the Portal configurations page of the Web Admin Suite an error occurred. This problem has been solved, and the file name can now be updated successfully.

#669394 - Localization changes are saved only for EN and DE locales​

When modifying localization files in the Files tab of the Portal configurations page of the Web Admin Suite, changes for locales other than English and German were not saved and disappeared after a page reload. This problem has been solved and localization changes are now properly saved and retained for all locales.