Bugs fixes
The following defects have been corrected in this major ConSol CM version 6.18.3.
6.18.3.0
#630610 – Contact icon shown for companies in detail search
When adding a company column to the results table of a search for contacts in the detail search of the Web Client, the same icon was shown both for the contact and the company. This problem has been fixed; and the detail search now shows the correct icons in the company and contact columns.
#664530 - Problem with dashboard configuration
When defining a dashboard on the Dashboards page of the Web Admin Suite, it could happen that the defined tabs and widgets disappeared after clicking the Save button. This problem has been fixed, and the dashboard now correctly displays all configured elements.
#666328 - Incorrect formatting of variables in templates
When inserting several variables next to each other in a rich-text template and applying formatting, e.g. bold font, to some of the variables, the bold formatting was applied to all adjacent variables when using the template in the Web Client. This problem has been solved and formatting is now applied to the intended variables only.
#667342 – Adding a row to table took long
Adding a row to a table (struct) when editing a case, contact or resource in the Web Client was slow when dependent enum scripts and hierarchical lists with lots of disabled values were involved. This issue has been resolved by filtering out disabled values, so that the first row now appears quicker and subsequent rows are added instantly.
#667450 – Special characters removed from attachment file names in CM/Track
When an attachment containing a plus sign or an apostrophe in its file name is uploaded in CM/Track, those characters are automatically removed. This problem has been solved and CM/Track and the underlying REST API now preserve plus signs and apostrophes in attachment names making the behavior consistent with the Web Client.
#667493 – Not possible to reply to incoming email
When a user tried to reply to an incoming mail in the Web Client, a template parsing error occurred because the reply retained the objectid and objecttype attributes from the original email, preventing the reply from being sent. The problem has been solved by removing these attributes during reply, forward, and quote operations, so users can now reply to emails without errors.
#667501 - History visibility setting missing in custom export
The setting Visibility in history, which can be defined for workflow elements, was lost when exporting a workflow on the Custom export page of the Web Admin Suite. On import, the setting was set back to its default value. The problem has been solved, and the export now includes the history visibility settings.