Bugs fixes
The following defects have been corrected in this major ConSol CM version 6.17.4.
6.17.4.0
#632944 - Dynamic display value of autocomplete fields not exported
When exporting runtime data containing autocomplete fields with dynamic display values, the respective flag was not included, causing the imported data to revert to static values, which are not updates when the referenced object changes. This issue has been resolved and dynamic display values are now correctly exported.
#660447 - Missing localizations for enum selector in grid view
When viewing the detail search as a grid in the Web Client and selecting a field of the type Enumerated list as a grouping criterion, the technical names of the enum values were shown in the Add/Remove table column field instead of the localized value. This problem has been solved, and the selector now correctly displays the localized values.
#661106 - Deactivated enum values not italic in detail search
Deactivated enum values were only displayed in italics in the detail search of the Web Client if the enum field had the setting Enum display with the setting Autocomplete list. If another enum display was set, the deactivated enum values were displayed in normal styling, making it difficult for users to distinguish them from active values. This issue has been resolved, and deactivated enum values are now correctly displayed in italics.
#662816 - Whole line indented when pressing tab in script editor
When editing a script in the Web Admin Suite and pressing the tab key between two words, the entire line was indented instead of inserting a tab at the cursor position. This problem has been solved, and pressing the tab key now correctly inserts a tab at the cursor position within the line.
#663485 - Incorrect validation of maximum SMTP timeout values
When configuring SMTP timeouts in the Settings tab of the Email configuration page of the Web Admin Suite, values above 65535 were not accepted, and the error message incorrectly displayed a limit of 300000. This problem has been solved by setting the upper limit to 3600000 (1 hour), allowing for longer timeout durations.
#663909 - Attempts to resend an email not logged
When attempting to resend an email on the Failed outgoing email page of the Web Admin Suite by clicking the Retry icon, nothing was logged in the mail.log file. This problem has been solved, and now all mail resend operations initiated in the Web Admin Suite are properly logged.
#663917 - Problem with adding dependencies for custom export
When attempting to add dependencies on the Custom export page of the Web Admin Suite, it could happen that newly added dependencies were not added correctly or were not visible. This problem has been resolved, and dependencies can now be added and are visible as expected.
#664052 - Permissions to contacts of my cases not handled properly
When setting the system property my.customer.enabled from the module cmas-core-server to False, the permissions for contacts of my cases were correctly hidden from the Roles page of the Web Admin Suite, but already set permissions were still applied, so that users with these permissions were able to edit such contacts. This issue has been resolved, and now the permissions for contacts of my cases are completely ignored if my.customer.enabled is set to False.
#664386 - Inconsistent time displayed using different time zones
When viewing case history entries which were created in a different time zone in the Web Client, the creation time displayed in the entry header was not shown according to the current user's time zone. This problem has been solved, and the date and time display is now adjusted to the different time zones.
#664529 - Incorrect escaping of HTML characters in authentication application
The authentication application escaped HTML characters like > incorrectly, so that certain CSS selectors in the custom.css file were invalid. This problem has been solved, and the custom.css file now includes characters without HTML-escaping, ensuring correct CSS rule application.
#664578 - Change in portal settings deletes description of related system property
In the Web Admin Suite, when changing values of authentication-related properties on the Portal configuration or Global portal settings pages, the description of the respective system properties was deleted. This problem has been solved, and the description of system properties is now retained when their values are changed on the pages with portal settings.
#664629 - Scripts referenced in single quotes not detected for viewing and editing
In the Web Admin Suite, when using single quotation marks to reference a script inside a script, the feature to open the script for viewing or editing was not functioning, whereas it worked with double quotation marks. This issue has been resolved, and now scripts enclosed in single quotes are correctly underlined to indicate that they can be opened by clicking.
#664679 - Save button not blocked after clicking
The Save button in the Add comment / attachment dialog of CM/Track V3 was not blocked after being clicked, leading to multiple requests being sent if the user clicked multiple times. This problem has been solved by adding a loading indicator and blocking the Save button after it is clicked.
#664692 - Company name not refreshed in favorites
When the fields used in the display template of a company were updated on the page of one of the persons belonging to the company in the Web Client, the company name was not updated accordingly in the favorites. This problem has been solved and the company name is now properly refreshed in the favorites even if the changes are performed on the person page.
#664742 - Text disappears with prefilled comment in CM/Track V3
When the option Prefilled text is used as an Initial content type of a case creation tile in CM/Track V3, additional text added by the user in the comment field would sometimes disappear when clicking outside the comment field or not be saved upon case creation. This problem has been solved, and the added text in the comment field is now retained and saved correctly when creating a case.
#664776 - Incorrect styling of selected items in case list
The line at the bottom of a selected item in the case list in the Web Client always had rounded corners, regardless of the item's position within the list. This problem has been solved, and now only the last item of a case list group has rounded bottom corners, matching the general styling of the case list.
#664812 - Broken layout for multiline script names in code snippets dialog
When browsing scripts in the Code snippets dialog of a script in the Web Admin Suite, the layout appeared broken due to insufficient space between scripts with multiline names. This issue has been resolved by adding more space between the script names to ensure proper display.
#664863 - Error during when migrating client configuration
When attempting to create a portal configuration for CM/Track V3 based on a client configuration for CM/Track V2 on the Portal configurations page of the Web Admin Suite, an error occurred if the source configuration contained an empty localization.json file. This problem has been solved, and empty localization files are now populated from the template during the migration.
#664865 - Problems in workflow editor with development mode
When changing activity descriptions when the development mode is active on the Workflows page of the Web Admin Suite, concurrency exceptions were written to the log files, and it could happen that the workflow editor closed unexpectedly. This issue has been resolved, and users can now change activity descriptions in development mode without encountering any problems.
#664907 - Description for time and event triggers not saved in development mode
When entering a description for a time or event trigger when the development mode is active on the Workflows page of the Web Admin Suite, the description disappeared after being set, despite a notification indicating successful deployment. This problem has been solved, and descriptions for time and event triggers are now correctly saved in development mode.
#664908 - Missing discard changes dialog on Roles page
After assigning user functions to a role on the Roles page of the Web Admin Suite, the Discard changes dialog was not displayed when starting the creation of a new role or switching to another page, leading to a potential loss of unsaved changes. This problem has been solved, and the Discard changes dialog is now displayed in these situations.
#664929 - Search results disappear after canceling action in case administration
When a user performed a search on the Case administration page of the Web Admin Suite and then attempted to delete or reopen a case but canceled the confirmation, the search results were cleared. This problem has been solved, and the search results now remain visible after canceling the delete or reopen action.
#664963 - Username field in for support ticket creation does not accept email addresses
When creating a support ticket on the Troubleshooting page of the Web Admin Suite, it was not possible to enter an email address as a username for authentication. This problem has been solved by removing the validation enforcing alphanumerical characters only, allowing email addresses to be used as usernames without any issues.
#665000 - Fields required even though OIDC is not used
The settings in the OIDC in the Web Client and OIDC in the Web Admin Suite sections of the Authentication page of the Web Admin Suite were mandatory even if OIDC enabled was set to False. This problem has been solved and these settings are now optional.
#665001 - Field visualization not executed in CM/Track V3
When creating a second case in CM/Track V3 in the same session, the defined field visualization script was not executed correctly. This issue has been resolved, and field visualizations are now executed consistently for each new case.
#665067 - Missing image after copying text with inline image for email
When copying text with an inline image from an email entry and pasting it to the email editor in the Web Client to use it in a new email, the image was not displayed in the history entry of the sent email, showing Image not available or removed instead. This issue has been resolved, and now the copied inline images are correctly displayed in history entries.
#665139 - Incorrect behavior of global permission checkbox
On the Roles page of the Web Admin Suite, when attempting to deselect the Access cases of own company checkbox for an existing roles with this permission, the checkbox could not be deselected, and the Global permissions counter was incorrectly incremented. This issue has been resolved, and the checkbox can now be deselected properly.
#665141 - Missing log information for failed logins with wrong credentials
When users tried to log in using the authentication applications for the Web Client, Web Admin Suite or CM/Track V3, and entered incorrect login credentials, no information about the failed login attempts was written to the log files. This issue has been resolved, and now failed login attempts are properly logged.
#665166 - Error in log during script syntax checking
When opening a script containing import wslite.rest.* in the script editor of the Web Admin Suite, an error was written to the log files because the script syntax could not be validated. This problem has been solved, and the error is no longer shown when performing syntax checks on such scripts.
#665182 - Error when using time trigger script in interrupt
When creating a workflow which contains an interrupt chain ending in an automatic activity with a time trigger attached, which has a trigger script, the script was not executed and an error occurred when a case entered the activity. This problem has been resolved and the error does not occur anymore. Nevertheless, the time trigger script is still not executed as the case returns to its previous position in an interrupt chain.
#665183 - Table formatting and borders not visible in emails
When sending emails with tables from the Web Client, the table formatting and borders were not visible to the recipients due to email clients ignoring the class attribute in elements. This issue has been resolved by adjusting the editor to use inline styles instead of classes, ensuring that table formatting and borders are now visible in emails.
#665197 - Changes to autocomplete script and type not saved during field duplicating
When duplicating a field of the type Autocomplete in the Web Admin Suite and changing the field type and script, the field was created with the type and script of the original field. This problem has been solved, and the new type and script are now correctly saved when duplicating an autocomplete field.
#665207 - Data of unhistorized field not sent to DWH on manual update
When a field had the settings Transfer to DWH and Field value omitted from history both set to true, updating its value in an entity and performing a manual DWH update did not send the new value to the DWH database. This problem has been solved, and now the new field data is correctly updated in the DWH when a manual update is performed.
#665223 - Unable to upload attachments in CM/Track V3 on Oracle when whitelist is empty
When using CM/Track V3 with an Oracle database and the system property attachment.allowed.types from the module cmas-core-server was empty, it was not possible to upload any file, although all file types should be allowed. This problem has been solved, and it is now possible to upload attachments when the property is empty.
#665230 - Fixed-point number field is filled with data from other field
When editing an entity in the Web Client, it could happen that fixed-point number fields were incorrectly filled with data from other fields, preventing saving the entity due to invalid data. This issue has been resolved and fixed-point number fields are no longer pre-filled in this way.
#665259 - Wrong escalation times for different time zones
When using a business calendar with a different timezone than the user's timezone, holidays were not considered correctly for time triggers. This problem has been solved, and holidays are now correctly calculated for time triggers, even if the calendar has a different timezone than the user.
#665271 - Editor not focused for newly created scripts
When creating a new script on the Scripts page in the Web Admin Suite, the script editor was not automatically focused, requiring users to manually click into the editor to start typing. This problem has been solved, and the editor is now automatically focused when a new script is created.
#665319 - Broken autocomplete field when there are other validation errors
When there are validation errors due to incorrect content in some fields during the creation of a case in CM/Track V3, it was not possible to select the value for an autocomplete field, and an error was written to the log files. This problem has been solved, and autocomplete requests can now be handled although invalid data was entered in other fields on the case creation page.
#665325 - Wrong number of cases displayed in detail search results
When the number of results per page in the detail search of the Web Client was changed, and the user navigated to another page and returned to the detail search later, the number of displayed results reverted to the default instead of the selected number. This problem has been solved, and the selected number of results per page is now correctly retained when returning to the detail search.
#665486 - Online help links stopped working (#665486)
The links to the manuals in the Documentation section of the Troubleshooting page within the Web Admin Suite stopped working due to changes to the documentation structure. This problem has been solved and the links point to the correct manual locations now.
#665502 - Case history not refreshed when opening cases via URL in CM/Track V3
When opening a case in CM/Track V3 via a URL, the case history from the previously opened case was displayed instead of the correct history for the current case. This problem has been solved, and the case history is now correctly loaded when opening a case from a link.
#665763 - Workflow error when placing decision node after time trigger
When designing a workflow where a decision node was placed directly after a time trigger attached to an activity which is connected to a scope activity, an error occurred when a case entered the respective flow. This problem has been solved and such a workflow is executed correctly now.