75675453-6287-4681-9033-6924c7cd592d.png

Effortlessly reserve dedicated blocks of time in your calendar, ensuring uninterrupted focus on critical tasks and projects. Streamline your interactions with Outlook calendars by automating event creation, invitation sending, and appointment management. Simplify scheduling by accurately calculating business working days between any two dates, enabling efficient resource allocation and planning. Retrieve the current date and time in any specific time zone to ensure synchronized coordination across different locations. Stay connected with your team by automating updates to your Teams and Slack status, keeping them informed of your availability and fostering collaboration.

Make every minute count and revolutionize your meeting management. Discover the power of the "Meeting Management" collection to optimize your productivity and supercharge your efficiency.

Automate scheduling and routine tasks to optimize collaboration and enhance efficiency.

Meeting Management

UiPath Orchestrator is your key to centralized control and management of automated processes. Seamlessly orchestrate and monitor your workflows from a single, user-friendly interface. With UiPath Orchestrator, gain real-time insights, streamline deployments, and enhance collaboration across your organization. Drive efficiency, scalability, and reliability in your automation initiatives with the power of UiPath Orchestrator. Elevate your automation journey and unlock unparalleled control over your digital workforce.

Elevate productivity with UiPath Orchestrator. Automate tasks across apps, freeing time for what matters. Empower teams and explore smarter workflows now.

UiPath Orchestrator Integrations

Solution Architect

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:**

*   The user must provide Orchestrator details, Assets, Queues, Processes, Packages, Environment in an Excel file that will be provided to the user including the package. 
*   A workflow is created that takes the 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.

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

Lead Engineer

**Sample use case:**

A process is scheduled to run only on the 5th business day of the month for doing payroll calculations for employees for the previous month. The Orchestrator scheduler runs every day for the first 10 days of the month to trigger the payroll process. The process first calls this custom activity to check if the current day is the 5th business day of the month. If this activity returns true, the process runs the payroll calculations. Otherwise, it does not take any actions until next day.

  

**Arguments:**

\- in\_Month\_MMM (String) - Optional input argument which allows the user to provide any month in the string format "MMM". Default value is the current month.

\- in\_OrchestratorCalendarName (String) - Optional input argument which allows the user to provide the Orchestrator calendar name. Default value leads to no non-working days to be considered including the weekend days.

\- in\_BusinessDayOfMonth (Int32) - The index of the business day to be checked for the given month. For example, to find the 5th business day of a month, the value for this argument is 5. Default value is 1 (1st working day of the month).

\- out\_NextWorkingDate (DateTime) - The output argument which returns the date of the nth business day of the month.

\- out\_WorkingDayFlag (Boolean) - The output argument which returns "True" if the out\_NextWorkingDate is the current day.

This activity returns the date of the nth business day of any month based on Orchestrator calendar

**Sample use case:**

  

A process is scheduled to run only on the 5th business day of the month for doing payroll calculations for employees for the previous month. 

  

The Orchestrator scheduler runs every day for the first 10 days of the month to trigger the payroll process. The process first calls this custom activity to check if the current day is the 5th business day of the month. If this activity returns true, the process runs the payroll calculations. Otherwise, it does not take any actions until next day.

  

**Arguments:**

*   in\_Month\_MMM (String) - Optional input argument which allows the user to provide any month in the string format "MMM". Default value is the current month.
*   in\_OrchestratorCalendarName (String) - Optional input argument which allows the user to provide the Orchestrator calendar name. Default value leads to no non-working days to be considered including the weekend days.
*   in\_BusinessDayOfMonth (Int32) - The index of the business day to be checked for the given month. For example, to find the 5th business day of a month, the value for this argument is 5. Default value is 1 (1st working day of the month).
*   out\_NextWorkingDate (DateTime) - The output argument which returns the date of the nth business day of the month.
*   out\_WorkingDayFlag (Boolean) - The output argument which returns "True" if the out\_NextWorkingDate is the current day.

This activity returns the date of the nth business day of any month based on Orchestrator calendar.

Technical Account Manager

**Introduction**

  

Summary reporting for multiple performers is a challenge that has been addressed in multiple ways. This documentation and custom activity present a methodology for doing reporting that is less apparent to most solution architects. It is simple and reliable. It eliminates many of the pitfalls of other methods like file contention on Excel files and race conditions between performers.

  

**Overview**

  

At a high level, this methodology uses a single “Reporting” transaction that is added to the queue by the dispatcher. This ensures that only 1 performer will attempt to do the reporting. The transaction is set to “Low” priority so that it is always the last transaction pulled from the queue. The custom activity is then invoked to extract the transactions from the queue. It will extract exception information for failed transactions as well as 'Output Data' for successful ones.

  

**Coding**

  

The coding is simple, and I have provided screenshots below.

  

**Dispatcher**

  

After the normal transactions are added, use a separate Add Queue Item with the properties set as shown in the image below.

  

**Performer**

  

The IF activity shown below will direct normal transactions to the Process.xaml and the Reporting transaction to a Reporting workflow.

  

**Summary Reporting**

  

For creating a summary transaction report, a great source of information is the queue transactions themselves. They have the business data used for the transaction as well as the status of each transaction, exception information, etc.

  

The Transaction Summary Report library handles all of these requirements.

· Waits for given other performer jobs to end

· Extracts all transactions from a queue since the given start date.

· Extracts exception details for failed transactions – Exception Type and Exception Reason

· Extracts the given columns of Specific Content data

· Extracts the given columns of Output Data

  

I have tested it in a test queue, and you can see the sample results below. I manually did a little formatting. You can also use the datatable output property to customize the report however you wish.

  

**Capturing Output Data**

  

Transactions have the ability to take additional data that may be relevant for analysis or reporting. This is accomplished by using the Set Transaction Status activity. As shown below in the RE Framework a collection of value pairs can be assigned to the “Output” property.

  

Warning: The Output collection can only be used for Successful transactions. For Exception transactions, the exception reporting information is already in place. If your code uses a Throw, include any needed reporting text there in the message.

  

The Output values are shown in the “Output Data” part of the transaction page in Orchestrator. See attached screenshots.

In the example below the column name is “TransactionOutput”. This is the string you’ll use in the string array argument called “OutputDataHeaders”. See the example below.

This activity is used for creating a transaction report for transactions in a queue. It is especially needed when there are multiple performers on the queue.

**Introduction**

  

Summary reporting for multiple performers is a challenge that has been addressed in multiple ways. This documentation and custom activity present a methodology for doing reporting that is less apparent to most solution architects. It is simple and reliable. It eliminates many of the pitfalls of other methods like file contention on Excel files and race conditions between performers.

  

**Overview**

  

At a high level, this methodology uses a single “Reporting” transaction that is added to the queue by the dispatcher. This ensures that only 1 performer will attempt to do the reporting. The transaction is set to “Low” priority so that it is always the last transaction pulled from the queue. The custom activity is then invoked to extract the transactions from the queue. It will extract exception information for failed transactions as well as 'Output Data' for successful ones.

  

**Coding**

  

The coding is simple, and I have provided screenshots below.

  

**Dispatcher**

  

After the normal transactions are added, use a separate Add Queue Item with the properties set as shown in the image below.  Optionally include a date time in this Reporting Transaction that will serve as the filter for the transactions pulled from the queue.

  

**Performer**

  

The IF shown below will direct normal transactions to the Process.xaml and the Reporting transaction to a Reporting workflow.

  

If you are using a unique Reference queue, you will want to add a date or DateTime to the Reference of your reporting Transaction. In that can you would use a .contains(“Reporting”) in the IF below instead.

  

The activity excludes all transactions from the report results that have “Reporting” in the Reference field.

  

**Summary Reporting**

  

For creating a summary transaction report, a great source of information is the queue transactions themselves. They have the business data used for the transaction as well as the status of each transaction, exception information, etc.

  

The Transaction Summary Report library handles all of these requirements.

· Waits for given other performer jobs to end

· Extracts all transactions from a queue since the given start date.

· Extracts exception details for failed transactions – Exception Type and Exception Reason

· Extracts the given columns of Specific Content data

· Extracts the given columns of Output Data

  

  

  

**Capturing Output Data**

  

Transactions have the ability to take additional data that may be relevant for analysis or reporting. This is accomplished by using the Set Transaction Status activity. As shown below in the RE Framework a collection of value pairs can be assigned to the “Output” property.

  

Warning: The Output collection can only be used for Successful transactions. For Exception transactions, the exception reporting information is already in place. If your code uses a Throw, include any needed reporting text there in the message.

  

The Output values are shown in the “Output Data” part of the transaction page in Orchestrator. See attached screenshots.

In the example below the column name is “TransactionOutput”. This is the string you’ll use in the string array argument called “OutputDataHeaders”. See the example below.

**Introduction**

  

Summary reporting for multiple performers is a challenge that has been addressed in multiple ways. This documentation and custom activity present a methodology for doing reporting that is less apparent to most solution architects. It is simple and reliable. It eliminates many of the pitfalls of other methods like file contention on Excel files and race conditions between performers.

  

**Overview**

  

At a high level, this methodology uses a single “Reporting” transaction that is added to the queue by the dispatcher. This ensures that only 1 performer will attempt to do the reporting. The transaction is set to “Low” priority so that it is always the last transaction pulled from the queue. The custom activity is then invoked to extract the transactions from the queue. It will extract exception information for failed transactions as well as 'Output Data' for successful ones.

  

**Coding**

  

The coding is simple, and I have provided screenshots below.

  

**Dispatcher**

  

After the normal transactions are added, use a separate Add Queue Item with the properties set as shown in the image below.  Optionally include a date time in this Reporting Transaction that will serve as the filter for the transactions pulled from the queue.

  

**Performer**

  

The IF shown below will direct normal transactions to the Process.xaml and the Reporting transaction to a Reporting workflow.

  

If you are using a unique Reference queue, you will want to add a date or DateTime to the Reference of your reporting Transaction. In that can you would use a .contains(“Reporting”) in the IF below instead.

  

The activity excludes all transactions from the report results that have “Reporting” in the Reference field.

  

**Summary Reporting**

  

For creating a summary transaction report, a great source of information is the queue transactions themselves. They have the business data used for the transaction as well as the status of each transaction, exception information, etc.

  

The Transaction Summary Report library handles all of these requirements.

· Waits for given other performer jobs to end

· Extracts all transactions from a queue since the given start date.

· Extracts exception details for failed transactions – Exception Type and Exception Reason

· Extracts the given columns of Specific Content data

· Extracts the given columns of Output Data

\* See attached Word document for full features list and details.

\*\* If you need a Windows Legacy version please submit a question to this listing or contact me directly.

  

  

  

**Capturing Output Data**

  

Transactions have the ability to take additional data that may be relevant for analysis or reporting. This is accomplished by using the Set Transaction Status activity. As shown below in the RE Framework a collection of value pairs can be assigned to the “Output” property.

  

Warning: The Output collection can only be used for Successful transactions. For Exception transactions, the exception reporting information is already in place. If your code uses a Throw, include any needed reporting text there in the message.

  

The Output values are shown in the “Output Data” part of the transaction page in Orchestrator. See attached screenshots.

In the example below the column name is “TransactionOutput”. This is the string you’ll use in the string array argument called “OutputDataHeaders”. See the example below.

**Introduction**

Summary reporting for multiple performers is a challenge that has been addressed in multiple ways. This documentation and custom activities present a methodology for doing reporting that is less apparent to most solution architects. It is simple and reliable. It eliminates many of the pitfalls of other methods like file contention on Excel files and race conditions between multiple performers.

  

**Overview**

At a high level, this methodology uses a single “Reporting” transaction that is added to the queue by the dispatcher. This ensures that only 1 performer will attempt to do the reporting. The transaction is set to “Low” priority so that it is always the last transaction pulled from the queue. The custom activity is then invoked from the Process Transaction state to extract the transactions from the queue. It will extract Exception information for failed transactions as well as 'Output Data' for successful ones. 

  

This activity optionally waits for the number of running processes with a given name to be one. This gives other performers time to complete the last few transactions before the reporting begins. Please see additional details below for the full list of features. Demo projects have also been provided.

  

**Coding The Dispatcher**

  

**Transactions Remaining Activity**

There are scenarios where the dispatcher is scheduled to run frequently. If you want to report on each batch of transactions separately you may want to make sure that the reporting transaction is processed before the next batch of transactions is added to the queue.

  

An activity called Transactions Remaining is provided to be used in scenarios where a dispatcher may be scheduled so that it could add a second batch of transactions into the queue before the previous batch is complete. Using the activity below, your Dispatcher can easily determine if there are still New or In Progress transactions still in the Queue and skip creating more transactions if needed.

  

Please note the “Ignore In Progress Transactions Older Than Minutes” property. If a performer faults it is possible to leave the transaction with the state, “In Progress” even though it is really abandoned. For this reason, you are able to ignore any transactions that started more than X minutes ago.

  

**Create Reporting Transaction Activity**

After the normal transactions are added, use this activity to easily add a Low priority Reporting Transaction to your queue. The Reference property must contain the word “Reporting”, but it can also have other text as needed. The BatchStartDateTime property will be used by the Performer to filter the transactions. So the time needs to be before the Create time of the transactions added to the queue.

  

**Coding the Performer**

  

**CreateSummaryReport activity**

This activity is used to extract the data from the queue and has many options. It is best to implement this activity in the Process Transaction state of your Performer process. The IF shown below will direct normal transactions to the normal transaction logic and the Reporting transaction to a Reporting workflow.

  

If you are using a unique Reference queue, you will want to add a date or datetime to the Reference of your reporting Transaction. This is the reason for using .contains(“Reporting”) in the IF below.

  

The activity excludes all transactions from the report results that contain “Reporting” in the Reference value.

This activity is used for creating a transaction report for transactions in a queue. It is very useful when using multiple performers.

**Introduction**

Summary reporting for multiple performers is a challenge that has been addressed in multiple ways. This documentation and custom activities present a methodology for doing reporting that is less apparent to most solution architects. It is simple and reliable. It eliminates many of the pitfalls of other methods like file contention on Excel files and race conditions between multiple performers.

  

**Overview**

At a high level, this methodology uses a single “Reporting” transaction that is added to the queue by the dispatcher. This ensures that only 1 performer will attempt to do the reporting. The transaction is set to “Low” priority so that it is always the last transaction pulled from the queue. The custom activity is then invoked from the Process Transaction state to extract the transactions from the queue. It will extract Exception information for failed transactions as well as 'Output Data' for successful ones. 

  

This activity optionally waits for the number of running processes with a given name to be one. This gives other performers time to complete the last few transactions before the reporting begins. Please see additional details below for the full list of features. Demo projects have also been provided.

  

**Get Queue Items**

  

**Get Queue Items Export Activity**

This activity can be used independently of the Reporting activities.  It is generally a replacement for the UiPath Get Queue Items activity.  It uses the recommended Export APIs to get the data.  This method is not affected by the new API limits or the removal of the Specific Content and Output Data from other APIs.

  

**Get Queue Items Export And Parse Activity**

This activity can be used independently of the Reporting activities.  It is a more advanced replacement for the UiPath Get Queue Items activity.  It uses the recommended Export APIs to get the data.  Compared to the activity above, this one will parse the Specific Content and Output Date values into separate datatable columns for ease of use.

  

**Coding The Dispatcher**

  

**Transactions Remaining Activity**

There are scenarios where the dispatcher is scheduled to run frequently. If you want to report on each batch of transactions separately you may want to make sure that the reporting transaction is processed before the next batch of transactions is added to the queue.

  

An activity called Transactions Remaining is provided to be used in scenarios where a dispatcher may be scheduled so that it could add a second batch of transactions into the queue before the previous batch is complete. Using the activity below, your Dispatcher can easily determine if there are still New or In Progress transactions still in the Queue and skip creating more transactions if needed.

  

Please note the “Ignore In Progress Transactions Older Than Minutes” property. If a performer faults it is possible to leave the transaction with the state, “In Progress” even though it is really abandoned. For this reason, you are able to ignore any transactions that started more than X minutes ago.

  

**Create Reporting Transaction Activity**

After the normal transactions are added, use this activity to easily add a Low priority Reporting Transaction to your queue. The Reference property must contain the word “Reporting”, but it can also have other text as needed. The BatchStartDateTime property will be used by the Performer to filter the transactions. So the time needs to be before the Create time of the transactions added to the queue.

  

**Coding the Performer**

  

**CreateSummaryReport activity**

This activity is used to extract the data from the queue and has many options. It is best to implement this activity in the Process Transaction state of your Performer process. The IF shown below will direct normal transactions to the normal transaction logic and the Reporting transaction to a Reporting workflow.

  

If you are using a unique Reference queue, you will want to add a date or datetime to the Reference of your reporting Transaction. This is the reason for using .contains(“Reporting”) in the IF below.

  

The activity excludes all transactions from the report results that contain “Reporting” in the Reference value.

Problem Statement :

In UiPath Orchestrator, inside the tenant - there is no provision to auto allocate the runtime licenses to bot machines (when required).

  

Solution :

License Allocation bot will auto allocate the “UiPath runtime licenses” to pending job’s machine. Basically, this bot will check for any pending jobs in Orchestrator every 1min, consider if the bot is able to find 1 pending job, then it will allocate 1 runtime license to the pending job’s (bot) machine from the License pool machine. On end of this bot process - de-allocation process will pick the unused runtime licenses from bot machines and move it to pool machine.

*   It is a continue background process, where we can run it either as attended/ unattended bot.
*   You need to pick one machine as License pool machine from your tenant and set the machine name while creating the process.

Ability to auto allocate the UiPath runtime licenses.

RPA Content Manager

Overview of UiPath Pipelines Activities Package
-----------------------------------------------

The UiPath Pipelines Activities package empowers users to create automations dedicated to tasks such as project building, cloning, testing, and publication of automation projects. When integrated with Automation Ops - Pipelines, this package facilitates the establishment of a robust continuous integration/continuous delivery (CI/CD) system. This system effectively oversees the management of code for automation projects, fostering predictability and scalability in the development process.

Activities in the UiPath Pipelines Package
------------------------------------------

The following activities are available in the UiPath Pipelines Activities package:

*   [Analyze Activity](https://docs.uipath.com/activities/other/latest/workflow/analyze-activity) - Analyzes a project.
*   [Build Activity](https://docs.uipath.com/activities/other/latest/workflow/build-activity) - Builds the project into a .nupkg file.
*   [Clone Activity](https://docs.uipath.com/activities/other/latest/workflow/clone-activity) - Clones a repository to be used in the project.
*   [Download Package Activity](https://docs.uipath.com/activities/other/latest/workflow/download-package-activity) - Downloads a package from Orchestrator locally.
*   [Publish Package](https://docs.uipath.com/activities/other/latest/workflow/publish-package-activity) - Publishes the project package in Orchestrator.
*   [Stage Activity](https://docs.uipath.com/activities/other/latest/workflow/stage-activity) - Is the main activity that represents a step in the pipeline.
*   [Update Process Activity](https://docs.uipath.com/activities/other/latest/workflow/update-process-activity) - Updates a specific process in Orchestrator.
*   [Run Tests Activity](https://docs.uipath.com/activities/other/latest/workflow/run-tests-activity) - Runs tests marked as publishable against the workflow as part of the pipeline.

  

**IMPORTANT:** This package version requires Studio 21.10.7 or higher. On lower versions some functionality may be missing, or unexpected behaviours may occur.

The UiPath Pipelines Activities package allows you to create automations that build, clone, test, or publish your automation projects.

RPA Developer

This activity facilitates the recording of process executions by a Robot, utilizing the multimedia framework available at https://ffmpeg.org/. You can download the framework from https://github.com/BtbN/FFmpeg-Builds/releases.

Primary applications of this activity include:

- Assisting in troubleshooting faulty processes.
- Facilitating the sharing of video recordings with stakeholders for obtaining UAT sign-off.

This activity will assist in capturing the video of running process.

Some of the activities contained in this package are:

*   Test Server Connection
*   Add User to Role
*   Add User to Group
*   Create User
*   Delete User
*   Enable User
*   Get User Status
*   Remove User from Group
*   Unlock User
*   Update User Password

UiPath Solution Accelerators Active Directory reusables is a package that bundles common activities used in Solution Accelerators for Active Directory Automation.

	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.		3095
	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		415
	Enquero - Business Day Calculator for Scheduling This activity returns the date of the nth business day of any month based on Orchestrator calendar.		176
	Transaction Summary Report Activity This activity is used for creating a transaction report for transactions in a queue. It is very useful when using multiple performers.		<100
	Auto Allocation for UiPath Runtime Licenses Ability to auto allocate the UiPath runtime licenses.		<100
	UiPath Pipelines Activities The UiPath Pipelines Activities package allows you to create automations that build, clone, test, or publish your automation projects.		<100
	Screen Recording Activities This activity will assist in capturing the video of running process.		<100
	Solution Accelerators Active Directory Reusables UiPath Solution Accelerators Active Directory reusables is a package that bundles common activities used in Solution Accelerators for Active Directory Automation.		<100

UiPath Orchestrator - Your Command Center for Efficiency

Explore Studio Desktop listings

Explore Collections to get inspired

Similar apps

Productivity

Productivity

Productivity

Productivity