Report reference

cBrain continuously develops and maintains a wide range of standard report types. Here you will find a description of each report type and their standard report configurations.

Many of the described standard report types are automatically included in Analytics, while others must be set up separately. Additionally, in cooperation with cBrain, it is possible to develop report types that match your organisation’s specific needs, such as extracting data regarding your case guides. Contact cBrain for more information.

Standard report types are categorised according to the type of data they extract:

  • Access provides insight into how users utilise their privileges and access to data.

  • Users covers report types focusing on users in F2. This specifically concerns user setups, including roles, privileges, and membership of security groups.

  • Data provides insight into the data elements in the organisation’s archive, such as records and cases.

  • MIS covers report types intended for management reporting with a focus on the case processing and its efficiency.

  • MIS Request covers management reporting specifically regarding the installation’s request types. Read more about the different request types under Request, Request (Group), and Request (External) (documentation available in Danish)

  • MIS Approvals covers management reporting specifically regarding approvers and approval processes. Read more about approval processes under Approvals.

How to read a report reference

The report reference primarily explains from which part of the database the report type extracts data. Additionally, it describes the overall purpose of reports of that type, which you can also use as inspiration for setting up your own reports.

The report reference also cover each report type’s standard configurations. For each report configuration, the intended purpose and the following parts of the configuration are described:

  • Columns, which are described with:

    • Column name as it appears in F2’s user interface.

    • Description of the data that the column extracts.

    • Example of extracted data.

  • Potential filters, which are described with:

    • The name of the column that constitutes the filter.

    • The value of the filter.

    • Description of the effect the filter has on the extraction.

  • Potential fields to fill in, which are described with:

    • The name of the column that constitutes the field.

    • Description of how to fill in the field.

Some columns are filled in with technical terms for elements in F2 and may not correspond to element names as they appear in F2’s user interface. For example, this applies to the privileges that can be assigned to roles.