Quality Clouds 23.13.0.0 Release Notes


Release date: September 27th , 2023

New general improvements


  •  Auto-closed property, when rewriting the rule

Pre-requisites: Customer Admin is the only role with Admin permissions that can modify rulesets in Quality Clouds platform.

Description:

A rule is rewritten, when the severity and time to fix change. This implies that, after launching a full scan, the issues will be automatically closed (auto-closed property), and will no longer be visible in the 'Closed' (fixed) tab in the Debt Manager dashboard.

Previously, on the Debt Manager dashboard, when an admin user changed the severity and/or time to fix in a default rule, the issues that were closed automatically were in the "Closed tab" after a full scan. 

This release ensures that the only issues that appear in the "Closed tab" in the Debt Manager dashboard are the ones closed by developers. This improvement will affect all the customers using ServiceNow, SalesForce, and Office365.

Remember that changing the time to fix will directly impact the technical debt.

How to:

How to change the severity or time to fix in a default rule?

    1. Log in QC platform.
    2. Access to admin portal.
    3. Navigate to the "Rulesets" section.
    4. Choose the specific instance in which you want to change the severity and/or time to fix.
    5. In the "Severity" field, change the severity and/or in the "Time to fix" field, change the time.
    6. Click Save.



→ What is a rewritten rule? 

A rewritten rule is a rule that has been edited by changing the severity and/or the time to fix.


→ What happens after you rewrite a rule? 

A) In the Rulesets grid, for rules that have been rewritten, a new icon is available to reset the rewritten rule to its default state.



B) In the Rulesets grid, if you click on the edit icon of a rule, you can restore the severity or time-to-fix values to their default rule.



Use cases:

    • You can not change the severity and time to fix of an ignored rule, you need to enable the rule.


  • Filter removed in the Update Set Scan

In the 'History' section of the admin portal, the 'provider' filter has been removed when viewing Update Set Scans because it only operates in the ServiceNow platform.

Bug fixes

  • Inconsistencies between Code Monitor and Governance view (number of lines of code)

Bug explanation:

Previously, after launching a scan, Code Monitor and Governance View (ServiceNow and Salesforce platforms) displayed an inconsistent number of lines of code due to a calculation error. 

Solution:

We fixed the bug by correcting the calculation method for lines of code.

Remember that in Salesforce, both Code Monitor and Governance View consistently display the same lines of code because OOTB elements cannot be modified. However, in ServiceNow, where OOTB elements can be customized, Code Monitor and Governance View can show different values, accurately reflecting customization.



  • When scrolling down the notifications tap on the Admin Portal, new notifications appear correctly in 24 inch screen and below.

  • The PDF downloaded from "Multiple Instances View" has no format issues on the top section.





Last modified on Oct 10, 2023