Workspace Views - linking to specific dashboard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago - last edited 4 hours ago
I am struggling to efficiently use the Workspace views. In this example, I am using the CAM Workspace.
Am I able to do the following and if so, how?
1. Link directly to a specific dashboard.
The default dashboard appears anytime you link to /now/risk/cam/dashboard. But I want to give a user a link to another dashboard that appears when the page loads.
2. Open record from Workspace in Classic view
There are times when I want to open a record from the Workspace view in the Classic view. Its usually so I can locate the exact field label name for development.
How can I quickly do that without having to open the table in Classic view and search for the record?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
1. Direct linking to a specific dashboard
The workspace dashboard URL supports a query parameter to specify which dashboard to load. The format is:
/now/risk/cam/dashboard?id=<sys_id_of_dashboard>
To get the sys_id, navigate to the pa_dashboards table (or sys_aw_dashboard depending on whether it's a Performance Analytics dashboard or a Workspace-native dashboard), find the dashboard record (e.g., "CAM Overview"), and grab its sys_id. Then construct the URL like:
/now/risk/cam/dashboard?id=abc123def456...
If that parameter isn't honored in your version, an alternative approach is to use the Dashboard URL directly from the dashboard record itself. You can also try the sysparm_dashboard parameter variant. The exact parameter name can vary slightly across releases — on Zurich/Vancouver, check the workspace router configuration under sys_aw_master_config or inspect the URL behavior when you manually switch dashboards (open browser DevTools → Network tab → watch the URL or API calls as you select a different dashboard from the dropdown). That'll reveal the exact parameter your instance version expects.
2. Opening a workspace record in Classic view
There are a few ways to do this quickly:
The fastest method is to copy the sys_id from the workspace URL and construct a classic URL manually. When you open a record in a workspace, the URL typically contains the record's sys_id (e.g., /now/risk/cam/record/cmdb_ci/abc123...). You can then navigate to:
/<table_name>.do?sys_id=<sys_id>
To make this even faster, you can use a UI Action or browser bookmarklet. Create a simple JavaScript bookmark in your browser like:
javascript:void(function(){
var parts = location.pathname.split('/');
var sysId = parts[parts.length-1];
var table = parts[parts.length-2];
if(sysId && table){
window.open('/' + table + '.do?sys_id=' + sysId, '_blank');
}
})();
Click that bookmarklet while viewing any workspace record, and it'll open the classic form in a new tab. You may need to adjust the path parsing depending on how your workspace URLs are structured, but the concept is the same — extract the table name and sys_id from the workspace URL path segments.
Another option: from within the workspace record, right-click the hamburger/context menu (if available) and look for an "Open in new tab" or "Copy sys_id" option. Some workspace configurations expose this OOTB. If yours doesn't, you could add a declarative action or UI Action scoped to the workspace that opens /${table}.do?sys_id=${sys_id} in a new window.
The bookmarklet approach is probably the quickest win for your development workflow since it requires zero instance configuration.
