F2 Approvals configuration options

F2 Approvals can be configured to fit the needs of the individual organisation. The following functions can be configured in cooperation with cBrain:

  • Decide if users have the option of creating a “New empty approval flow”. The organisation can decide whether users must use an existing approval template when creating a new approval or if they can create personal approval templates.

  • The organisation can decide that only users with the “Template administrator” privilege can save approval templates.

  • Decide whether it is possible to mark an approval as urgent. The “Urgent” checkbox is then visible when creating a new approval.

  • Decide whether parallel approvers on an approval step are allowed, i.e. whether multiple approvers can be added to the same step of an approval flow.

  • Define one or more templates for the approval document. Users can choose a new approval document by clicking “Replace approval document” when creating or editing an approval process. Additionally, approval documents can be linked to specific approval templates.

  • Decide whether it is possible to add an approval on an already existing record. The module can be configured so new approvals cannot be created on records that already exist. Approvals can then only be created via the “Add approval” option from either the main window or the case window.

  • Select which options are available when creating approvals with or without a record document. The following can be configured:

    • Whether a standard approval is created with or without a record document.

    • Whether a user is able to create the approval without a record document.

    • Whether a user is able to create a record document after the approval has been created.

  • Decide if it is possible to create and edit approvals using F2 Touch using parts of the approval functionality from F2 Desktop. By default, it is not possible to create or edit approvals in F2 Touch.

  • Decide whether a record can be deleted if it contains an active approval.

  • Decide whether a new version of the record is created following each approval action.

  • Decide whether a warning appears to a user who edits a record with an ongoing approval process. The warning will appear if the user is not an approver on the current step.

  • Decide whether users are warned when they attempt to send records with an ongoing approval process. This configuration only applies to F2 Desktop and the warning is only displayed here.

  • Select the default notification settings for the approval’s responsible user. The configuration has three options:

    • The responsible user receives no notifications when approvers return or approve, i.e. at step changes. This is the default setting.

    • The responsible user is notified of step changes if the approver on the step added a comment.

    • The responsible user is notified of all step changes.