Notifications

608 views

Description

Drilling down on a data visualisation component added to a custom workspace landing page does not work.

Steps to Reproduce

1. Open an Orlando instance
2. Change the application to Agent Workspace
3. Navigate to Workspace Experience -> Administration -> All Workspace
4. Select the New UI action
5. Create a custom workspace
6. Navigate to Workspace Experience -> Administration -> Landing pages and select the New UI action
7. Create a new landing page for the Custom workspace and enable the UI builder
8. In the UI builder, drag and drop a Data Visualisation component
9. Add the open incident widget
10. Save the record
11. Now open the custom workspace
12. Observe that you cannot drill down into the report
13. Go to the landing page and in the field “Applicable Page Registry” change the value to Agent workspace
14. Now open the OOB workspace
15. Observe that we are able to drill down into the report

Expected behaviour: Users should be able to drill down into the reports in custom workspaces

Actual behaviour: Report drill-down does not work in custom workspaces

Workaround

This problem is currently under review. You can contact ServiceNow Technical Support or subscribe to this Known Error article by clicking the Subscribe button at the top right of this form to be notified when more information will become available..


Workaround 

Note: Please de-activate the UI policy “Hide old Render Type” before starting the process. This will allow one of the fields to appear on the form


1. Navigate to sys_aw_renderer.list

2. Click the New UI action

3. Workspace Settings (workspace_config column) = The custom workspace

4. Renderer Type Extension (type_ext column) = "layout" (the reference record in the sys_aw_renderer_type table where sys_id = "bfacd1a10f517300bb57f4a1ff767e92" and renderer_type = "layout")

5. Application (application column) = a reference to the application scope in which the workspace is created in. To modify this value, make sure to switch into that scope.

6. Module flag (module_flag column) = true

7. Workspace Module (workspace_module column) = "home" (the reference to the record in Workspace Module / sys_aw_module record where id = "home", Application = the application scope from item #3, and Workspace = the workspace that the user is trying to add the renderer to / same value as item #1).

8. Custom Renderer (custom_renderer column) = "now-record-list-connected" (the reference to the UX Component Definition / sys_ux_lib_component table where sys_id = "d57daf1053203300099addeeff7b12e8")

9. renderer_type column = "layout"


Related Problem: PRB1401936

Seen In

Orlando Patch 1
SR Shodan Kingston r1 - v5.0.10
SR - Finance - Common - NY v1.1
SR - Finance - ERP Integration - NY v1.1
SR - Finance - Financial Close - NY v1.1
SR - Finance - Risk Management - NY v1.1
SR - IRM - Advanced Risk - New York 2019 Q3
SR - IRM - Audit Management - New York 2019 Q3
SR - IRM - Audit Management PA Content - Madrid 2019 Q1
SR - IRM - GRC Profiles - Madrid 2019 Q2
SR - IRM - GRC Workbench - New York 2019 Q3
SR - IRM - GRC: Mobile - New York 2019 Q3
SR - IRM - NIST CSF - New York 2019 Q3
SR - IRM - NIST RMF - New York 2019 Q3
SR - IRM - PA Premium Integration - New York 2019 Q3
SR - IRM - Policy and Compliance - Madrid 2019 Q2
SR - IRM - Policy and Compliance PA Content - Madrid 2019 Q1
SR - IRM - Risk Management - New York 2019 Q3
SR - IRM - Risk Management PA Content - Madrid 2019 Q1
SR - IRM - SIG Assessment Legacy - Madrid 2019 Q1
SR - IRM - SIG Questionnaire - New York 2019 Q3
SR - IRM - Vendor Risk Management - Madrid 2019 Q1
SR - ITOM - Discovery and Service Mapping - 201908
SR - ITOM - Fundamentals Istanbul Jakarta Kingston r1 - v5.99.6
SR - PAR - Performance Analytics Content Pack for Service Portal - v1.0
SR - Security - Integration Framework - Madrid 2019 Q2
SR - Security - Support Common - Madrid 2019 Q2
SR - Security - Support Orchestration - Madrid 2019 Q2
SR - SIR - ArcSight Logger Integration - Madrid 2019 Q1
SR - SIR - CarbonBlack Integration - New York 2019 Q3
SR - SIR - Check Point Integration - New York 2019 Q3
SR - SIR - CrowdStrike Host Integration - Madrid 2019 Q1
SR - SIR - CrowdStrike Intel Integration - Madrid 2019 Q1
SR - SIR - ElasticSearch Integration - Madrid 2019 Q1
SR - SIR - Exchange OnPrem Integration - New York 2019 Q3
SR - SIR - LogRhythm Integration - New York 2019 Q3
SR - SIR - McAfee ESM Integration - Madrid 2019 Q1
SR - SIR - MetaDefender Integration - New York 2019 Q3
SR - SIR - Palo Alto AutoFocus Integration - New York 2019 Q3
SR - SIR - Palo Alto Firewall Integration - New York 2019 Q3
SR - SIR - Palo Alto WildFire Integration - New York 2019 Q3
SR - SIR - Qradar SIEM Integration - Madrid 2019 Q1
SR - SIR - RecordedFuture Integration - New York 2019 Q3 2
SR - SIR - Security Incident Response - Madrid 2019 Q2
SR - SIR - Security Incident Response Flow Designer Content - Madrid 2019 Q2
SR - SIR - Security Incident Response Mobile - New York 2019 Q3 2
SR - SIR - Security Incident Response PA Content - New York 2019 Q3
SR - SIR - Security Incident Response UI Patch - London 2019 Q2 v.6.2.3
SR - SIR - Splunk Sighting Search Integration - Madrid 2019 Q1
SR - SIR - Store SecOps Setup Assistant - Madrid 2019 Q2
SR - SIR - Store Threat Core - Madrid 2019 Q2
SR - SIR - Store Trusted Security Circles Client - New York 2019 Q3
SR - SIR - Store Trusted Security Circles Client Advanced- Madrid 2019 Q1
SR - SIR - Tanium Integration - New York 2019 Q3
SR - SIR - Threat intelligence - New York 2019 Q3
SR - SIR - VirusTotal Integration - New York 2019 Q3
SR - SIR - WHOIS Integration - New York 2019 Q3
SR - VR - Configuration Compliance - New York 2019 Q3
SR - VR - Qualys - New York 2019 Q3
SR - VR - Shodan Exploit - New York 2019 Q3
SR - VR - Solution Management Madrid Q2
SR - VR - Vulnerability Response - New York 2019 Q3
SR - VR - Vulnerability Response Mobile - New York 2019 Q3
SR - VR - Vulnerability Response PA Content - Madrid 2019 Q2

Intended Fix Version

Quebec

Fixed In

Orlando Patch 7
Paris Patch 1

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-09-16 10:44:43
Published:2020-06-10