Now Available: RPA Central 2.8.0 and Nintex Bot 17.8.0

michta
Nintex RPA Expert
Nintex RPA Expert
2 4 267

Hi, Everyone,
Today we released the latest versions of both Central and Bot. I encourage you to upgrade Central and Bot today! You will also notice that we have released an updated version of the Chrome extension which should upgrade automatically in your browser.
We have added two new actions – Open Chrome and Open Edge – that should make it more reliable to open these browsers.
You will see a ParseJSON function in Bot as well, making it easier to work with objects returned from REST calls.
If you are using Open Data, there’s a new option to execute one or all records, so check that Help topic out if you are using Open Data actions.
If you are in the banking industry and use Fiserv, you are most likely moving from IE-based automations to Google Chrome and perhaps custom applications. We have made some enhancements for you to be more successful with both, particularly Fiserv Navigator. We have also made it easy to create copies of your IE actions so that they target Chrome or Edge. Right-click any IE action to see the conversion options; read our Help topic about it here. Be sure to upgrade to this version of Bot as soon as possible if you are using Fiserv.
We have upgraded our email functionality with the latest MailKit libraries, so sending & receiving email as well as parsing your inbox should be more reliable now.
In Central, we have updated the Instances page to load only a subset of the latest instances and added automatic paging to the page. As you scroll more instances are returned. You can control the page size (default is 50) by editing the SharedServiceSettings file located at \Program Files (x86)\Nintex\RPACentral\RPACentral.
I am also happy to tell you that you can now automate Central using the API. Just add /Swagger to your RPA Central URL and you will see the full API. We have documented the most interesting endpoints in our Help topic, which also includes four Postman collections to get you started.

Lastly, if you are using K2 Five, you can work with the RPA Central API using custom Swagger files. Read more about that in the community article.
I also wanted to call your attention to the blog from yesterday regarding the Kryon acquisition we made and what that means to you. Please read more about that here.

Finally, here's a link so that you can read the release notes.

Thanks,
Mike
Product Manager - Nintex RPA and AssureSign

4 Comments
Jrissmiller
Novice

The bot improvements such as run all records from an Open Data action and send Creds to an emulator may be big for fully automated bots. Instance limits in RPAC is a good addition!

 

I really need Participants to be able to run botflows outside of RPAC similar to Foxtrot v15.  In our environment these users are randomly assigned a VM from a pool of 6, and some have access to the same botflow. Running a botflow from RPAC can potentially run on the other user's VM. It's requiring overhead on my part to limit issues.

michta
Nintex RPA Expert
Nintex RPA Expert

Hi,

Thanks for the feedback. One thing you could do is call the "/api/jobbotflows/{botflowId}/run-on-bot/{botId}" endpoint to force the botflow instance to a particular bot. Checkout the Swagger page in 2.8 for more information, but here's a screenshot starting botflow 1 on bot 1.

RunBotflowOnBot.png

Jrissmiller
Novice

Thank you Mike!

 

The API is interesting and I will definitely review it at some point.  The "Run all Records" on Data Open works and this small addition will allow me to upgrade from v15 to v17 in 2 weeks.

michta
Nintex RPA Expert
Nintex RPA Expert

Glad to hear you'll be able to upgrade to v17 now!

 

FYI to use the CURL command listed on the Swagger page in a PowerShell script, you need to use curl.exe like so to start a botflow instance with botflow ID 1:

 

curl.exe -X 'POST' 'https://localhost/api/jobbotflows/1/run' -H 'accept: application/json' -H 'Content-Type: application/json-patch+json' -d '{}' --ntlm -u :

 

To run a botflow on a particular bot, use this command (botflow ID 1 & bot ID 1):
curl.exe -X 'POST' 'https://localhost/api/jobbotflows/1/run-on-bot/1' -H 'accept: application/json' -H 'Content-Type: application/json-patch+json' -d '{}' --ntlm -u :

 

The --ntlm adds the integrated Windows auth and the colon says send the currently logged-in user.

 

HTH,

Mike