This article will explain how to add a flow which will allow you to retrieve the release information required to trigger a job from a process.  

 

ui_path_Logo_SMALL_rgb_Orange_digital_147x50.png

After setting up your authentication, we must also fetch the information regarding which process you wish to start. We do this using the Get Releases node. 

Add Get Releases node to flow

In your flow below your Authentication node click on + to open the mask to add nodes. Navigate to Extensions in the mask and then the UiPath symbol to see all Nodes associated with the UiPath extension. Choose the Get Releases node from the list and it will be added to the flow. 

 

mceclip0.png

Figure 1: Add a Get Releases node to the flow

 

Finding and Adding Information

Clicking on the node will open up the edit node function where you can enter the credentials for your node. 

 

mceclip1.png

Figure 2: Edit node fields for Get Releases node

 

Ideally you should already have set up the Orchestrator Instance Information when setting up the authentication.  The template you already added should appear when you click on the arrow for the drop down menu. 

mceclip2.png

Figure 3: Window for adding account and tenant information

 

You can find the information in the same place you found your Client ID and User Key

 

mceclip3.png

Figure 4: Completed information in the Get Releases Edit Node mask

 

The Access Token is a dynamic value created by when you run the Authentication node. Simply put the Cognigy code for the field where you stored the results here. 

Results Storage

After adding your entering the information to retrieve your release data you need to decide whether to save the data you will receive from UiPath in the Input or Context. This data data will be needed at a later point by other nodes (for example the Start a specific job node). 

Where to find the release information after retrieving it

If you were to run the branch of your flow with this node the information for all of your processes should show up as JSON in the context information. 

mceclip5.png

Figure 5: Releases Information in context

 

Depending on how many processes and folders you have set up in UiPath Orchestrator might find multiple releases. Please make a not of which process in the list is the one you wish to use. This will be relevant in the next step when you add the Start a specific job node. 

Please keep in mind that the order of your process might change if you delete or move any of your processes in UiPath. This will need to be changed in the Cognigy flow later.

Get Releases By Name Node

In addition to the Get Releases Node there is also a Get Releases By Name Node. This node functions exactly like the Get Releases Node but with an addition field with which you can also filter your results by the name of the process. This makes it easier to find and trigger specific processes. 

mceclip0.png

Figure 6: Add a Get Releases By Name node to the flow

 

mceclip1.png

Figure 7: Field to filter releases/processes by name

 

After setting up both the Authentication and Get Releases nodes you can either add a node to start a specific job or add a node to add a transaction to a process. 


Comments

0 comments

Please sign in to leave a comment.

Was this article helpful?
0 out of 0 found this helpful