Prerequisites for the Gatekeeper dashboards
Overview
Three things have to line up before you can open a dashboard and see results: the dashboards component must be installed, the application must have been analyzed and its results published, and your user profile must grant access. This page covers each in turn, then shows you how to open a dashboard.
Step 1 - Check the component is installed
The dashboards are provided by the optional dashboards component, which is only present in installation scenarios S1, S4 and S5. If your deployment was installed as S2 or S3, it has the Viewer but no dashboards, and the dashboard actions described below will not appear.
See CAST Imaging components for what the component does, and Choose your deployment for the scenario matrix.
Step 2 - Analyze the application and publish the results
A dashboard reads consolidated results, not the live analysis. That data arrives in two stages:
- A snapshot is generated. A snapshot is a capture of the application’s source code at a point in time, measured against a set of rules. Snapshots are what the Engineering and Management dashboards are built from.
- The snapshot is published. During analysis, the Publish to Management Dashboard job uploads the snapshot into the Measurement schema (
general_measure), where results for all applications are consolidated. You can also publish existing snapshots afterwards using Publish All Snapshots on the Snapshots page.
Rules configured with a 0 weight are never consolidated into the Measurement schema, so they are triggered during analysis but do not appear in the Management Dashboard. See Assessment model.
Step 3 - Apply a license key
The dashboards are available with the appropriate CAST licenses only. CAST Imaging uses one of two license strategies, chosen when the installation is first initialized:
| Strategy | What it means |
|---|---|
Named Application |
Each application needs its own dedicated license key, matching the application name |
Contributing Developers |
A single global key covers all applications |
If an appropriate key is not in place, the dashboard actions are not available. See Manage license keys.
Step 4 - Check your permissions
Access to a dashboard is decided by your profile and the roles it contains. The dashboard actions are available when any of the following is true:
- You have the
Administratorrole, which grants access for all applications. - You have the
Application Ownerrole on the application. - The application is assigned to a profile that includes any dashboard-related role.
- The application is assigned to two or more profiles and at least one of them includes a dashboard-related role.
The default profiles that grant result consumption in the dashboards are Admin, Application Creator, Application Architect, Application User and Application Guest. See Default profiles and roles for exactly what each one contains.
Roles that unlock actions inside a dashboard
Opening a dashboard and acting within it are governed separately. These three roles control the Engineering Dashboard’s editable features:
| Role | What it grants |
|---|---|
Quality Manager |
Add and remove objects in the Action Plan, and use the Action Plan Recommendation features |
Exclusion Manager |
Add and remove objects in the Exclusion List |
Quality Automation Manager |
Add and remove objects in the Education list |
A user with Viewer Read Only can consult results but cannot edit any of these. See User permissions.
Step 5 - Open a dashboard
Open the application landing page and use the action for the dashboard you want: View Management Dashboard, View Engineering Dashboard or View Security Dashboard.
Why is the dashboard action missing or greyed out?
| What you see | Why |
|---|---|
| The action is not visible at all | The application exists only via imported results, or your profile grants no dashboard-related role for it |
| The action is visible but disabled | The application has not been analyzed yet |
| No dashboard actions anywhere | The dashboards component is not installed in this deployment - see Step 1 |
| The action is unavailable despite an analysis | An appropriate license key is not in place - see Step 3 |
Read-only deployments
Where analysis runs on one installation and users consult results on another, the dashboards can be deployed in a read-only S4 (Dashboards only) configuration. In that case an administrator imports the result schemas and declares the applications before end users can reach them. See Standalone dashboard workflow.