Quality Clouds 23.16.0.0 Release Notes
Release date: November 29th , 2023
New general improvements
Debt Manager dashboard provides a unified data view across all tabs.
Pre-requisites: Have access to the Debt Manager dashboard.
Description:
The structure and organization of the data provided in the Debt Manager dashboard for all platforms (ServiceNow, Salesforce and Office 365), have been updated. By default, all tabs (Open, Closed Written Off, and Closed) display the data in the columns and the filters in a the same order.
→ How to access the data in the Debt Manager dashboard:
- Log into the Quality Clouds Portal.
- Go to the Debt Manager dashboard.
- Click across the Open, Closed (Written Off) and Closed (Fixed) tabs of the dashboard.
- Each of the tabs displays the same columns, and in the same order.
- Check the data included by default in the graph from the Debt Manager dashboard in the Open issues Debt Manager tab.
-
-
- Check the data included by default in the graph from the Debt Manager dashboard, in the Closed (Written Off) issues tab.
-
- Check the data included by default in the graph from the Debt Manager dashboard in the Closed (Fixed) issues tab.
Use cases:
Customers who have already modified the column order in the Debt Manager dashboard will retain their customised data grid view, and the default option will not be applicable to them.
In order to customise the column order presented on the Debt Manager dashboard, the option to enable or disable specific columns to display is available.
The customers who would like to change the order of the columns displayed, can drag the specific column to the preferred order to be displayed in the grid.
Filters in the Peer Review dashboard work in cascade mode.
Pre-requisites: Have access to the Peer Review dashboard.
Description:
There is a requestor filter in the Peer Review dashboard that shows who requested the write-off for review. The approver filter shows the user who was assigned to approve that write-off. Now it is possible to apply the filters in cascade mode, so that when a filter is selected, only applicable values will be available in the remaining filters.
Write-off expiration event is shown in the "Issue Activity" tab in the Peer Review details drawer
Pre-requisites: The Peer Review feature must be enabled, and the permissions to access the Peer Review dashboard must be granted to the user.
Description:
When a write-off is temporarily approved, after the selected expiration date for the approval has gone by, a new entry is created in the "Issue Activity" tab in the Peer Review details drawer. The value for the "Action" column on this entry will be "Issue reopened due to write-off expiration.", and the date will be the date of expiration of the write-off approval.
→ How to access the Issues Activity tab.
Log into the Quality Clouds Portal.
Go to the Peer Review dashboard.
Select the write-off you would like to check (this write-off should have been granted temporary approval, and the approval expiration date should have ellapsed).
Go to the "Issue Activity" tab.
Check entry with the "Issue reopened due to write-off expiration." value in the "Action" column.
- Note that the Peer Review status will remain as "Done", since no further action is expected on this Peer Review.
New format for the write-off expiration email.
Pre-requisites: When a write-off is granted temporary approval and the approval date is reached, both the user who requested the write-off, and the user who approved it, will be notified via email.
Description:
The contents of the email have been simplified and re-organised. The new email structure is as follows:Peer Review ID: The Identification number assigned to the Peer Review Write-off.
Affected element: The Configuration Element on which the issue which was written-off was found.
Issue type: The issue for which the write-off was requested.
Requester: The user who requested the write-off.
Action: A link open the configuration element in the instance. If the issue is on a ServiceNow instance, running a new LiveCheck will show the issue status as "Active" again.
Improved User Experience when copying a ruleset across instances
Pre-requisites: Admin account permission to access rulesets in the Admin portal.
Description:
It is possible to copy the ruleset customisations made in one instance to a different instance. That functionality is unchanged, but since the process can take a long time, the user experience has been improved, including a spinner which shows that the process is running, and giving explicit feedback once the process completed. The notification message: "You have now copied the ruleset to the selected instance" will confirm the action once it is completed.
→ How to verify the copy of a ruleset:
Log into the Quality Clouds Admin Portal.
Go to the "Rulesets" section.
Select a ruleset that you want to copy to another instance in the same platform
Select an instance and confirm to copy a ruleset and wait till the process is completed.
A message confirming the action will show up.
Date format under European and American style is consistently applied across all dates in the dashboards:
Pre-requisites: Must have a Customer Admin role to modify/edit users.
Description:
The Quality Clouds portal now displays the date format in all date fields in all the dashboards in both EU and US styles. Previously, some date fields were ignoring this setting. Dashboards showing this improvement include Code Monitor, Multiple Instances, and Release Management.
EU date format style: month/day/year
US date format style: day/month/year
→ How to change the date format
Log into the Quality Clouds Portal.
Go to "Users" in the Account section.
Select the user and click the "Edit user" icon.
Go to "Time Format" dropdown and choose either EU or US based on your preferences..
Click "Save".
New ServiceNow Best practices
There are no new ServiceNow Best Practices included in this release
New Salesforce Best practices
New PMD rule for Salesforce (SF-AVOID-MSG-IN-LOOP).
Description:
This best practice focuses on preventing governor limit issues by avoiding messaging operations within loops. To achieve this, batch up data into a list and send messages outside the loop, ensuring improved system performance and stability.
New PMD rule for Salesforce (SF-AVOID-APPROVAL-IN-LOOP).
Description:
This best practice aims to optimize approval operations by avoiding potential governor limit issues associated with executing approval processes inside loops. To address this, batch up data into a list and invoke approval processes once on that list outside the loop.
New PMD rule for Salesforce (SF-AVOID-ASYNC-IN-LOOP).
Description:
This best practice aims to enhance efficiency by preventing potential governor limit issues. To address this, batch up the data into a list and invoke async processes once on that list outside the loop.
New rule for Salesforce (SF-AVOID-FUTURE-IN-LOOP).
Description:
This best practice aims to ensure effective exception handling by preventing the override of exceptions thrown in previous try/catch blocks when throwing an exception in a finally block. To address this, remove the throw statement in the finally block and utilize a catch block for throwing exceptions.
New rule for Salesforce (SF-AVOID-THROW-FINALLY).
Description:
This best practice aims to enhance efficiency by avoiding potential governor limit exceptions associated with invoking a future method inside a loop. To address this, accumulate all the requests that need to be made and pass them off in a single call to the future method.
Bug fixes
Catalog items included in multiple Catalogs are now included in the count of items.
Bug explanation:
The number of Catalog Items in the Catalog View was not including items assigned to multiple catalogs.
Solution:
Items included in multiple catalogs are now correctly counted in the total amount of items displayed in the Catalog View.
The number of catalog and catalog items shown in the dashboards will reflect the items visible to the user running the full scan. This may be different than the total number of items in the instance if there are security-sensitive catalogs and/or items in the instance.
Incorrect write-off statistics data displayed in the Peer Review drawer.
Bug explanation:
The data points which show the statistics of Peer reviews requested, approved and rejected per developer included in the Peer Review details drawer were displaying incorrect information.
Solution:
The three data points are now correctly calculated.Incorrect margins when zooming for larger screen in the Write-off drawer.
Bug explanation:
When zooming with very high resolution, margins were not adapting properly in the drawer which shows the details of a write-off.
Solution:
Margins are now adapted according to the size of screen.
Debt Manager dashboard load time improvements.
Bug explanation:
The Debt Manager dashboard performance took 8 second to charge.
Solution:
After some improvements in the structural architecture, we have successfully optimized the loading time, reducing it from 8 to 4 seconds.
Peer Review drop-downs and menus.
Bug explanation:
In the Peer Review dashboard, when trying to enable one specific data from a dropdown menu, it selected all the data included in that menu.
Solution:
The bug has been fixed by enabling/disabling only the data selected in any dropdown menu.
Inconsistent data shown in the number of issues in the Profiling report.
Bug explanation:
In the Profiling dashboard, when viewing the data from the report, the number of issues were incorrect, as Warnings were included in the count.
Solution:
The bug has been fixed, and now the proper value of the issues is shown correctly, with warnings being excluded.
Incorrect Configuration Elements variation in the Profiling report.
Bug explanation:
In the Profiling dashboard, when viewing the data from the report, the Configuration Elements variation was incorrect.
Solution:
The bug has been fixed, and now it shows the proper variation and proper colors to identify its impact (if decreases in green, if increases in red).
Note that usually when a value decreases, it is represented in green (indicating a positive outcome), and if it increases, it is shown in red (indicating a negative outcome); however, this is not always the case, as sometimes an increase could also be indicative of a positive metric. |