Uipath Marketplace
MarketplaceListingsSolutionAutomatically Create Orchestrator Assets

Create your first automation in just a few minutes.Try Studio Web

Automatically Create Orchestrator Assets

Automatically Create Orchestrator Assets

by Manish Jagtap

StarStarStarStarStarStar

1

Solution

Downloads

104

back button
back button
carouselImage0
next button
next button

Summary

Summary

This solution aims to automate the process of manual Asset creation using Orchestrator UI. Create the Assets in Modern or Classic folders directly based on the Config file used for the project.

Overview

Overview

The assets are created in Orchestrator based on the assets present in the Config file. The executable requires the below parameters as inputs:

  1. tenantname: Name of the tenant. This value is available in the API access  section of Orchestrator.
  2. clientid:  Client ID. This value is available in the API access section of Orchestrator.
  3. userkey: User key. This value is available in the API access section of Orchestrator.
  4. accountlogicalname: Logical name of the account. This value is available in the API access section of Orchestrator.
  5. configfilepath: Absolute file path of the Config file. For details of the Config file format, please reffer to the attached Word document. Only Text, Bool and Integer asset types are currently supported.
  6. foldername: Name of the folder in which the assets must be created. Supports both modern and classic folders. In case assets have to be created in a subfolder, the absolute path of the folder has to be provided. Eg: “PROD/HR/Onboarding”

The executable can be run from Command Prompt or Powershell.

Note: The solution will create the assets with global scope and empty values. The values of the Assets must be updated using the Orchestrator UI.

Features

Features

By using this solution, the creation of the Assets in Orchestrator can be automated. This solution can be integrated in CI/CD pipelines, so that the assets are automatically created once the build has passed successfully. This will also eliminate the chances of spelling mismatch between the Asset names specified in the Config file and the Orchestrator.

Additional Information

Additional Information

Dependencies

No external dependencies. The executable must be called from Command Prompt or PowerShell.

Code Language

C#, Visual Basic

Publisher

Manish Jagtap

Visit publisher's page

License & Privacy

MIT

Privacy Terms

Technical

Version

1.0.0

Updated

Jan 3, 2021

Works with

Studio: 20.10 - 22.10

Certification

Silver Certified

Support

UiPath Community Support

Resources

Similar Listings