View reference
Learn about the available Views you can use to build reports.
Available Views
Views define the categories and fields from Diligent One that you can use to build a report. Fields are specific columns of data and categories are logical groupings of fields within a View.
To view project or framework information in a report using a Fieldwork or Framework View, the project or framework must contain at least one objective. For more information about objectives in Projects, see Defining objectives.
View name | Description | Use cases and remarks | Categories |
---|---|---|---|
Action Items |
This View contains issue action items for all active projects. |
|
|
Action Items by Entity |
This View contains issue action items for all active projects by entity. Records are replicated for each tagged entity at the issue level so that you can filter results by entity. |
|
|
Archived Issues |
This View contains issues for all archived projects. |
|
|
Archived Issues by Entity |
This View contains issues for all archived projects by entity. Records are replicated for each tagged entity at the issue level so that you can filter results by entity. |
|
|
Fieldwork |
This View contains data for all active projects including Objectives, Risks, Controls, Walkthroughs, Test Plans, and Testing. |
For management reporting, you can generate a report on failed control tests and which risks they are associated with. Tip
This is the most versatile View. You can use this View to report on a subset of fields, allowing you to query only the specific data you want to report on. |
|
Fieldwork by Entity |
This View contains data for all active projects including Objectives, Risks, Controls, Walkthroughs, Test Plans, and Testing by entity. Records are replicated for each tagged entity at the control level, allowing you to filter results by entity. |
For management reporting, you can generate a report on failed control tests and which risks they are associated with. |
|
Frameworks | This View contains framework data including Objectives, Risks, and Controls. |
For operational reporting purposes, you can generate a report that consolidates and aggregates the results from multiple projects associated with a framework. For example, if you have a series of SOX projects based in different regions, you can aggregate the results from each region. |
|
Issues |
This View contains issues for all active projects. |
|
|
Issues by Entity |
This View contains issues for all active projects by entity. Records are replicated for each tagged entity at the issue level so that you can filter results by entity. |
|
|
Projects and Users |
This View contains project details including assigned users and associated roles. |
Generate a report for user access monitoring across all projects, by user and role assigned. |
|
Projects and Users by Entity |
This View contains project details including assigned users and associated roles by entity. Records are replicated for each tagged entity at planning level of a project so that you can filter results by entity. |
Generate a report for user access monitoring across all projects, by user and role assigned. |
|
Request Items |
This View contains all request items in active projects. |
|
|
Results | This View contains all record metadata related to tables in Results. |
|
|
Strategy | This View contains strategic risks, treatment, and assurance from Strategy. |
|
|
Timesheets | This View contains timesheet details for all active projects. |
Aggregate time captured in your projects at a summary of detailed level. |
|
To-Dos |
This View contains to-dos for all active projects and frameworks. |
Generate reports that show all to-do items entered across all active projects and frameworks in the organization. To report on to-dos only associated with active projects or frameworks, you can filter by Project Status. |
|
"by Entity" Views
Views that are suffixed with "by Entity" allow for reporting of that View according to your entity structure in Projects. You can tag items (projects / frameworks, objectives, risks, controls, or issues) to entities in Projects to generate entity-specific reports in the Reports app.
For more information on entity tagging in Projects, see Setting up entity tagging.
When should I use a "by Entity" View?
The "by Entity" Views are intended for report writers that want to specifically include the Parent Entity, Entity Category, or Entity field in their reports. Entity fields in these Views are used to split data.
Entities are ordered based on their creation date in Projects.
If you do not need to split data by entity, Diligent recommends that you use any of the Views that are not suffixed with "by Entity".
The difference between "by Entity" Views and other Views
The difference lies in the way that the data is displayed in a report. Either the data is displayed independently in multiple rows or consolidated into a single row.
For example, let's say you have a single control that is tagged to two entities. The table below describes how the control data is displayed in a report based on the two View types:
View Type | How data is displayed in a report |
---|---|
Views suffixed with "by Entity" |
The data is displayed independently in two rows.
|
Views not suffixed with "by Entity" |
The data is consolidated into a single row. The two tagged entities associated with the control display in a comma separated list. |