# Managing processes

> * You are in the correct Orchestrator folder context.
* You have the right [user permissions](https://docs.uipath.com/action-center/standalone/2025.10/user-guide/roles-and-permissions#custom-roles---processes) to view and manage processes.

## Prerequisites

* You are in the correct Orchestrator folder context.
* You have the right [user permissions](https://docs.uipath.com/action-center/standalone/2025.10/user-guide/roles-and-permissions#custom-roles---processes) to view and manage processes.

## Generating forms to provide inputs to a queue

Make sure you have the [Queue Process User role](https://docs.uipath.com/action-center/standalone/2025.10/user-guide/roles-and-permissions).

1. [Create a queue in Orchestrator](https://docs.uipath.com/orchestrator/standalone/2025.10/user-guide/managing-queues-in-orchestrator#creating-a-queue).
2. Create a consumer automation project that processes items from the queue and passes data into third-party systems as imposed by the specific business scenario.
3. [Create a queue trigger](https://docs.uipath.com/orchestrator/standalone/2025.10/user-guide/managing-triggers) that launches the consumer process whenever a new item is added to that queue.

**Result**: The queue becomes available on the **Processes** page for a user with the appropriate access rights to the folder in which the queue resides.

## Generating forms to provide inputs to a job

Make sure you have the [Job Process User role](https://docs.uipath.com/action-center/standalone/2025.10/user-guide/roles-and-permissions).

1. [Create a workflow with input arguments](https://docs.uipath.com/studio/standalone/2025.10/user-guide/using-arguments#example-of-using-an-argument) in the main `.xaml` file of the automation project and [publish it to Orchestrator](https://docs.uipath.com/studio/standalone/2025.10/user-guide/about-publishing-automation-projects).
2. [Deploy a process from the above package](https://docs.uipath.com/action-center/standalone/2025.10/user-guide/managing-processes#managing-processes), and provide default values for the input parameters if any.

**Result**: The process becomes available on the **Processes** page for a user with the appropriate access rights to the folder in which the process resides.

## Triggering unattended processes through file upload

As an RPA developer, you can build unattended processes that accept files as input from the business users, using the **UiPath Form Designer** incorporated in the **Create Form Task** activity (comes with the UiPath.Persistence.Activities activity package v1.1.8+). The process' design includes special arguments that are used to upload the files. One argument allows a single file upload. There are two main types of arguments that you can use to trigger the process:

### The `_storage` argument

1. Inside your workflow in Studio, open the **Arguments** panel.
2. Define the argument that requires a file upload:

   2.1. Add the `_storage` suffix to the argument name.

   2.2. Set the argument **Direction** to **IN/OUT**.
3. For Queues, add the `_storage` suffix to the property name in the [Queue schema](https://docs.uipath.com/orchestrator/standalone/2025.10/user-guide/about-queues-and-transactions#schema-definitions).

   ![docs image](https://dev-assets.cms.uipath.com/assets/images/action-center/action-center-docs-image-100952-230566f5-dc333e29.webp)

### The storage bucket argument

1. In Orchestrator, [create a storage bucket](https://docs.uipath.com/orchestrator/standalone/2025.10/user-guide/about-queues-and-transactions#schema-definitions).
2. Inside your workflow in Studio, open the **Arguments** panel.
3. Define an argument to indicate the actual storage bucket the files are uploaded to (for example, `BucketName`).
4. In Orchestrator, navigate to the corresponding process folder, then to **Automations**,**Processes**,**Edit** and then navigate to **Runtime arguments**.
5. Enter the name of the storage bucket created at step 1 as the value for the `BucketName` argument.
   :::important
   To allow file uploads, make sure to map the desired storage bucket to the `BucketName` argument of the workflow (see the above steps 4 and 5).
   :::

   ![docs image](https://dev-assets.cms.uipath.com/assets/images/action-center/action-center-docs-image-100195-8cdc2748-f9020c2d.webp)
6. In Queues, add the `BucketName` property in the Queue schema and map the name of your storage bucket to the `"default"` key.
   ```
   ...
         "UserFile_storage": {
         "$id": "#/properties/UserFile_storage",
         "type": "string",
         "title": "Upload Document",
         "default": "FileName",
         "examples": [
           "User FileName"
         ]
       },
       "BucketName": {
         "$id": "#/properties/BucketName",
         "type": "string",
         "title": "BucketName",
         "default": "ActionsTest",
         "examples": [
           "User FileName"
         ]
       },
   ...
   ```
7. To specify a storage folder path different to the current workflow or queue, add an argument `BucketFolderPath` and provide it with a default value in the same manner as above.

### To trigger unattended processes with file upload

1. Navigate to **Processes** on the left-hand menu.
2. Run a process which allows for file upload. The form is displayed to the right.
3. Fill in the fields and attach the file.
4. Click **Submit**.

Follow the sample workflow on how to [trigger unattended processes with file upload control using a queue schema](https://docs-dev.uipath.com/action-center/automation-cloud/latest/user-guide/release-notes-general-availability).

## Business user experience

1. Sign in to Action Center.
2. Navigate to **Processes**.
3. Launch a process by clicking **Run**. If the process has input parameters, a form is displayed.
4. Fill in the values for the input parameters and click **Submit**.
5. Click **Refresh** to view the latest status of a transaction.
6. The workflow is suspended and an action is generated.
7. After you complete the action, the workflow resumes.
8. Upon completion, you can navigate to the **Details** page to view or copy the output.