Integrated Approval Workflow

OneCloud’s approvals feature, also known as Integration Workflow, is a form of a Chain Event that is designed to integrate an approval within a OneCloud Chain execution. When adding an approval event to your Chain, Chain execution pauses to collect end-user accept or reject responses along with additional commentary. These responses are then tracked to be used in combination with other branching logic or for audit purposes.

A complimentary OneCloud function is to provide supporting file attachments to an approval workflow. Please visit Runtime File Upload Chain Event, to see how file attachments can be included in a workflow.

Some example use cases include:

  • Approve a data flow between systems before it actually occurs.

  • Easily coordinate resources and collect auditable responses.

  • Automate the workflow between requesters and approvers.

To see Human Integration Workflow in action, visit running chains with approvals.

Approval Configuration

To set up Integration Workflow in OneCloud, at any point in a Chain, add an approval event.

At this point, various parameters need to be provided to configure the approval. The following table describes each parameter. All of the following fields can be dynamically set by variables or by static values.

Field

Input Type

Description

Title

Static text input or variables

Name of the requested approval.

Requesters

Email address or a variable that contains a comma-delimited list of emails or requesters.

If using a variable that contains more than one email address, please use a comma delimiter.
Must be OneCloud users to request.

Approvers

Email address or a variable that contains a comma-delimited list of emails or Approvers.

If using a variable that contains more than one email address, please use a comma delimiter.
Must be OneCloud users to approve.

Details

Static text input or variables

Details/Description of the approval.

Due in

Numeric Input

If the approval type is set to sequential, then this value represents the number of days each approver has to approve before it gets escalated to the next approver.
If the approval type is set to flat or single, then this value represents the number of days before the approval will time out.

Approval Type

Sequential, Flat or Single

Allows end-user approvals to be handled sequentially, in parallel, or a single approver from a list. See Approval Hierarchy below.

Attachment (Optional)

File Command Output or File Resource

Typically used in combination with a prior chain commands that produce file outputs such as an HTTP Get Request.

📓 Runtime User for Approvals

If needed, the runtime user can also be inserted as a variable for either the requestor or approver. Simply choose the "Runtime User" in the respective dropdown.

Approval Hierarchy

If the Approval Type is set to Sequential, then the order of the approvers drives the approval order. The order can be controlled by simply moving the email addresses to the desired order.

📓 Pro Tip: Dynamically Configure Approvals

Use variables to dynamically update each approval field from an external source such as a relational database that has an approval hierarchy and other metadata to drive an approval.

Approval Outputs

Approvals generate valuable data that can be loaded into target systems such as a relational database. The following approval outputs can be used directly or transformed in combination with any other OneCloud commands where this type of operation would be relevant.

Field

Input Type

Description

Approval Emails

List

Optionally use variable transformation to pick elements from the list.

Requestor Emails

List

Optionally use variable transformation to pick elements from the list.

Approval Details

String


Approval Responses

JSON

A JSON structure that holds the responses of individual approvers and any comments.
Optionally use variable transformation to extract certain values from the JSON response.

Approval Outputs Example

In the example below, the approval responses are used to populate a SQL update query to load the responses to a relational database. This is just one of many ways to use Human Integration Workflow to enhance business process automation.

Did this answer your question?