Skip to content
FlinkISO

FlinkISO supports both reusable automatic approval processes and approvals selected while working with a record. The request, comments, responses and status stay connected to the document or generated form.

Define an automatic approval process

  1. Open Approval Processes from the main menu and create a process.
  2. Add the approval steps in the required sequence.
  3. Assign one or more users to each step.
  4. Choose how the step should behave when more than one approver is assigned.
  5. Save the process and connect it to the relevant document or form workflow.
Create a reusable automatic approval process.
Create a reusable automatic approval process.
Define the sequence and responsible approvers for each step.
Define the sequence and responsible approvers for each step.

Send a record for approval

From the record’s approval panel, select the approver or process, add a useful comment and choose the approval mode and type available to the workflow.

SettingEffect
View OnlyThe recipient reviews the record without being given edit access through the approval request.
EditThe recipient may edit as part of the approval activity when the record and role allow it.
AllEvery selected approver must complete the required response.
AnyOne of the selected approvers can complete the approval requirement.
Choose approval mode and whether all or any selected approver must respond.
Choose approval mode and whether all or any selected approver must respond.

Approve, reject or reply

Approvers receive a dashboard and email notification when configured. Open the request, review the record and its history, then approve, reject or reply with the available response action. A reply keeps the conversation in the approval history and allows the sender to answer without losing context.

Pending approvals are available from the dashboard.
Pending approvals are available from the dashboard.
The approver reviews the record and records a controlled response.
The approver reviews the record and records a controlled response.

Complete and publish

When the required approvals are complete, an authorised user can publish the record. If approval is mandatory, the publish action is withheld until the workflow is satisfied. Rejected requests remain visible in the history and can be corrected and resubmitted.

The sender can follow every request, response and reply in one history.
The sender can follow every request, response and reply in one history.
Choose All or Any deliberately. Use All when every named approver represents a required control; use Any when the selected users are equivalent alternatives.
  • On Cloud

    Start your 15 days On-Cloud QMS trial. No payment required. One free training session included. Live chat & email support.

    Register
  • On Premise

    Download Free Quality Management Software On-Premise Edition. Installation, Training, Support Services on-demand.

    Free Download