The assets are created in Orchestrator based on the assets present in the Config file. The executable requires the below parameters as inputs:
tenantname: Name of the tenant. This value is available in the API access section of Orchestrator.
clientid: Client ID. This value is available in the API access section of Orchestrator.
userkey: User key. This value is available in the API access section of Orchestrator.
accountlogicalname: Logical name of the account. This value is available in the API access section of Orchestrator.
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.
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.