Efecte Service Management Tool 2023.2.1 release notes
Efecte Service Management Tool 2023.2.1 release notes
Executive Summary
The Efecte Service Management Tool 2023.2.1 minor version includes several bug fixes found during QA activities. The bug fixes are related to the early access beta UI renewal introduced in version 2023.2.0, which included a large number of new UI capabilities. The 2023.2.1 is the first general availability (GA) version, which is distributed to Efecte customers.
The Efecte Service Management Tool (ESM) 2023.2.0 major version introduced an early access beta version of the new user interface (UI). Admins can opt-in to the early access beta version by turning it on in the application's platform settings. In addition to the new beta UI, the release included one new feature and three bug fixes.
The 2023.2 release also introduced features, improvements and fixes related Efecte Provisioning Engine (EPE) and Efecte Secure Access (ESA). A beta version of the Efecte Chat reports dashboard was included in the release.
Since 2022 Q4 release, the release notes for ESM are provided via docs.efecte.com. If a .pdf version of the release notes is needed, it can be printed using the “Print to PDF” button. Previous release items can be found Efecte community.
More information available in Efecte community
More information about the released features as well as features already roadmapped can be found from the Efecte Community (https://community.efecte.com/)
The following article provide an overview of current and upcoming datacard view capabilities: https://community.efecte.com/t/q6hc2vj/sneak-peek-to-the-new-data-card-view
How to access and enable the early access beta UI
The early access beta UI is available for cloud and private cloud environments. The beta UI is not available for on-premise installations running on Windows or Linux servers.
The early access beta UI can be accessed by adding /beta after the environment's URL.
Example: https://environment.efectecloud.com/itsm/beta
The early access beta UI can be made accessible through the user interface by enabling the following platform setting. The setting is enabled by assigning the value true in it. The setting default to false. The platform settings can be accessed by navigating to the Admin UI -> Maintenance -> System settings -> Edit platform settings.
new.ui. switch. enabled = true | false
Enabling this setting will introduce a new button to the right-hand side of the header bar. The button is used for navigating between the classic (current) UI and the early access beta UI. The button text indicates which UI the user is currently using. CLASSIC means the current UI, while BETA means the early access beta UI.
The user is in the current UI:
The user is in the early access beta UI:
The early access beta UI can always be accessed through the URL
Please note that the early access beta UI can be accessed through the URL regardless of the platform settings' value.
Making the new UI default for users
The following platform setting can be used for making the early access beta UI the default option for users when they login to the application. The setting defaults to False. Since the new UI is an early access beta version in ESM 2023.2.0, enabling the following setting is not recommended while using ESM 2023.2.0.
new.ui.as.default = true | false
Later, once the new UI covers more of the necessary functionalities used on a daily basis by most of the users, it is recommended to turn the setting on.
Bug fixes
- CP-7468: The attachment font size is bigger than other texts
- The attachment font size was adjusted to match with other value texts.
- CP-7490: The ticket partly in edit, and only the edit button is visible
- Fixed. In certain scenarios, with certain user navigation flows, it was possible to end up in a situation in which the datacard was in a partial edit mode.
- CP-7501: The ticket does not fit into the screen vertically
- Fixed. Datacards did not fit into the screen when certain layouts were used.
- CP-7472: Other than text file attachments cannot be downloaded
- Fixed. Now attachments can be downloaded normally.
- CP-7469: Beta UI Oops something went wrong error
- Fixed. Navigating to the new early access beta UI from unsaved list views in the classic UI resulted in an error.
- CP-7461: Excessive line spacing in text attributes
- Fixed. When a text value with line spaces written in the classic UI was viewed or edited in the early access beta UI, the text got excessive line breaks.
- SUMA-41079: "Select all" checkbox does not select the rows if clicking outside of the box or the checkbox borderline
- The fix adjusted the clickable area of the checkbox to make it work if the user clicks on the grey area or the borderline. Still, there are some very small areas on the borderline or close to the borderline which are not working - these will be addressed in the future in SUMA-41710.
- SUMA-41103: Global search template selection firing request also when selecting the same template
- This fix optimized the API calls sent by the user interface to the backend. The fix did not introduce any visible changes to the users.
- SUMA-41119: Static attributes are not filled automatically when going into edit mode or new mode when using the Firefox browser
- This fix ensures that static string attributes show their values correctly.
- SUMA-41127: When deleting a datacard, the user is navigated back to the previous page instead of handling it correctly
- If the user navigated from Edit mode → View mode and then deleted the datacard, the user was navigated back to edit mode of deleted datacard. The flow has been fixed.
- SUMA-41135: Wrong popup when saving datacard after populating attachments to FileUpload handler
- Fixed. The Discard changes dialog was shown in the wrong scenario (when saving datacard after populating attachments to FileUpload handler).
- SUMA-41136: Email attribute shows the message "... cannot be displayed..." right below the content
- Fixed. The "This information cannot be displayed" message was removed from the EntityStateMail handler.
- SUMA-41144: New view button does not work, although it interacts when the user clicks on its border
- The button was fixed.
- SUMA-41152: The navigation panel is empty when it includes old E6 bookmarks
- Fixed. If the navigation panel included old \(E6\) views, it was not able to show any views.
- SUMA-41160: Click on the edit button in a list view item redirects to datacard edit mode. Cancel the edit and now clicking on New email message does not open an email editor
- Fixed.
- SUMA-41161: Navigating from Classic to Beta UI from a view that is not supported throws an error and crashes the navigation panel & startup view not correctly navigated
- Fixed. Now the user is navigated properly to the home page (the user's startup view if it is defined in the user profile settings).
- SUMA-41218: Save button does not activate right away when entering/changing a value
- Fixed.
- SUMA-41226: Code snippet formatting does not have the grey background as in the SF demo
- Fixed, now the code font style has a dark background in edit mode. The view mode is planned to be tackled in SUMA-41720 in the future.
Note related to the rich text editor font styles
Please note that the various heading, code, and quote font styles require the following values in the html.allowed.tags platform setting: pre, blockquote, h1, h2, h3, h4
- SUMA-41283: Datacard delete throws an error when deleted in edit mode
- Datacard deletion is prevented in edit mode by removing the alternative from the three-button dropdown menu.
- SUMA-41296: The email link leads to an error page.
- The email links were replaced with green icons indicating unread emails.
- SUMA-41305: Websocket connection is not working in some environments
- Fixed.
- SUMA-41353: The rich text editor overlaps with the profile settings with a narrow window
- Fixed.
- SUMA-41372: Display datacard viewers when there is more than one viewer
- The datacard viewers (swarming) feature was disabled in the new UI. The feature will be enabled as part of SUMA-41730 in the future.
- SUMA-41391: Change the "Oops something went wrong" error text
- The error text was changed to “Something went wrong. If the issue persists, please contact your administrator.”
Need help?
Do you need help, or you have suggestions or change proposals?
Please contact the Efecte Service Desk (servicedesk@efecte.com) if you have any questions or change proposals regarding the latest release.
Table of Contents