Responsive dashboard properties
Summarize
Summary of Responsive Dashboard Properties
This document outlines the configuration options available for responsive dashboard properties in ServiceNow, allowing customers to fine-tune the behavior and appearance of their dashboards. Access these settings viaSystem Properties > Dashboard Properties.
Show less
Key Features
- Unified Analytics Workspace: Enables a combined view of responsive and Next Experience dashboards in the Analytics Center. Default is false.
- Secure Dashboard Sharing: Restricts the visibility of users, groups, and roles when sharing dashboards based on ACL configurations. Default is false, with a performance penalty for enabling.
- Role-Based Dashboard Sharing: Allows specification of roles that can share dashboards, defaulting to an empty state allowing all users to share.
- Widget Performance Threshold: Sets the maximum seconds for a widget to render; no default limit is set.
- Concurrent Widget Rendering: Limits the number of widgets that can render simultaneously, defaulting to 3.
- Widget Cache TTL: Defines the cache duration for responsive dashboard widgets in seconds, defaulting to 2.
- Search Result Limits: Controls the maximum number of users, groups, and roles returned during searches in the Share panel, defaulting to 100 per category.
Key Outcomes
By configuring these properties, ServiceNow customers can enhance their dashboard experience, optimize performance, and manage user access effectively. Proper adjustment can lead to improved interface responsiveness and user satisfaction while ensuring secure sharing practices are followed.
Use properties to fine-tune dashboard behavior and appearance.
Navigate to to configure the main responsive dashboard properties.
Responsive Dashboard properties
| Property | Description |
|---|---|
Enable the unified analytics workspace experience, which shows all responsive dashboards and Next Experience dashboards in the same overview in the Analytics Center. com.glide.par.unified_analytics.enabled |
When enabled, users see both Platform Analytics and core UI (responsive) dashboards in the Analytics Center. Users can still drill down to KPI details from responsive dashboard indicator visualizations. |
Apply security rules to the list of users, user groups, and roles that are visible when sharing dashboards. glide.cms.dashboards.sharing_with_secure_search |
When enabled, the list of users, user groups, and roles that are visible in the sharing panel is restricted. The restriction is based on the configuration of the sys_user, sys_user_group, and sys_user_role ACLs. For more information, see Access control list rules. There is a performance penalty associated with enabling this property. Performance degradation may be based on the number and complexity of business rules and ACLs on your instance. |
Specify a comma-separated list of roles that can share their own dashboards. glide.cms.share_dashboards.role |
Note: Properties that restrict dashboard sharing do not apply to users with the admin and dashboard_admin roles. Users with these two roles can always share any dashboard. |
Maximum number of seconds for a widget to render on a responsive dashboard. glide.canvas.grid.widget_performance_threshold |
For more information, see Optimize widget rendering time on responsive dashboards. |
Maximum number of widgets that can render simultaneously on a responsive dashboard. glide.canvas.grid.widget_render_concurrent_max |
For more information, see Optimize widget rendering time on responsive dashboards. |
Number of seconds that responsive dashboard widgets are cached in the browser. glide.canvas.grid.widget_cache_ttl |
|
| Number of users, groups, and roles returned when searching for a name in the Share panel of a Responsive Dashboard. The value of this property is per category, so the default value of 100 may yield 300 results - 100 users, 100 groups, and 100 roles. glide.cms.dashboards.sharing.search.maxRecords |
Setting the value too low can cause the expected results not to be found. The minimum value is 5. Setting the value too high can cause performance issues. |