{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":16746,"path":"governance-risk-compliance/create-new-subflow-for-bcm.md","title":"Create a subflow form","bundle":null,"doc_type":null,"release":"australia","body":"\n# Create a subflow form\n\nUse the Create a subflow form to automate a manual recovery task within the business continuity plan.\n\n## Create a subflow form\n\nFor description of the field values, see the table.\n\n<table id=\"table_FloorForm\"><thead><tr><th>\n\nField\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td class=\"sub-head\" colspan=\"2\">\n\n \n\n</td></tr><tr><td>\n\nSubflow Name\n\n</td><td>\n\nName of the subflow. For example, if you want to automate a manual task for sending an email, you can name the subflow as Send an email subflow.\n\n</td></tr><tr><td>\n\nDescription\n\n</td><td>\n\nDescription of the subflow.\n\n</td></tr><tr><td>\n\nApplication\n\n</td><td>\n\nApplication scope for creating the subflow in. For the BCM tasks, you can select GRC: Business Continuity Management.\n\n</td></tr><tr><td>\n\nAccessible From\n\n</td><td>\n\nAll application scopes that the subflow can be accessed from.\n\n</td></tr><tr><td>\n\nCategory\n\n</td><td>\n\nCategory or logical group for the subflow. For the BCM automation tasks, you can select the **BCM: Task automation** category.\n\n</td></tr><tr><td>\n\nProtection\n\n</td><td>\n\nOption to mark the subflow as read-only. When you create the subflow in an application scope that you own, you can select a value for this field. Editing permissions and protection for the subflow. Select one of these options:-   **None**: Default value. Select this option to edit the subflow.\n-   **Read-only**: Mark the subflow as read-only. Only the creator of the subflow can edit it.\n\n</td></tr><tr><td>\n\nSubflow annotation\n\n</td><td>\n\nAnnotation for the subflow. The help text under the subflow title in Workflow Studio helps the flow designers to understand what the subflow does when it is used in a flow.\n\n</td></tr><tr><td>\n\nRun As\n\n</td><td>\n\nOption to define the user who runs the subflow. Select one of these options:-   **User who initiates 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 to receive the approval email from the approver.\n-   **System user**: Select the system user to run the subflow.\n\n</td></tr><tr><td>\n\nRun with roles\n\n</td><td>\n\nRoles that the subflow runs with. This option is only available when **Run as** is set to **User who initiates the session**. For example, a plan user should have the email\\_api\\_send role to send the email and the sn\\_bcm.program\\_manager role to read the BCM tasks.\n\n</td></tr></tbody>\n</table>For more information on creating a subflow, see [Create a subflow in Workflow Studio](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/create-subflow.md).\n\n**Parent Topic:**[Automate recovery tasks](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/automate-the-recovery-tasks.md)\n\n"}}