Quality Clouds 24.3.0.0 Release Notes
Release date: February 21st, 2024
New general improvements
Peer Review Dashboard Enhancements
To identify any Peer Reviews by change set in the Peer Review dashboard
Pre-requisites: Have the Peer Review feature enabled and have access to the Peer Review dashboard.
Description:
The Peer Review dashboard provides the information related to the write-offs requested by the developers using the Quality Clouds application in ServiceNow and Salesforce.
As a user of the Peer Review dashboard, it is possible to quickly identify any Peer Reviews by change set applying specific filters.
The name of the filters to identify a Peer Review by change set in ServiceNow is Update Set and Feature Branch in Salesforce. The Update Set filter will show the peer reviews requested on issues found in the ServiceNow Update Set Scans. The Feature Branch will show the peer reviews requested on issues found in the Salesforce Feature Branch scan.
→ How to use the new filters on Peer Review dashboard :
- Log into the Quality Clouds Portal.
- Select ServiceNow or Salesforce instance.
- Select the Peer Review dashboard on the 'View' tab.
- On the top of the Peer Review dashboard, select the date range.
- Select the Change Set name according to your SaaS platform.
The concept of Change Set is implemented in different ways depending on the SaaS platform.
For ServiceNow:
The Change Set name in the Peer Review dashboard filter is called the Update Set. In this example, the Change Set name is QAT-689 so the card also shows the write-off required (Peer Review) but resulting from the issues found in the Update Set scan.
By clicking on one specific write-off card additional information shows a drawer where the name of the Update Set change set can also be tracked.
In the Peer Review grid an additional column with the name Update Set has been added to track the write-offs by Change Set. This new Column will appear in the Peer Review grid, at the end of the existing columns, for ServiceNow instances with the Update Set name.
This column will show a blank value for peer reviews requested on issues detected in all types of scans which are not ServiceNow Update Set Scans.
For Salesforce:
The Change Set name in the Peer Review dashboard is the Feature Branch. In this example, the Change Set name is WI-000005 so the card also shows the write-off required (Peer Review) but resulting from the issues found in the Feature Branch scan.
By clicking on one specific Peer Review card (A write-off requested), additional information shows a drawer where the name of the feature branch can be also tracked.
In the Peer Review grid an additional column with the name Feature Branch has been added to track the write-offs by change set. This new Column will appear in the Peer Review grid, at the end of the existing columns for Salesforce instances with the filter Feature Branch. This column will show a blank value for peer reviews requested on issues detected in all types of scans which are not Salesforce Feature Branch Scans.
→ How to find the new Peer Review dashboard:
- Log into the Quality Clouds Portal.
- Select ServiceNow or Salesforce instance.
- Select the Peer Review dashboard on the 'View' tab.
- On the top of the Peer Review dashboard you can select the Feature Branch box.
- By filtering the Feature Branch you will see the peer reviews by Change Set.
Impact: To increase the level of productivity to organise the write-offs workflow.
Use cases:
- The information related to Update Set or Feature Scan only informs for peer reviews requested on issues found on ServiceNow Update Set Scans or Salesforce Feature Branch.
Peer Reviews created from ServiceNow and Salesforce CE LiveChecks do not include the Update Set name.
NOTE: In future releases this option will be available for CE live checks.
- Write-off notifications emails can be configured in the email grid in the Quality Clouds Admin Portal.
Pre-requisites: The Customer Admin role must be enabled.
Description:
The E-mail grid notifications section in the Quality Clouds portal provides the information related to the type of emails that users can receive from the Quality Clouds portal activity.
For Peer Review notifications to enable notifications for users in the E-mail grid implies that a user can be assigned to a Peer Review requested so now it is possible for Customer Admin role to manage the subscribers to the "Peer Review Notification" event through the mail grid. Previously, only the Quality Clouds Admins were able to manage subscriptions.
The requestor of a Peer Review still receives notifications about approvals or rejections. The requestors and the approvers still receive notifications about Peer Review activity (Peer Review expirations) and the default approver still receives reminders about Peer Reviews (Pending for approval or rejection, a Peer Review about to expire).
→ How to find the E-mail grid notifications:
- Log into the Quality Clouds Portal.
- Go to the Admin Portal.
- Click on the Account tab.
- Select the E-mail notifications tab.
- Enable the notification for the users required.
*In future releases the notification system will be improved to select who is going to receive notifications.
Impact: Increase the level of organization at Customer Admin level.
Use cases:
- In order for a Peer Review Approver to receive a notification when a Peer Review is assigned to them, they need to have been explicitly subscribed to the 'Peer Review Notifications' event in the email grid.
The default assignee is no longer automatically subscribed to the 'Peer Review Notifications' event in the email grid.
- New Configuration Element in ServiceNow
Pre-requisites: Access to the Executive and Code Monitor dashboards.
Description:
Inline Scripts enable Flow Designer users with coding experience to write scripts that set and modify input values during the configuration of an action or flow. Inline scripts should be used to modify input values that require small format conversions, data transformations, or math operations. As of this release, Inline Scripts are analysed by Quality Clouds, both from a code quality and from an inventory point of view. This means that any Inline Script which has been added to your instances, or any out of the box inline script which has been modified, will appear in the inventory dashboards (especially Code Monitor). Additionally, six rules have been added to the ruleset to be evaluated against the code in Inline Scripts.
In all dashboards where you can filter by configuration element, the new configuration element 'Inline Script' will now be available.
→ How to filter by Configuration Element:
- Log into the Quality Clouds Portal.
- Select ServiceNow instance.
- Go to the 'View' tab and select the dashboard of your preference.
- Go to 'CE Type' and look for Inline Script.
-
- You can also go to 'Issue Type' and look for the issues that contain Inline Script configuration element.
→ Code Monitor Dashboard:
In the Code Monitor Dashboard, Inline Scripts will be shown as a new Configuration Element type. Differences between the numbers of detected Inline Scripts in different instances will be shown in the Code Monitor Dashboard, just as for all other Configuration Element Types.
Impact: This configuration element is available to all users (Normal user, Customer Admin, and Project user) and ServiceNow platforms.
New ServiceNow Best practices
New rule for ServiceNow (SN-INLINE-SCRIPT-MAX-LINES-CODE).
Description:
This rule monitors the length of code lines in Inline Scripts. Since Inline Scripts are meant for simple tasks like format conversions or math operations during action or flow configuration, an excessive amount of lines of code indicates that the Inline Script is not being used for its intended purpose. The rule has a default threshold of 10 lines of code, but this can be increased or decreased to comply with your development standards.
Existing ServiceNow rules which now apply also to Inline Scripts:
The below rules were already existing in the default ruleset. As of this release, they are also applied to the Inline Script Configuration Element type:
- SN-0421: Use of GlideRecord and getRowCount
- SN-0411: Usage of gs.cacheFlush() on Scripts
- SN-0390: Scripts directly call to Java packages
- SN-0377: Dot walking to sys_id
- SN-0372: Unlogged API call error condition.
New Salesforce Best practices
New rule for Salesforce (SF-EXCEPTION-NOT-EXTEND-EXCEPTION).
Description:
This best practice ensures proper exception handling.
New rule for Salesforce (SF-AVOID-USING-HTTP-REFERER).
Description:
This best practice aims to enhance security by mitigating the risk associated with modified HTTP Referer headers.
Bug fixes
- Warnings incorrectly classified as baseline issues in ServiceNow application
Bug explanation:
Issues of severity Warning which were introduced after the Quality Gate activation date were being incorrectly classified as "Baseline" in the ServiceNow Quality Clouds application, after running a LiveCheck. Note that this was having no impact on Quality Gate evaluation since Warnings never break Quality Gates.
Solution:
These Warnings are now shown in the "Active Issues" tab in the ServiceNow Quality Clouds application.
- The 'Expiration date' column in the Open tab of Debt Manager has been removed
Bug explanation:
The "Expiration Date" column in the Open tab of Debt Manager caused confusion because open issues didn't have the write-off expiration date.
Solution:
The 'Expiration Date' column has been removed to avoid unnecessary elements for managing open issues.
- The 'Expiration date' filter in the Open tab of Debt Manager has been removed.
Bug explanation:
The "Expiration Date" filter in the Open tab of Debt Manager is causing confusion because open issues don't have the write-off expiration date.
Solution:
The 'Expiration Date' filter is been removed to avoid unnecessary elements for managing open issues.
- Accurate Display of Write-Off Approval Status in Peer Review dashboard
Bug explanation:
In the Peer Review dashboard, the newly requested write-offs appeared as pending with a 'Done' status.
Solution:
Newly requested write-offs are shown as approved with the right date and status.
- Sorting Bug Fixed for Improved Functionality
Bug explanation:
In the Admin portal, the API keys section had an issue where sorting was enabled but not functioning correctly.
Solution:
When sorting the columns, the functionality works correctly.
- Introducing Autoscroll for Seamless Column Management
Bug explanation:
Managing the column order in the dashboards by moving items from the bottom to the top or vice versa in the table configurations was very challenging.
Solution:
An autoscroll feature has been introduced which allows items to move seamlessly up or down the list when configuring a table.