Streamline your work using UiPath Orchestrator. Seamlessly connect with popular apps to automate tasks and free up your time without any coding required. Enablement for business departments to automate their work and integration with an RPA ecosystem make it easy to use and efficient.

UiPath Orchestrator enables seamless automation of tasks and workflows using robots and RPA. Integration with other apps and an RPA ecosystem allows for easy integration and automation across departments.

UiPath Orchestrator - Automate Tasks and Streamline Workflows

This package allows you to Create Assets (Both Single and Value per Robot), Create Queue, Upload Package, Create Process, Create Environment, Add robots to the environment and provision robot from an input Excel file to target Orchestrator Instance (considering Organization units).

The workflow is created using the custom activity where it takes input from the Excel file and creates assets queues etc.

The developer will create the Excel in the development phase and the same Excel can be used to migrate to different environments.

[**Workflow**](https://github.com/bharatchhajed0617/migrateprocessuipath):

*   The user must provide Orchestrator details, Assets, Queues, Processes, Packages, Environment in an Excel file that will be provided to the user including with the package. 
*   A workflow is created that takes input from an Excel file for all the details mentioned in the first point and uses different activities from the package to create the data in the target Orchestrator Instance.
*   This package uses Orchestrator APIs to perform the above functionalities.

Below are the Activities in the Package:

*   Orchestrator Scope
*   Create Asset
*   Create Asset Per Robot
*   Create Machine
*   Create Queue
*   Get Robot Status
*   Provision Robot
*   Start Job
*   Stop Job
*   Update Package Version
*   Upload Library Package
*   Upload Package

Uses Orchestrator API and will perform Release management actions like Create Assets(Both Single and Value per Robot), Create Queue, Upload Package, Create Process, Create Environment.

This Custom Activity contains the following two activities:

*   **GetTasks**
*   **ExtractTasksFormDataTable**

With **GetTasks** you can get a Json object with all the tasks fulfilling the filters properties (listed below). 

If you set more than 1 filter property, the logic operator "and" will be applied automatically except for CustomFilters which has a special behaviour: it allows you to add a custom query part to the rest of the query so, if you are setting other properties as well you have to specify the logic operator, otherwise you don't have to. 

**Examples:**

1.  If you want to extract all the tasks whose title is not "Report" you just have to set the CustomFilters property this way "not(Title eq 'Report')"
2.  if you want to extract all the tasks with priority "High" and Catalog='Invoices' or Catalog='Receipts' you have to set: Priority='High', CustomFilters="and (TaskCatalogName eq'Invoices' or TaskCatalogName eq 'Receipts')"

**CustomFilters**: if set along with other properties, you need to specify the logic operator. For example: if Status is set to "Pending" and you want to add a custom filter, you have to set CustomFilter=" ". If CustomFilter is the only filter, you just have to set CustomFilter="" (without the logic operator). You can find more info about api requests filtering [here](https://docs.uipath.com/orchestrator/reference/building-api-requests).

  

With **ExtractTasksFormDataTable** you can extract Tasks fields and related TaskForm data fields. The activity properties are:

*   jsonObjFromTasksAPI: the Json object returned by GetTasks activity
*   TaskFieldsToExtract: an array of string, listing the Task fields to be extracted
*   TaskFormFieldsToExtract: an array of string, listing the TaskForm data fields to be extracted

Get Orchestrator action tasks item, filtered by their fields. Extract data table with Action Tasks fields and related Action TaskForm fields

Product manager

When developing RPA solutions, we breakdown our processes into multiple REFramework solutions or simple workflow files which run independently. For example, when dealing with web scraping and processing, we develop a dispatcher solution and a performer solution using REFramework which are independently executed one after the other.

  

In order to execute the Performer right after the Dispatcher process completes, people use many approaches. Some tend to include the Performer within the dispatcher workflow which can make it much more complicated while some come up with workaround solutions to handle this manually or by simple controller workflows.

  

However, if these Dispatcher, Performer and all the independent solutions are in UiPath Orchestrator as separate processes, we can easily execute them without any hassle using this controller template. In situations where you need to schedule these tasks to be run one after the other at a particular day/ time, rather than scheduling each and every independent process, we can simply schedule this one controller solution and it will handle the rest automatically.

  

Prerequisites

  

The tasks that should be executed through the controller workflow solution should be published to the Orchestrator and should be available under Processes

About the Controller

  

The controller workflow is developed using REFramework. We have to include all the processes that needs to be run in the sequential order in Configuration excel sheet. The process will access this excel sheet and extract the jobs that needs to be executed one after the other.

REFramework template to centrally provide the execute command to other independent REFramework solutions or workflow processes which are in Orchestrator that need to be executed in a sequencial order

Simple engine to pull and process a Transaction from an Orchestrator queue

This engine contains code that will do the following:

1\. Read a configuration file, by default located in Data\\Config.xlsx and output as a dictionary named config

2\. Calls ProcessLayer\\InitAllApplications.xaml, where you should initialize applications

3\. While there are items in the Queue, read a new Item and process it.

*   3.1 Get Item from queue
*   3.2 Execute Process - retry if you run into a AppEx
*   3.2.1 Calls ProcessLayer\\ProcessTransaction.xaml, where you should input data into your opened applications
*   3.2.2 Evaluate Process wb output
*   3.2.3 Recover if wb failed with AppEx
*   3.2.3.1 Call ProcessLayer\\CloseAllApplications.xaml
*   3.2.3.2 Call ProcessLayer\\InitAllApplications.xaml

4\. Call ProcessLayer\\CloseAllApplications.xaml

A simple workblock engine made in UiPath Studio to process Orchestrator queue items

The solution proposes to export configurable data contained by the queue items in the Orchestrator and save them as an Excel file.

It is possible to use the current Orchestrator context of the Robot (No Auth) or connect to a different Orchestrator/Tenant, providing an Orchestrator.

**Arguments**

*   Required StrQueueName The Orchestrator Queue Name.
*   Required StrReportDestionationPath The location where the xlsx report will be saved Required (with Auth) StrOrchestratorServerURL The Orchestrator from where the queue report will be permformed (ex:http://platform.uipath.com/). 
*   Required StrColumnMapping The expected report columns - See Column mapping Details bellow.
*   Required (with Auth) StrTenancyName The Orchestrator Tenant consider - Let Blank for 'Default' - The tenancy name is only considered if Auth is used.
*   Required (with Auth) StrCredentialName Criterion to determine if Auth is used - The Credentialname which will be used to pull Credential From either Orchestrator. or the Windows Crendential manager - The Solution is using GetAppCrendentials Workflow from ReFramework.
*   Optional DtmReportFrom The Date from when the Queue Items will be considered.
*   Optional DtmReportTo The Date until when the Queue Items will be considered.

  

**Columns Mapping Details:**

The column mapping will have to be specific as a CSV string to determine the data exported.

It is possible to export different type of data based on prefix

**Prefixes / Description**

**data.** Refer to the Specific content 

**exc.** Refer to the exception property

**output.** Refer to the output data stored

**No prefix** Refer to a property of the Queue Item (ex: Status, Priority etc…)

Example of Column mapping strings:

Priority, Key, Status, exc.Details, exc.Type, exc.Reason

CreationTime, StartProcessing, EndProcessing, data.TransactionID, RetryNumber, output.ConfirmationNumber, exc.Details, exc.type, exc.reason

It is recommended to have a read on the API documention (example [here](https://platform.uipath.com/swagger/ui/index#!/QueueItems/QueueItems_GetById)) to see which properties will be available for extraction.

An UiPath project aiming to simplifly reporting based on a specific Orchestrator queue based on the REST API.

	Listing	Apps	Downloads
	Orchestrator Activities Uses Orchestrator API and will perform Release management actions like Create Assets(Both Single and Value per Robot), Create Queue, Upload Package, Create Process, Create Environment.		159
	Orchestrator Tasks API Helper Get Orchestrator action tasks item, filtered by their fields. Extract data table with Action Tasks fields and related Action TaskForm fields		<100
	test-external test-external		<100
	lead with tags alex test		<100
	Central Controller Template For Sequential Jobs REFramework template to centrally provide the execute command to other independent REFramework solutions or workflow processes which are in Orchestrator that need to be executed in a sequencial order		229
	Queue MiniFramework A simple workblock engine made in UiPath Studio to process Orchestrator queue items		188
	Symphony - Queue Reporting An UiPath project aiming to simplifly reporting based on a specific Orchestrator queue based on the REST API.		163

Automate Tasks and Streamline Workflows

Explore Studio Desktop listings

Similar apps

automation

automation

automation

automation