--- schema_version: "1" id: 9a8235564cb79f2960070b0b10fd7bf92a030111fcfb73380aa98fe0c81649f7 title: Workflow Initialization collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/rpa-builder/latest/workflow-initialization.md canonical_url: https://docs.mulesoft.com/rpa-builder/latest/workflow-initialization source_site: docs.mulesoft.com content_type: documentation content_hash: 4c6b42702f1f60d57ff3241bfd6eaad14f0cc202525c82a4ef442701e3cea856 description: MuleSoft Documentation Site release: "6.7" latest: true --- --- product: RPA Builder version: 6.7 is-latest-version: true --- # Workflow Initialization > For the full documentation index, see: https://docs.mulesoft.com/llms.txt ![The Workflow Initialization window](/mulesoft/current/en-us/rpa-builder/latest/_images/workflow-initialization.png) The Workflow Initialization element groups different configuration elements. You can only insert suitable elements here, such as the Actions Steps Activity Parameters, STC Protector or Settings. Workflow Initialization is at the project level and cannot be deleted. The Workflow Initialization section contains additional elements that are not available in the Toolbox. The **Settings** action step is located in the global initialization section of a Workflow. It is always there and cannot be removed. This action step defines basic path information and checks paths for all action steps of the type File Operations. In addition, you can define the proxy settings for the action step REST Call in the Network Settings tab. ## Workflow Settings Properties The following are the properties of the **Settings** action step. - **Misc** - **Base Path** Shows the currently selected base path. - **Generate Subfolder per run** When you enable this option, RPA Builder creates a temporary directory using a GUID (unique random number). - **Remove Base Path Subfolder after Run** When you enable this option, RPA Builder deletes the temporary directory after the action step runs. - **Use Allowed Paths limitation** When enabled, only the _allowed_ paths set in **Workflow Initialization** → **Settings** are used. Note that before executing any action step of the type File Operations, the specified Directory Path is checked against the _Allowed Paths_. If the Directory Path specified in the action step is not allowed, the Workflow terminates and displays an error message. > [!WARNING] Do not disable the **Use Allowed Paths limitation** option if important data is > stored on your system, as this information could be deleted by mistake. - **Network Settings** - **Proxy setting** - **No Proxy** (Default) No proxy is used. - **Use system proxy settings** The proxy settings of the operating system are used. No further configuration is necessary. - **Manual proxy configuration** The connection data to the proxy can be entered manually in the wizard. - **Proxy url** Shows the address to the proxy server entered in the Wizard. - **Use Authentication** Shows if this option is enabled in the wizard. ## Workflow Settings Wizard - **File Operation Settings** ![The Workflow Settings Wizard](/mulesoft/current/en-us/rpa-builder/latest/_images/workflow-settings-wizard.png) These settings apply for all File Operation action steps. - **Base Path Settings** - **Base Path (%Stws\_BasePath%)** Specifies the base path to use for all action steps of the type File Operations. Use the Browse button (![The browse button](/mulesoft/current/en-us/rpa-builder/latest/_images/browse-button.png)) to browse the path. If you leave the path blank, the default `%Stws_BasePath%` is used internally as the path. To retrieve the specified base path later when configuring action steps of the type File Operations, use the Pin button (![The Pin button](/mulesoft/current/en-us/rpa-builder/latest/_images/pin-icon.png)) and the `Settings-BasePath` option. The base path is shown in the Workflow Run Results and Print Preview. - **Base Path Preview** Shows the currently selected base path. - **Generate subfolder per run** When you enable this option, RPA Builder creates a temporary directory using a GUID (unique random number). The temporary directory is shown in the **Base Path Preview** and appended with `\[RunGuidFolder]`. - **Remove subfolder after run** Enabling this option means that the temporary directory is deleted after the action step has been run. - **Allowed Paths** - **No path limitations for File Operation Action Steps (default)** Use this option if you don’t want to set any limitations on the path for executing the action step and allow all possible paths. > [!WARNING] Do not disable the **Use Allowed Paths limitation** option if important data is > stored on your system, as this information could be deleted by mistake. - **Allow File Operation Action Steps only in following paths** Use this option if you want to restrict action step execution to certain paths (Allowed Paths). The gray field then shows the path specified in **Base Path Settings**, which means that, for File Operations, only the base path is allowed. Add up to 10 more allowed paths using the (![The Add icon](/mulesoft/current/en-us/rpa-builder/latest/_images/add-icon.png) **Add Allowed Path …​**) button. Enter a path in the field shown or browse for a path using the Browse (![The browse button](/mulesoft/current/en-us/rpa-builder/latest/_images/browse-button.png)) button. Additional paths can be deleted using the **Delete Path** (![The Delete Path button](/mulesoft/current/en-us/rpa-builder/latest/_images/delete-icon.png)) button. The paths calculated at runtime are checked against the **Allowed Paths**. Allowed paths show in the Workflow Run Results and Print Preview. Note that before executing any action step of the type File Operations, the specified Directory Path is checked against the **Allowed Paths**. If the specified Directory Path is not allowed in the action step, the Workflow terminates and displays an error message. - **Runtime Environment Settings** ![The Workflow Settings Wizard showing the Runtime Environment Settings tab](/mulesoft/current/en-us/rpa-builder/latest/_images/workflow-settings-environment-wizard.png) - **Name** and **Value** Create new environment variables using the (![The Add icon](/mulesoft/current/en-us/rpa-builder/latest/_images/add-icon.png) **Add Environment Variable …​**) button. Enter the name of the new environment variables in the **Name** field enclosed in `%` signs, for example `%newPath%`. Enter a path for the new variable in the **Value** field. To enter path information, it is best to browse for the path using the Browse (![The browse button](/mulesoft/current/en-us/rpa-builder/latest/_images/browse-button.png)) button. Additional variables can be deleted using the **Delete Environment Variable** (![The Delete Path button](/mulesoft/current/en-us/rpa-builder/latest/_images/delete-icon.png)) button. - **Network Settings** ![The Workflow Settings Wizard showing the Network Settings tab](/mulesoft/current/en-us/rpa-builder/latest/_images/workflow-settings-network-wizard.png) To run the action step _REST Call_ via a proxy, configure the appropriate settings here. If an additional authentication is necessary, activate the checkbox **Use Authentication** and enter **Username** and **Password**. See [Workflow Settings Properties](#properties) for a detailed description of the Network Settings properties that are available in the Wizard. - **Error Handling Settings** ![The Workflow Settings Wizard showing the Error Handling Settings tab](/mulesoft/current/en-us/rpa-builder/latest/_images/workflow-settings-error-handling-wizard.png) Specify the behavior of the Error Out variable when receiving more than one error message. Choose between appending or overwriting values. ## See Also - [Workflow Elements in Detail](https://docs.mulesoft.com/rpa-builder/latest/workflow-elements-in-detail) - [Workflow Finalization](https://docs.mulesoft.com/rpa-builder/latest/workflow-finalization) - [File Operations](https://docs.mulesoft.com/rpa-builder/latest/toolbox-file-operations)