MarketplaceListingsSolutionAutomatically Create Orchestrator Assets

Automatically Create Orchestrator Assets

Bronze Certified

Solution

0 reviews

4

Automatically Create Orchestrator Assets

Bronze Certified

Solution

0 reviews

4


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.

carouselImage0

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.

Benefits


Published: 2021-01-19T12:43:58+00:00 | Updated: 2021-01-19T12:43:58+00:00

Manish Jagtap
RPA Developer

License

MIT


Code Language

C#, Visual Basic


Tags

assets
ci-cd
cicd
CommandPrompt
config
Create Assets
orchestrator
Orchestrator Assets
powershell

Compatibility

Compatible with UiPath Cloud Orchestrator only. Authorization Compatibility not tested with On-Prem Orchestrators. No dependency on Studio or Robot.


Dependencies

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


Documentation


Similar Listings