Managing Processes

Note:

Make sure you:

• are in the correct Orchestrator folder context, and
• have the right user permissions to view and manage processes.

Generating Forms to Provide Inputs to a Queue

1. Create a queue in Orchestrator.
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 that launches the consumer process whenever a new item is added to that queue.

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

Make sure you have the Queue Process User role.

Generating Forms to Provide Inputs to a Job

1. Create a workflow with input arguments in the main .xaml file of the automation project and publish it to Orchestrator.
2. Deploy a process from the above package, and provide default values for the input parameters if any.

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

Make sure you have the Job Process User role.

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 Form Designer incorporated in the Create Form Task activity (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 tab.
2. Define the argument that requires a file upload:
   2.1. Append the _storage suffix to the argument name.

   2.2. Set the argument Direction to IN/OUT.

3. For Queues, append the _storage suffix to the property name in the Queue schema.
   
   

   

   
   

The storage bucket argument

1. In Orchestrator, create a storage bucket.
2. Inside your workflow in Studio, open the Arguments tab.
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 > Automations > Processes > Edit > 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).
   
   

   

   
   
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 do the following:

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.

Business User Experience

1. Log 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.