{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":3700,"path":"build-workflows/approvals/c_GeneApprovalsUsingWorkflows.md","title":"Generate approvals using Workflow flows","bundle":null,"doc_type":null,"release":"australia","body":"\n# Generate approvals using Workflow flows\n\nWorkflow Studio flows are a powerful and flexible method of generating approvals. Use workflow flows to create group approvals and user approvals.\n\nA 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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/build-workflows/workflow-studio/ask-approval-flow-designer.md).\n\n**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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/build-workflows/approvals/c_ApprovalEngines.md) should be turned off for that table.\n\n**Related topics**  \n\n\n[Classic approvals](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/build-workflows/approvals/r_Approvals.md)\n\n"}}