You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

Approvals can be defined for all tasks whose workflow may require such a step; they allow users and groups to be associated with a task, for the purpose of either approving or rejecting the task.

To define approvals, please navigate to the Approvals category.

Approval tickets


In SimpleOne, once a task requiring authorization is submitted, then it transitions to the authorization stage. For this, approval tickets should be sent to all persons responsible for the approval. In such a ticket, every recipient is proposed to approve or reject a request.

Approvals


In this list, you can find all the approvals that have worked in the system. Please be noted that "the approvals" are not equal to "the approval tickets", because one approval may contain a number of the approval tickets to approve.

To view this list, please navigate to Approvals → All.

FieldDescription
ApproverReference to the user responsible for approving the related record.
ItemReference to the item that was processed by the approval rule and approved or rejected.
State

Approval state. Available choice options:

  • Requested:
  • Approved;
  • Rejected;
  • Canceled.
SubjectApprove subject (copied from the Item subject).
DescriptionA text field for storing description regarding the approval.
CommentsA text field for storing comments regarding the approval.
Approval ruleReference to the approval rule that was run for this approve.
Approval setApproval tickets set number (if there were sent more than one sets of tickets for one record),

Approval Rules


Approval rules are a flexible instrument able to trigger on a predefined event. Once triggered, they send a set of approval tickets and process feedback (approves and rejects). Approval rules also can automatically create a set of approvers.

To define the approval rule, please complete the steps below:

  1. Navigate to Approvals → Approval Rules.
  2. Click New and fill in the form
  3. Click Save or Save and Exit to apply changes.

Approval rule start condition

Approval rules perform when the start condition specified with the Approve condition field is met. After defining the Target table, all fields of this table are available in the constructor.

Use non-dynamic and dynamic filter conditions (like is (dynamic) or is not (dynamic)) when composing conditional expressions with the Condition Builder to make your business rules more versatile. You can create complex AND and OR filters, more than one in one approve condition.

Approval Rules form fields

FieldDescription
TargetSpecify a table which will be processed by this approval rule (for example, Incident).
Approve conditionCreate a condition to meet before sending approve tickets. Use the Condition Builder to build a filter that fits your needs. 
Approver

A choice field specifying a category of users responsible for the request approving. Available choice options:

  • Users;
  • Group;
  • Script.
UsersIf the Users option was selected in the Approver field, then choose one or more users responsible for the approval process in this dictionary field.
Script

If the Script option was selected in the Approver field, then enter the script extending your approval condition. You can use SimpleOne server-side API there.

GroupIf the Group option was selected in the Approver field, then choose the group responsible for the approval process in this dictionary field. All the group members will have approval tickets to process.
Approval abortion rule

In this field, you can specify the condition of the approval request reject. Available choice options:

  • More than half tickets rejected
  • Set rejected tickets limit
  • All tickets rejected
  • One of the tickets rejected
CountSpecify a limit of the rejected tickets for the approval request reject (if the Set rejected tickets limit option was chosen in the Approval abortion rule field).

Approval status


Generally, the approval status of any issue may be either Rejected or Approved; other states may depend on issue types and their state models.

For example, Change Request will have the Authorization state on the approval stage. If the request is approved, then it will pass to the Scheduled state; otherwise, it will return to Registered.

  • No labels