Managing Processes

Prerequisites

• You are in the correct Orchestrator folder context.
• You have the right 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 in the Action Center website.for a user with the appropriate access rights to the folder in which the queue resides. That means you need to assign the user a role at the folder level in Orchestrator with the following permissions:

• View on Queues
• View,Edit,Delete on Transactions

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 in the Action Center website for a user with the appropriate access rights to the folder in which the process resides. That means you need to assign the user a role at the folder level with the following permissions:

• View on Processes
• View,Edit,Delete on Jobs

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

• In Studio, under the Arguments tab, add the _storage suffix to the name of the argument that requires a file upload, and set the Direction to IN, as it is an input from the business user.
• In Queues, add the _storage suffix to the property name in the Queue schema.

The storage bucket argument

• In Studio, under Arguments tab, add an argument (for example, BucketName) to indicate the actual storage bucket the files are uploaded to.
• In Orchestrator, configure the storage bucket and set it as a value for the BucketName argument by navigating to the process' folder > Automations > Processes > Edit > Runtime arguments.
• In Queues, add the BucketName property in the Queue schema and enter the name of the storage bucket for the "default" key.
• To specify a storage folder path different from the current workflow or queue, add an argument BucketFolderPath and provide it with a default value in the same manner as above.
  
  

  

  
  

  ...
        "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"
        ]
      },
  ...

  
  

  

  
  

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, by hovering over the corresponding tile and clicking Run process.
3. The form is displayed as a right-hand pane.
4. Fill in the fields and attach the file.
5. 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 the Action Center website.
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 the completes the action, the workflow resumes.
8. Upon completion, the user can navigate to the Details page to view/copy the output.