Quality Clouds 24.7.0.0 Release Notes

Release date: 15 of May, 2024

New general improvements #

1. OmniStudio elements of a specific Org are now scanned by the Full Scan 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.

Description:

OmniStudio is a modular system with standard click-based components to quickly build Salesforce flows and solutions. OmniStudio effortlessly satisfies 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 and have also included our first two best practices for Omni.

We have implemented four types of OmniStudio Configuration Elements:

– DataTransforms: DataRaptors support the retrieving, transforming and updating of data.
– IntegrationProcedures: Integration Procedures allow you to retrieve information from third-party services.
– OmniScripts: An OmniScript gives customers a guided path for completing a business process and works as a configurable way of creating a seamless customer experience. OmniScripts let you configure sequences for sales, services paths, and other business processes.
– OmniCards: Represent the structure, data source, content and styling of the card. FlexCards summarize and display contextual data and actions, both from Salesforce or third-party systems.

→ How to access the OmniElements in your Salesforce Executive view:

1. Go to Quality Clouds Portal. 
2. Click on your Salesforce instance.
3. Select the view Salesforce Executive in the dropdown menu.
4. Click on the Inventory tab.
5. Click on Packages.
6. Search for the OmniElement you would like to check on the Configuration Elements Type drop-down menu.
   

Impact: A comprehensive visibility into OmniStudio elements across all Orgs, ensuring effective governance of changes to these crucial configurations.

Use cases:

2. Execution of the Application Scan through the Quality Clouds Admin portal only for ServiceNow #

Pre-requisites: To have enabled the option to launch the Application Scan in the Admin portal. To have an instance connected where the Application is configured in Quality Clouds.

Description:

When launching a Full Scan using the Admin portal, four different type of scans are available: Full Scan, Profiling Scan, Application Scan and Operational Scan. The Application Scan is the Full Scan performed at an application level, which means scanning all the changes made in an application.

It is possible to launch this type of scan by selecting the Manual Entry option in the Application Scan drop-down menu that requires providing the Application name and the Sys Id number if an application has never been scanned. If the application has been previously scanned through the Quality Clouds Admin portal, then it will be visible in the Application Scan drop-down menu.

By clicking on ‘Manual Entry‘, it is possible to include the Application Name and the Sys Id number as we can see in this image.

Once the application Scan has successfully finished it is possible to see the data related in the Live Check view by clicking on the Applications Live Check tab.

Also it is possible to see the results in the History tab in the Quality Clouds Admin portal.

→ How to find the Sys Id number for an application:

1. Go to the ServiceNow instance.
2. Click on the World icon at the top right of the instance.
3. In the Application Scope option click on the right arrow.
4. Click on the three dots symbol.
5. A screen to find the name of your application will appear so type the Application Name in the name search bar.
6. Click on the name of the application.
7. Right click on the grey part of your application in the top part of the screen.
8. A menu will show you the Sys Id number. Just copy it.
   

→ How to launch an Application Full 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 Application in the ‘Scan type’ drop-down menu and then click on Launch Scan.
5. A pop up will show up to select the name of the Application to scan. If it doesn’t appear in the drop-down menu then it will be necessary to select Manual Entry.
6. Type the Application Name and the Sys Id number, click Yes and start scaning.

Impact: To verify in detail the status and progress at an Application level using the Admin portal.

Use cases:

3. Improvements made to the grid columns and filters of Update Set Scans.

Pre-requisites: Have enabled the option to launch an Update Set Scan in the Admin portal.

Description:

The Update Set Scans tab in the Admin History has been upgraded with improved grid columns for more detailed information. These include:

1. Update Set Name: Displays the name of the update set against which the scan was executed.
2. Quality Gates: Indicates whether the scan passed or not.
3. P. Time: Reflects the processing time of the scan.
4. Technical Debt: Provides information about the Technical Debt.
5. Source: Specifies the origin of the scan, distinguishing between scans triggered from the Portal or the App.

Moreover, you can now easily filter scan records by updating set names using the filter added to the Update Set Name column.

→ How to access the Update Set Scan History Tab?

1. Go to Quality Clouds Admin portal.
2. Click on the ‘History‘ tab.
3. Go to the Update Set Scan section.
4. Use the filters to locate your instance.
5. View the data provided.
6. Execute any action needed.

Impact: To verify in detail the status and progress of the scans using the Admin portal.

Use cases:

4. Display Tag Column and Tag Field to Table Configuration in Debt Manager view

Pre-requisites: Have access to the Debt Manager view.

Description:

In the Closed (fixed) issues of the Debt Manager tab, a new filter labeled ‘Tag‘ and its corresponding column have been added to the issue’s table. Additionally, the ‘Tag’ field is available in the Table Configuration functionality, allowing users to personalize the order of the columns in the issue’s table.

→ How to access the Debt Manager view?

1. Go to Quality Clouds Admin portal.
2. Go to the Debt Manager view.
3. Click on Closed (fixed) issues tab.
4. Filter the issues by tags.
5. Use the table configuration to display the Tag column and organize the order of the columns.

New Salesforce Best practices #

• Avoid Using Workflow Rules

New rule for Salesforce (SF-AVOID-ACTIVE-WORKFLOW-RULES)

Description:

This rule has been created due to the upcoming deprecation of workflow rules after 2025. Using this functionality beyond this date will accumulate Technical Debt . This best practice highlights that Workflow Rules running post-2025 won’t get support or bug fixes. To fix this, make a strategic plan to mitigate its impact before the deadline.

In this release we are covering Omni configuration elements. Additionally, we created two rules designed to evaluate performance within your Omni developments:

• Avoid Spaces In Omniscript Elements

New rule for Salesforce (SF-AVOID-SPACES-IN-OMNI-NAME)

Description:

This best practice advises against using spaces in element names, as they can slow down performance.

• Avoid Too Many Elements In Omniscripts

New rule for Salesforce (SF-AVOID-TOO-MANY-ELEMENTS-IN-OMNI)

Description:

This best practice suggests that having over 750 elements in a single OmniScript could slow down performance. To fix this, simply reduce the number of elements in the script.

Bug fixes #