Quality Clouds 24.8.0.0 Release Notes

Release date: 5th of June

New general improvements #

1. Execution of the Update Set Scan through the Quality Clouds Admin portal #

Pre-requisites: To have an instance connected where the Application is configured in Quality Clouds. To have configured a user with Admin permissions at an instance level OR the latest version of the non-admin configuration Update Set (available here).To have enabled the Scan Launcher permission for specific users in the Quality Clouds admin portal.

Description:
When launching a Scan using the Admin portal, five different type of scans are available: Full Scan, Profiling Scan, Application Scan, Update Set Scan and Operational Scan. The Update Set Scan is the Scan performed at an Update Set level, across a group of Configuration Elements in the same instance.

In order for the list of `In Progress´ Update Sets to be populated in the drop down menu when the Update Set Scan type is selected, the instance must have been either configured with an admin user for Full Scans, OR the latest version of the non-admin configuration Update Set must have been applied to the instance.

For non-admins, the latest version of non-admin configuration Update Set includes the necessary ACLs for the qc_access role to have read-only access to the Update Sets table.

It is possible also to launch this type of scan by selecting the Manual Entry option in the Update Set Scan drop-down menu which requires providing the Update Set name and the Sys Id of the Update Set which will be scanned.

In the Update Set drop-down menu we can see the Manual Entry option, as well as all `In progress´ Update Sets.

By clicking on ‘Manual Entry‘, it is possible to manually specify the Update Set Name and the Sys Id as we can see in this image.

Once the data is introduced and by clicking Yes, the Update Set Scan starts running.

Once the Update Set Scan has successfully finished it is possible to see the related data in the Live Check view by clicking on the Update Set Live Check tab in the Live Check view on the Quality Clouds Main Portal. It is possible to see all the Update Set Live Checks performed from the Quality Clouds admin portal in the source column as PORTAL or those launched from the application in the source column as APP, as we can see in the Live Check view image.

Also it is possible to see the results in the History tab in the Quality Clouds Admin portal by clicking on the Update Set Scans tab.

→ How to find the Sys Id number for an Update Set:

1. Go to the ServiceNow instance.
2. Look for the Local Update Sets at the top left of the instance in the ‘ALL‘ menu.
3. Select the Update Set that you would like to scan.
4. Once selected, right click on the grey part of your Update Set in the top part of the screen.
5. One of the menu options will allow you to Copy the sys_id to your clipboard directly.

→How to launch an Update Set Scan in the Quality Clouds Admin portal:

1. Go to Quality Clouds Admin portal.
2. Click on the Launch Scan tab.
3. Select the instance you want to scan.
4. Select Update Set in the ‘Scan type’ drop-down menu and then click on Launch Scan.
5. A pop up will appear in order to select the name of the Update Set to scan. If it doesn’t appear in the drop-down menu then it will be necessary to select Manual Entry.
6. Type the Update Set Name and the Sys Id number, clic Yes and start scaning.

Impact: To scan an In Progress Update Set in your instance, even if the Quality Clouds for ServiceNow application is not installed in that instance.

Use cases:

2. OmniStudio elements of a specific Org are now scanned by our VSCode Extension for Salesforce #

Pre-requisites:

1. You need a ORG Salesforce instance configured in Quality Clouds.
2. Your ORG should contain OmniStudio elements.
3. You need a user with full scan launcher permission.
4. Visual Studio Code version 2.1 installed.
5. A user with admin permissions.
6. An API key enabled.

Description:
OmniStudio is a modular system with standard click-based components to quickly build Salesforce flows and solutions. OmniStudio effortlessly meets the supply needs of the Omnichannel service, implementing and updating these interactions in different channels and devices. We have included these Configuration Elements from Salesforce in the Quality Clouds platform.

LiveCheck for Salesforce requires Visual Studio Code which is a free source-code editor made by Microsoft for Windows, Linux and macOS. It is used for building and debugging modern web and cloud applications.
You can install the extension directly from your editor or by going to the Visual Studio Marketplace. 

Check how to manage your code here.

This is how it looks when launching a Livecheck for Salesforce in Visual Studio Code:

Impact: To scan the OmniStudio elements during development across all Orgs, ensuring effective governance of changes to these crucial configurations.

Use cases:

3. Update Set Name visible in the Peer Review view #

Pre-requisites: To have access to the Peer Review view.
Description:
In the Peer Review dashboard it is possible to track the evolution of the different Peer Reviews requested.
We now capture and display the update set for the change.
It is necessary to follow these steps:

1. Run a live check in ServiceNow on a Configuration Element. Note down the Update Set that the Configuration Element belongs to.
2. Make a Write off request on an issue.
3. Go to Peer Review view. The Update Set Name should be displayed for the Write off request that you made.

→ How to check the Update Set Name in the Peer Review view:

1. Go to the Quality Clouds Portal. 
2. Look for the Peer Review view.
3. On the grid tab at the right part of the view, the Update Set column will be displayed if added to the table configuration.
   

Impact: To properly identify the Update Set Name in a specific Peer Review.

Use Cases:

4. Display of Last Scan Type for Instance in Scan Launcher Page #

Pre-requisites: Permissions available depending on the type of scan to launch.

Description:
There are five different types of scan available in the Quality Clouds admin portal: Full Scan, Profiling Scan, Application Scan, Update Scan and Operational Scan.

Now it is possible to properly identify:

→ How to launch a scan :

1. Go to the Quality Clouds admin portal.
2. Click on the launch scan tab.
3. Select the platform (Salesforce, ServiceNow or Office 365).
4. Select the instance you would like to scan.
5. Select the type of Scan you need to launch.
   

5. The application column in the Debt Manager view has been renamed as Package Name in Salesforce

Pre-requisites: To have access to the Debt Manger view.

Description:
There are functionalities packaged together for distribution and installation in different Salesforce orgs. When accessing the Debt Manager view in a Salesforce instance, it is possible to see the Package Name information as a new column displayed in the issues Grid.

New Salesforce Best practices #

• Avoid Large Omniscript

New rule for Salesforce (SF-AVOID-LARGE-OMNISCRIPT)

Description:

This rule explains that large Omniscripts bigger than 4MB can cause low performance, so their size should be reduced to improve efficiency.

• Avoid Inactive Flows

New rule for Salesforce (SF-AVOID-INACTIVE-FLOWS)

Description:

This rule explains that inactive flows may cause clutter in the Salesforce org, so they should be removed if not used.

• Avoid Record-Triggered Flows Without Entry Criteria.

New rule for Salesforce (SF-AVOID-RECORD-TRIGGERED-WO-CRITERIA)

Description:

This rule explains that not specifying entry criteria in record-triggered flows can lead to unnecessary executions and negatively impact system manageability and performance, so ensure all such flows have appropriate entry criteria

Bug fixes #

2. Enhanced validation for Sys ID field in Application and Update Set Scans

Bug explanation:

The ‘Sys ID’ field allowed the entry of more than 32 characters, and the ‘Yes’ button is improperly enabled when a non-matching Sys ID value is entered during manual entry in both application and Update Set Scans.

Solution:
Now the ‘Sys ID’ field enforces a maximum length of 32 characters. Ensure the ‘Yes’ button is only enabled when the Sys ID matches the required regex and is 32 characters in length.

Bug explanation:
When programming scans for automatic launching, a specific scheduled scan shifted from one day to another.

Solution:
Now the Scan schedule is working properly.

4. Two manageability issues incorrectly detected by rule.

Bug explanation:
Two Manageability elements were wrongly identified as an issue related to System Property CE type.

Solution:

The issues are not generated any longer.

5. Issues identified in Scan were not loading properly in the History tab.

Bug explantion:
Information about the Issues from a Scan were not fully loaded in the Scan History tab.

Solution:
The information in the History tab related to the issues identified is now properly displayed by clicking on the Actions column on the three dots icon, in the Quality Clouds admin portal.