---
sourceDocument: Australia Build workflows
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/build-workflows

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Generate approvals using Workflow flows

# Generate approvals using Workflow flows {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Workflow Studio flows are a powerful and flexible method of generating approvals. Use workflow flows to create group approvals and user approvals.

A variety of variables are available to fine-tune the approval process, including the actions that occur when approval or rejection take place. When a Workflow Studio flow generates an approval record, the system populates the
Flow field on the approval record with a reference to the flow and the Ask for Approval action. Do not use this field when creating business logic. For more information, see [Ask for Approval action](https://servicenow-prod.fluidtopics.net/b_wb~rFm82ytUgYBbHM2nA "Request approval for a record. Configure a set of rules to automatically approve, reject, or cancel an approval request without having to write script. Add a due date to automatically approve, reject, or cancel when a decision has not been made by a designated time.").  
Note:  
Conflicts can arise when the approval process for a table is managed by both the Workflow Studio engine and the approval engine. In general, if there is a Workflow Studio flow that manages the approval process for a table, the [approval engine](https://servicenow-prod.fluidtopics.net/EW3Wyo5UwSeuVll1tjJ1Sw "The differences in the way that companies handle their approvals, as well as the differences between approvals for the various applications (such as Service Catalog Requests and Change Management), calls for supporting flexibility in setting up approvals within applications.") should be turned off for that table.
**Related reference**   

* [Classic approvals](https://servicenow-prod.fluidtopics.net/bnyoQtOJmQQnzCmEnmbxNQ "Classic approvals are a legacy process to require authorization on tasks before the work is done. In earlier releases, you could create approval records to define approval tasks and associate users or groups to approve or reject them.")