サインイン
はじめてのオートメーションをわずか数分で作成できます。Studio Web を試す →
Orchestrator for Node-RED
作成者: Internal Labs
4
コネクタ
306
Hi Dean,
I am trying to connect our Orch engine by using request but getting error which is Could not connect to CRP/dialog. Please check your credentials. I am sure that my credentials are ok.
Hi Baris. A few questions.
Are you using platform.uipath.com? If so, there are changes being made to the way the Cloud platform authenticates and connectors like this one are no longer supported. When the changes are completed in the next few months, I will issue an update.
If not using platform.uipath.com, are you providing all three credentials--tenant, username, and password?
If you're using a private Orchestrator, does it have a self-signed certificate (i.e. when you go to Orchestrator, is there a lock symbol up in the corner or a red, insecure icon? If the latter, you need to check the self-signed cert box in Node-RED.
The get QueueItems with Action Get all does't take into consideration filter parameters. I tried with QueueDefinitionId and/or Status and either way the response contains all the QueueItems from All the Queue lists. How should I form the query parameters?
Hi Cristian. Form the query parameters just as you would in an API call. For example:
Key: $filter
Value: QueueDefinitionId eq 'x'
Hi Dean, just wondering if there is an option to add an organization unit ID in header of request? Thanks, keep up the good work :)
EDIT: Org Units/Folders are now fully supported.
Original Reply:
Hi Nikola. Since Org Units are still experimental, I haven't included them in an obvious way. That said, you can use them in version 1.0.9 by adding the X-UIPATH-OrganizationUnitId parameter to any request.
Here's a sample flow that grabs the ID of the Org Unit, saves it as a flow variable, and then uses it to get all Assets from Orchestrator. You can import this flow from the hamburger menu in the top right corner. Just add your own login credentials and you'll be good to go.
