{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":2181,"path":"application-development/form-builder-glide-family-release/flows-tb.md","title":"Flows in Table Builder","bundle":null,"doc_type":null,"release":"australia","body":"\n# Flows in Table Builder\n\nYou can use the Workflow Studio functionality that is integrated within Table Builder to manage your table's record-based flows. You can manage these flows by using the **Flows** tab.\n\nWorkflow Studio is a ServiceNow AI Platform® feature that enables process owners to automate work. Build multi-step flows from reusable components without having to code.\n\nThe **Flows** tab within Table Builder is where you can view and work with record-based flows for a selected data table. These are actions triggered when a table record is created, updated, or both.\n\nThe following diagram shows flow cards in Table Builder.\n\n\\[Omitted image \"flows-tb.png\"\\] Alt text: Flows tab.\n\n**Parent Topic:**[Using Table Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/using-fb.md)\n\n## Find a record-based flow\n\nUse the **Flows** tab in Table Builder to search and filter a list of flows that are triggered when selected table records are updated, created, or both.\n\n### Before you begin\n\n-   Launch Table Builder. For more information, see [Accessing Table Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/accessing-form-builder.md).\n-   \\(Optional\\) Choose a domain to work within \\(if not global\\). For more information, see [Domain separation and Table Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/form-builder-domain-separation.md).\n-   \\(Optional\\) Choose an application scope to work within \\(if not global\\). For more information, see [Using an application scope with Table Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/fb-application-scope.md).\n\nRole required: personalize\\_forms, personalize\\_dictionary, and flow\\_designer permissions \\(or relevant AES user role and delegated developer permissions\\). For more information, see [Delegate developers using AES](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/app-engine-studio/aes-app-dev-workflow.md).\n\n### Procedure\n\n1.  Launch Table Builder as described in [Accessing Table Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/accessing-form-builder.md).\n\n2.  Select the **Flows** tab.\n\n    The flows triggered by the selected table are listed as flow cards.\n\n3.  4.  Filter or search the list of flow cards as needed to find the desired flow.\n\n<table id=\"table_zkp_3zn_15b\"><thead><tr><th>\n\nOption\n\n</th><th>\n\nSteps\n\n</th></tr></thead><tbody><tr><td>\n\nSearch text\n\n</td><td>\n\nType a keyword in the **Search** box. The list of cards will be filtered as you type.\n\n</td></tr><tr><td>\n\nSort flows\n\n</td><td>\n\nSelect an option from the sorting list to sort the flow cards.1.  Flow name \\(a to z\\)\n2.  Flow name \\(z to a\\)\n3.  Updated by \\(a to z\\)\n4.  Updated by \\(z to a\\)\n5.  Updated \\(recent to last\\) - Default option\n6.  Updated \\(last to recent\\)\n\n\n</td></tr><tr><td>\n\nFilter flows by setting up filter criteria\n\n</td><td>\n\n1.  Select the filter icon \\(\\[Omitted image \"filter-flows.png\"\\] Alt text: Filter flows.\\).\n2.  Add your filter condition criteria including any AND/OR logic.\n3.  To add additional conditions, select **+ New condition set**.\n4.  Select **Apply**.\n\n\n</td></tr></tbody>\n</table>\n### What to do next\n\n-   Select the flow card to edit your new flow using Workflow Studio. See [Modify a record-based flow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/flows-tb.md).\n-   Create a new record-based flow from an existing one. See [Copy a record-based flow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/flows-tb.md).\n-   Delete the flow. See [Delete a record-based flow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/flows-tb.md).\n\n## Add a record-based flow\n\nAdd flows that are triggered when a table record is updated, created, or both updated and created by using the **Flows** tab in Table Builder.\n\n### Before you begin\n\n-   Launch Table Builder. For more information, see [Accessing Table Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/accessing-form-builder.md).\n-   \\(Optional\\) Choose a domain to work within \\(if not global\\). For more information, see [Domain separation and Table Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/form-builder-domain-separation.md).\n-   \\(Optional\\) Choose an application scope to work within \\(if not global\\). For more information, see [Using an application scope with Table Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/fb-application-scope.md).\n\nRole required: personalize\\_forms, personalize\\_dictionary, and flow\\_designer permissions \\(or relevant AES user role and delegated developer permissions\\). For more information, see [Delegate developers using AES](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/app-engine-studio/aes-app-dev-workflow.md).\n\n### Procedure\n\n1.  Launch Table Builder as described in [Accessing Table Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/accessing-form-builder.md).\n\n2.  Select the **Flows** tab.\n\n3.  Select **Add flow**.\n\n4.  On the Add flow form, fill in the following fields.\n\n    |Field|Description|\n    |-----|-----------|\n    |Name|Name to uniquely identify your flow. The system computes the internal name of the flow from the name.|\n    |Description|Description of your flow.|\n\n5.  To enter advanced options for your flow, select **Show advanced options** on the New Flow form.\n\n<table id=\"table_kdg_zxh_ldb\"><thead><tr><th>\n\nField\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nProtection\n\n</td><td>\n\nOption that you can select if the flow is read-only. You can only select a value when you create the flow in an application scope that you own.\n\n</td></tr><tr><td>\n\nRun as\n\n</td><td>\n\nOption to specify the user that runs the flow. You can select the system user or the user who initiates the session. Select the user who initiates the session option when updates should come from the user who triggered the flow. For example, use this option when you want the incident record comments to come from the user who started the flow. Settings for the Run as option in a flow don't apply to child subflows.\n\n To create a flow that can run with a personal OAuth token, select the user who initiates the session option. If the user who is running the flow has a personal OAuth token, the flow runs with that token. For more information about creating a personal OAuth token, see [OAuth 2.0 credentials](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/oauth-2-credentials.md).\n\n When flows run as the user who initiates the session, the system limits the flow actions by user access control list \\(ACL\\) restrictions. Ensure that security restrictions don't prevent users who trigger the flow from performing flow actions. Flows that are run by the initiating user also respect user-specific settings, such as the date/time formats.\n\n **Note:** Inbound email flows ignore this setting and always run as the user who initiates the session. To test access controls for an inbound email flow, impersonate a typical inbound email user and manually trigger the flow.\n\n</td></tr><tr><td>\n\nRun with roles\n\n</td><td>\n\nRoles that the flow runs with. This option is only available when **Run as** is set to **user who initiates the session**.\n\n</td></tr></tbody>\n</table>6.  Select **Continue**.\n\n7.  Choose the event that your flow will be triggered by.\n\n<table id=\"choicetable_nl2_cmz_ztb\"><tbody><tr><td id=\"d91240e740\">\n\n**When the record is created**\n\n</td><td>\n\nCreate a flow that is triggered when a record in the selected table is created.\n\n</td></tr><tr><td id=\"d91240e749\">\n\n**When the record is updated**\n\n</td><td>\n\nCreate a flow that is triggered when a record in the selected table is updated.\n\n</td></tr><tr><td id=\"d91240e758\">\n\n**When the record is created or updated**\n\n</td><td>\n\nCreate a flow that is triggered when a record in the selected table is created or updated.\n\n</td></tr></tbody>\n</table>    The flow that you just created is displayed in the flow diagramming view. See [Flow diagramming view](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/flow-diagramming-view.md).\n\n8.  Select **Add node**, and then select one of the following options to modify your flow:\n\n<table id=\"table_smq_3ys_tcb\"><thead><tr><th>\n\nOption\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nAction\n\n</td><td>\n\nSelect the desired action. Workflow Studio includes [Workflow Studio actions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/flow-actions.md) that are available to flows and subflows. Alternatively, a user with the action\\_designer role can create additional actions to add to flows. The [Integration Hub](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/integrationhub.md) and [Spokes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/spokes.md) plugins install additional actions.\n\n To add draft actions from the More Actions menu, set **Show draft actions** to **true**.\n\n To view spokes that are available in the ServiceNow Store, set **Show store spokes** to **true** from the More Actions menu.\n\n**Note:** Under **Not Installed Spokes**, the system displays spokes that are available in the ServiceNow Store based on compatibility with the ServiceNow version and application dependency on Workflow Studio.\n\n</td></tr><tr><td>\n\nFlow Logic\n\n</td><td>\n\nSelect an option to specify conditional or repeated operations.\n\n</td></tr><tr><td>\n\nSubflow\n\n</td><td>\n\nSelect a published subflow and define the input values. In addition to adding a subflow as a flow action, you can enable the **Show triggered flows** option from the More Actions menu to select an activated flow and define the required inputs. Running a triggered flow ignores its trigger conditions and runs all actions.\n\n</td></tr></tbody>\n</table>    **Note:** Alternately, you may toggle the Workflow Studio default view from the view selector, and then select **Add an Action, Flow Logic, or Subflow** in that view of Workflow Studio. For more information, see [Flow diagramming view](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/flow-diagramming-view.md).\n\n9.  Continue modifying your flow in Workflow Studio.\n\n    **Note:** For detailed information on how to work with flows for your application, see [Create a flow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/create-flow.md).\n\n10. Select **Save**.\n\n    Workflow Studio saves a draft of the flow, trigger, and actions.\n\n\n### What to do next\n\nTest your flow until you're ready to activate it. For more information on testing and editing flows, see [Activate a flow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/flow-activate.md).\n\n**Note:** Your application can trigger only activated flows. For detailed information on how to design, test, and activate flows for your application, see [Flows in Workflow Studio](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/exploring-flows.md).\n\nTo return to the comprehensive list of flows related to the selected table after editing a flow, select the Additional actions \\( \\[Omitted image \"ellipsisIcon.png\"\\] Alt text: Additional actions menu.\\) menu to the right of the **Flows** tab, and then select **All flows**.\n\n## Modify a record-based flow\n\nEdit flows that are triggered when table records that you select are updated, created, or both updated and created by using the **Flows** tab in Table Builder.\n\n### Before you begin\n\n-   Launch Table Builder. For more information, see [Accessing Table Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/accessing-form-builder.md).\n-   \\(Optional\\) Choose a domain to work within \\(if not global\\). For more information, see [Domain separation and Table Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/form-builder-domain-separation.md).\n-   \\(Optional\\) Choose an application scope to work within \\(if not global\\). For more information, see [Using an application scope with Table Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/fb-application-scope.md).\n\nRole required: personalize\\_forms, personalize\\_dictionary, and flow\\_designer permissions \\(or relevant AES user role and delegated developer permissions\\). For more information, see [Delegate developers using AES](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/app-engine-studio/aes-app-dev-workflow.md).\n\n### About this task\n\nThe **Flows** tab in Table Builder lists flows triggered by record changes to a table. You can manage these flows from the record table that triggers the workflow.\n\n### Procedure\n\n1.  Launch Table Builder as described in [Accessing Table Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/accessing-form-builder.md).\n\n2.  Select the **Flows** tab.\n\n    The available flows that are triggered by the table are listed as flow cards.\n\n3.  Filter or search the list of flow cards as needed to find the desired flow.\n\n    See [Find a record-based flow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/flows-tb.md).\n\n4.  Select a flow card to open the flow for editing.\n\n5.  Edit the record-based flow by using Workflow Studio.\n\n    For detailed information on how to work with flows for your application, see [Create a flow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/create-flow.md).\n\n    **Note:** To return to the list of flow cards that are related to the table, select the Additional actions \\( \\[Omitted image \"ellipsisIcon.png\"\\] Alt text: Additional actions menu.\\) menu to the right of the **Flows** tab, and then select **All flows**.\n\n6.  Select **Save**.\n\n\n### What to do next\n\nTest your flow until you're ready to activate it. For more information on testing and editing flows, see [Activate a flow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/flow-activate.md).\n\n**Note:** Your application can trigger only activated flows. For detailed information on how to design, test, and activate flows for your application, see [Flows in Workflow Studio](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/exploring-flows.md).\n\nTo return to the list of flows related to the table that you selected after you edited a flow, select the Additional actions \\( \\[Omitted image \"ellipsisIcon.png\"\\] Alt text: Additional actions menu.\\) menu to the right of the **Flows** tab, and then select **All flows**.\n\n## Delete a record-based flow\n\nDelete a record-based flow by using the **Flows** tab in Table Builder.\n\n### Before you begin\n\n-   Launch Table Builder. For more information, see [Accessing Table Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/accessing-form-builder.md).\n-   \\(Optional\\) Choose a domain to work within \\(if not global\\). For more information, see [Domain separation and Table Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/form-builder-domain-separation.md).\n-   \\(Optional\\) Choose an application scope to work within \\(if not global\\). For more information, see [Using an application scope with Table Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/fb-application-scope.md).\n\nRole required: personalize\\_forms, personalize\\_dictionary, and flow\\_designer permissions \\(or relevant AES user role and delegated developer permissions\\). For more information, see [Delegate developers using AES](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/app-engine-studio/aes-app-dev-workflow.md).\n\n### Procedure\n\n1.  Launch Table Builder as described in [Accessing Table Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/accessing-form-builder.md).\n\n2.  Select the **Flows** tab.\n\n    The available flows that are triggered by the table are listed as flow cards.\n\n3.  Filter or search the list of flow cards as needed to find the desired flow.\n\n    See [Find a record-based flow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/flows-tb.md).\n\n4.  Select the Additional actions \\( \\[Omitted image \"ellipsisIcon.png\"\\] Alt text: Additional actions menu.\\) menu in the top-right corner of the flow that you want to delete, and then select **Delete** from the list of options.\n\n5.  In the delete confirmation window, enter `DELETE`, and then select **Delete**.\n\n6.  Select **Save**.\n\n\n## Copy a record-based flow\n\nCreate a new record-based flow from an existing flow by using the **Flows** tab in Table Builder.\n\n### Before you begin\n\n-   Launch Table Builder. For more information, see [Accessing Table Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/accessing-form-builder.md).\n-   \\(Optional\\) Choose a domain to work within \\(if not global\\). For more information, see [Domain separation and Table Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/form-builder-domain-separation.md).\n-   \\(Optional\\) Choose an application scope to work within \\(if not global\\). For more information, see [Using an application scope with Table Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/fb-application-scope.md).\n\nRole required: personalize\\_forms, personalize\\_dictionary, and flow\\_designer permissions \\(or relevant AES user role and delegated developer permissions\\). For more information, see [Delegate developers using AES](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/app-engine-studio/aes-app-dev-workflow.md).\n\n### Procedure\n\n1.  Launch Table Builder as described in [Accessing Table Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/accessing-form-builder.md).\n\n2.  Select the **Flows** tab.\n\n    The available flows that are triggered by the table are listed as flow cards.\n\n3.  Filter or search the list of flow cards as needed to find the desired flow.\n\n    See [Find a record-based flow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/flows-tb.md).\n\n4.  Select the Additional actions \\( \\[Omitted image \"ellipsisIcon.png\"\\] Alt text: Additional actions menu.\\) menu in the top-right corner of the flow that you want to delete, and then select **Copy** from the list of options.\n\n5.  In the Create a copy of the flow window, enter a name for the copied flow and select **Copy**.\n\n6.  Edit the flow using Workflow Studio.\n\n    For detailed information on how to work with flows for your application, see [Create a flow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/create-flow.md).\n\n7.  Select **Save**.\n\n    **Note:** To return to the list of flows after editing a flow, select the Additional actions \\( \\[Omitted image \"ellipsisIcon.png\"\\] Alt text: Additional actions menu.\\) menu to the right of the **Flows** tab, and then select **All flows**.\n\n\n"}}