Versions Compared

Old Version 12

changes.mady.by.user Anna Kryzhanovskaya

Saved on

compared with

New Version Current

changes.mady.by.user Dina Baksheeva

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

To make an approval process more flexible, you can separate the approvers set making their decisions mandatory and non-mandatory.

A mandatory approver can either Approve or Reject the approval task; the non-mandatory approver can either ignore or (optional) Reject a task optionally.

Flexible approvals are configured via User-approval workflow activity.

Configuring participants

In general, to configure participants, please specify the approval conditions in the Approval block in your workflow.

For To specify mandatory participants, please fill in the fields below on complete the following steps:

  1. Scroll down to the Mandatory Participants tab of the

Approval

  1. User-approval block properties

:

  1. .

  1. Employees / Groups / Roles (you can fill in one of these fields)
  2. When approved - define the approval logic
    1. Approval Conditions - specify the approval conditions
    2. Rejection Conditions - specify the rejection conditions.
  1. Fill in either the Employees, Groups or Roles fields.
  2. Define the approval logic in the Approved When field.
  3. Click Save.

The table below describes the available options for the Approved When field:

Choice optionDescription
Anyone to approveOne of the specified users can approve; the first received approval causes the activity to complete with the result of Approved.
Everyone to approve

All the users must approve. If one of the participants rejects the ticket, the approval state changes to Cancelled and the workflow activity completes with the result of Rejected. 

First response from anyoneThe first received approval causes the activity to complete with the result of Approved.
Most answersThe activity will be completed with the Approved result if the quantity of approvals is more than the rejection quantity.
Conditions based on scriptEach time a user approves or rejects, the Script is called to determine if the activity should be completed.

Image AddedImage Removed


If your process requires non-mandatory participants involvement, then, please complete the steps below:

  1. Select the Non-Mandatory Participants checkbox when configuring your Approval User-approval block properties. The Non-mandatory participants tab appears.
  2. Fill in the fields below:
    1. Employees / Groups / Roles (you can fill in one of these fields).
    .
    • You can fill in either the Employees, Groups or Roles fields.
  3. Select To make them able to reject approvals, select the Consider non-mandatory participants checkbox to make participants able to affect the decision and reject approvals.
  4. Click Save.

Participant properties

To make an approver mandatory The participant properties differ slightly for mandatory and non-mandatory participant in a particular process or task (for example, Change Request authorization). 

ParticipantsParticipant properties
Mandatory
participant properties

Their reaction is mandatory to authorize a request. When a mandatory approver receives an approval request,

he

they can:

  1. Approve it.
  2. Reject it
(
  1. providing the rejection reason
)
  1. .
 
Non-mandatory
participant properties

Their reaction is not mandatory for authorization. When a non-mandatory approver receives an approval request

(

and if

he was

they were involved in the process

)

,

he can:

they can reject it providing the rejection reason.


  1. Ignore it.
  2. Reject it (if this ability has been provided).
Tip

You can configure your approval rules so that the first reject from the a non-mandatory participant will cancel the approval process. For this, you need to use the specific options listed below in your Approval block:

  • The Non-mandatory participants checkbox is selected.
  • Participants taking part in the approval process are chosen (whether specified employees or user groups or user roles).

    • User-approval block. The table below is an example of how to populate the fields: 

    FieldValue
    Non-mandatory participantstrue
    EmployeesJohn Doe, Jane Doe
    GroupsHR
    Roleshr_manager
    Consider non-mandatory participantstrue

    This combination of checkboxes allows at least one of the non-mandatory participants to reject approval tickets regardless of the approval condition defined in the Approved When field. 

    The Consider non-mandatory participants checkbox s selected.

    Example of business usage

    Approvals flexibility serves well ad hoc, for example, in a business-cases requiring a case-by-case approach, such as Change Enablement Practice.

    When authorizing a change request, mandatory and non-mandatory approvers may can take part in the approval process.

    Both of these types mandatory and non-mandatory approvers can be classified according to the RACI matrix.

    RACI Matrix

    ProcedureProcess Manager (for example, Change Manager)Mandatory approverNon-Mandatory approver
    ApprovalARI, R


    Info

    The process manager is accountable for the whole process, so he is marked they are marked with A in the table.

    Mandatory approvers are responsible for the request implementation, so they are marked with R in the table.

    Non-mandatory approvers generally should be informed but may be responsible for one or more implementation stages, so they are marked with I and R.


    Table of Contents
    absoluteUrltrue
    classfixedPosition