Robotic Process Automation (RPA)

 View Only

NEW - Lab Guide for using IBM RPA with IBM BAW

By Jukka Juselius posted Wed July 06, 2022 03:51 PM

  

Hello IBM RPA practitioners!

It's been a while since I released the latest version of my community toolkit for BAW (Business Automation Workflow) that allows you to integrate IBM RPA with BAW process workflows. I promised already back then that I'll write a lab exercise and detailed instructions, but have not been able to finish up that work...UNTIL NOW!


I'm proud to present new advanced IBM RPA lab that shows you how to test and run IBM RPA together with IBM BAW using our existing RPA image in IBM Technology Zone (ITZ). Everything - including getting the environment from ITZ - is covered in the lab guide that you can download from HERE.


All comments are welcome! Thanks!


*** EDIT July 8 2022 ****

The IBM TechZone environment is now updated to fully support the lab!

3 comments
129 views

Permalink

Comments

Fri August 05, 2022 04:47 AM

Thanks for this lab.  Feedback:

  • After step 18 where you set the roles, you should tell the user to refresh the browser so that it picks up the new roles. Otherwise, they will get stuck later in the lab where they can't find the Workflows tab. 
  • Step 36  I would suggest it is best practice to always set the process variable to one of your input variables (input_text in your case).  This is so that you can track the bot invocations in the tenant log.
  • Step 51.  I had to bounce the server to get the certificate to work.
  • Section 3.  I found this section too verbose.  Why can't I import a working flow and then learn about the toolkit?  That's the only bit I'm interested in.  I don't want to create an entirely new flow.

Fri July 08, 2022 04:41 AM

The IBM TechZone environment to run the lab with is now updated! Thanks for your patience!

Thu July 07, 2022 09:42 AM

Just learned that the IBM Techzone Environment template was not yet updated to fully support this lab guide. BUT, it should be updated later today (2022-07-07) or tomorrow. Sorry for any inconveniences.