F2 Request

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.

F2 version 10 introduced a new and improved request window design through a configuration. This manual describes F2 Request using this new design. If your organisation uses the old design, refer to the version 9 manual (available in Danish).

A request is a method to formally ask a user or a unit to carry out a task. Requests help an organisation distribute work while meeting deadlines.

Requests are always associated with a record, which is then sent to the request recipient. The recipient can reply directly via the request window or with a reply record, which is automatically related to the original record. The recipient also have the option of adding an approval to the reply record.

There are three types of requests available. F2 Request lets you send requests between users and units within an F2 authority. This is called an internal request.

A range of special columns and icons provides you with a graphical overview of the organisation’s requests and their current status.

The request flow

Requests are created in the record window. In the request window, you select the request recipient and describe the work you are requesting.

Once you send the request, it is delivered to the recipient’s inbox.

From here the recipient can choose to accept, reject, or reply to the request.

The request is returned to your inbox upon execution. You can then finalise the request.

Get an overview of requests

You can get an overview of sent and received requests in F2 from the standard request searches. The request view and request columns of the result list can help with this overview.

The request icons provide information regarding the deadline and status of the request.

You can also pull detailed statical data on requests and their use with the F2 Analytics add-on module.