Access log
| The content of this website is last updated to F2 version 11. cBrain are working hard on supplying you with the newest documentation of F2. |
The "Access log" report type extracts data logging user actions in relation to cases, records, documents, and other F2 elements such as chats and annotations. F2 logs all searches and views as well as changes to documents' content or cases' keywords.
The report type has three default configurations. The configurations are based on different types of searches for and views of records and their attached documents, if any.
The "Views" default configuration
Use the "Views" default configuration to gain insights into users' views of records, documents, annotations, and more.
The configuration contains filters but no fields to fill in.
| Column name | Description | Examples |
|---|---|---|
Date and time |
The full timestamp with year, month, day, hour, minute, and second. |
2023-11-14T12:40:29.597 2023-04-12T15:30:20.773 |
Action |
Name of the action that was performed. |
Record seen Document seen |
Name |
Name of the user who has performed an action. If the action was performed on behalf of another user, the name of the "on behalf of" user is specified. |
Holly Rogers Isaac Johnson |
Record ID |
The record’s unique ID number in the authority’s archive displayed at the top of the record window. |
82 346 |
Case No |
The unique ID number in the authority’s archive for a case with which another element in F2 is associated, or for the case itself as seen at the top of the case window. |
2024 - 48 2023 - 5 |
Case title |
The full case title displayed at the top of the case window and in the "Title" metadata field. |
Board meeting Section 20 inquiries |
Record number |
The record’s unique ID number on the case specified in the "Record No" metadata field, which is automatically assigned during registration. |
3 27 |
Record title |
The full record title displayed at the top of the record window and in the "Title" metadata field. |
Reply to Section 20 no. 351 regarding budget expansion Citizen Request |
Document title |
The document’s title as seen in its properties. |
Record document Attachment |
Filters
When drawing a report with this default configuration, the extraction is filtered as described in the table below.
| Filter | Value | Effect |
|---|---|---|
Action is access-related |
True |
Ensures that the extraction only contains data about actions where users have accessed a record, case, annotation, or document. |
The "Searches" default configuration
Use the "Searches" default configuration to get an overview of all searches performed by users.
The configuration contains filters but no fields to fill in.
| Column name | Description | Examples |
|---|---|---|
Date and time |
The full timestamp with year, month, day, hour, minute, and second. |
2023-11-14T12:40:29.597 2023-04-12T15:30:20.773 |
Action |
Name of the action that was performed. |
Archive search |
Name |
Name of the user who has performed an action. If the action was performed on behalf of another user, the name of the "on behalf of" user is specified. |
Holly Rogers Isaac Johnson |
Search criteria |
Description of criteria for a search action. |
Standard search: Inbox for me Active requests: EXECUTED: ("No"); CREATOR: ("Me"); |
Filters
When drawing a report with this default configuration, the extraction is filtered as described in the table below.
| Filter | Value | Effect |
|---|---|---|
Action is search |
True |
Ensure that the extraction only contains data about actions where the user has performed a search in the authority’s archive, including opening predefined lists. |
The "History" default configuration
Use the "History" default configuration to create a list of actions performed on records and cases. The list is similar to the "Record history" and "Case history" dialogues that you can access from the record and case windows, respectively. The configuration differs from the two history dialogues by including permanent deletions of cases, records, and documents.
The configuration contains filters but no fields to fill in.
| Column name | Description | Examples |
|---|---|---|
Date and time |
The full timestamp with year, month, day, hour, minute, and second. |
2023-11-14T12:40:29.597 2023-04-12T15:30:20.773 |
Action |
Name of the action that was performed. |
Case created Add participant to record |
Name |
Name of the user who has performed an action. If the action was performed on behalf of another user, the name of the "on behalf of" user is specified. |
Holly Rogers Isaac Johnson |
Record ID |
The record’s unique ID number in the authority’s archive displayed at the top of the record window. |
82 346 |
Case No |
The unique ID number in the authority’s archive for a case with which another element in F2 is associated, or for the case itself as seen at the top of the case window. |
2024 - 48 2023 - 5 |
Case title |
The full case title displayed at the top of the case window and in the "Title" metadata field. |
Board meeting Section 20 question about data protection |
Record number |
The record’s unique ID number on the case specified in the "Record No" metadata field, which is automatically assigned during registration. |
3 27 |
Record title |
The full record title displayed at the top of the record window and in the "Title" metadata field. |
Reply to Section 20 no. 351 regarding budget expansion Citizen Request |
Document title |
The document’s title as seen in its properties. |
Record Document Attachment |
Participant name |
The name specified in the "Name" participant property. In this case, it applies to the participant that was involved through the specified action. |
Holly Rogers citizen@email.com |
Involvement |
The participant’s type of involvement in a given record in connection with an action. This also covers the record’s case, approval, and attachments, if any. |
Responsible unit Recipient |
Filters
When drawing a report with this default configuration, the extraction is filtered as described in the table below.
| Filter | Value | Effect |
|---|---|---|
Action is search |
False |
Excludes archive searches since that type of action does not directly affect the specified records and therefore will not be part of their history. |
Action is access-related |
False |
Excludes actions where users have opened the record, case, annotation, or document, since that type of action does not directly affect the specified records and therefore will not be part of their history. |
Other available columns
The following table covers columns that are accessible when configuring reports, but are not included in the default configurations.
| Column name | Description | Examples |
|---|---|---|
Count |
Accumulates identical rows in the data extract and returns the total. |
249 |
Attribute name |
The metadata or other data-related attribute that a given action has affected. |
WriteAccessToNode ClosedDate |
Details |
Any system-generated text that describes or elaborates on an action. In this instance, details are given about the request the action is performed on. |
Outgoing request #7 (Doc Authority) |
User ID |
The unique user ID of the user who has performed an action. If the action was performed on behalf of another user, the unique user ID of the "on behalf of" user is specified. |
107 124 |
Participant SSN/CVR No |
The SSN or CVR number specified in the participant property "SSN/CVR No" or "SSN". |
010203-4679 230198-7654 |
Action related to access |
Indicates whether a given action pertains to accessing an item and its data. |
true 0 |
Action related to search |
Indicates whether a given action is a search. |
true 0 |
Operation type |
The unique action ID |
2 22 |