How to build a Bot using SAP Intelligent Robotic Process Automation(IRPA)
Here I am going to explain about how to build a bot using “SAP IRPA” in sap cloud platform.
Subscribe to SAP Intelligent RPA service in SAP cloud platform(SCP)
For subscribing the SAP Intelligent Robotic Process Automation service we need to login to your SCP trail account.
Click on trial to go to subaccount.
Go to subscriptions and here we need to subscribe to the SAP Intelligent RPA service as shown in below image.
Once IRPA service subscription is done we need to create a new role collection of the required roles and assign the same. For that we have to go role collection and click on the new role collection button to create your role.
Enter our role name and click on save(Role Name: IRPAOfficer) to created our role.
Click on the created Role(IRPAOfficer)
Now click on the add role button to get the dialog, fill all the mandatory fields and save to add the role. Now we have successfully created one Role.
After creation of the role we need to assign the newly created role collection under the trust configuration. For that we have to go Trust Configuration and click on the “SAPID service” as mentioned in the below image.
Enter your SCP email and click on the assign role collection button to assign the role to your trail account as shown in below message.
Create a Service Key:
For accessing the “SAP IRPA” we need to generate the service key by following the below mentioned steps.
- Go to trail.
- Go to space.
- Go to ‘irpa-service-trial’(IRPA API’s) in Service marketplace.
IRPA service instance Creation.
- Go to Instance and click on new Instance button for creating a new instance.
Once we open the created instance dialog there is no need to specify any optional parameters. Enter your Instance name and click on finish button to create your instance as mentioned in the below image.
Click on the created instance name to generate the service key as shown in below image.
On-premise Components Setup:
Before installing the SAP Intelligent Robotic Process Automation on-premise components we need to install the following softwares in our system.
- Microsoft Internet Explorer 11
- NET framework 4.6.2 version.
- Microsoft Visual C++ 2013 Redistributable Package x86 (only for the Desktop Studio, not required for Agent) and]
- KDiff3 version.
Go to on below links for downloading the SAP IRPA and KDiff3.
Desktop Agent Tenant Registration
Once you’ve completed the installation steps of the SAP Intelligent Robotic Process Automation setup, you need to register a tenant so that you can execute the Desktop Agent.
When the Desktop Agent Tenant Registration window pops up, enter:
- The name of your tenant (ex:SAP RPA)
- The SAP Intelligent RPA Factory tenant URL you want to connect to (ex:https://PIdtrail.app.irpa-trial.cfapps.us10.hana.ondemand.com)
Click on save toadd a tenant to your trail like as shown in below image.
Now you have successfully installed the on-premise components of SAP Intelligent Robotic Process Automation. You must perform a few additional steps to finalize the installation if you want to use the SAP Intelligent Robotic Process Automation Desktop Studio.
This check-up is a quick procedure for validating that the installation is completed or not.
Open the Desktop Studio and go to settings(File>Settings)
Go to Workflow tab in desktop settings dialog and here we can configure your kdiff and merge tool as shown like below image.
Sample Project Creation in Desktop Studio:
- Create a new project using File>New Project.
- Enter a project name (ex: RPA demo), title, client name and click on save to successfully created a project.
Work flow creation for created project:
- Go to new new workflow option.
- Enter your workflow name and click on save to create the workflow shown like below image.
Here I am adding the MessageBox control to my workflow for which we need to go Activities tab and select MessageBox control in popup list shown like below.
By drag and drop the control we can add that control to our workflow.
After dropping the control we need to establish the connectivity between the workflow start to MessageBox control.
Now double click on the MessageBox control and fill all the required parameters and save the workflow like below.
My workflow is done. Now we need to export the project(File>Export Project)
We can see the zip file like below.
Login to our IRPA Factory:
- Go to SAP IRPA service.
- Enter our SCP credentials to Log on our IRPA Factory as shown in below.
Hierarchy and Environment Creation:
Go to Management tab in IRPA Factory here we have two tabs which are as below
G o to Hierarchies tab and click on the New Hierarchy button to get a pop up, enter the hierarchy name and click on save to created your hierarchy.
G o to Environment tab and click on the New Environment button to get a pop up, enter the environment name, Hierarchy,Hierarchy Node and click on save to created your Environment.
Now we need to import our project which we need exported from our desktop studio.
- Go to packages tab and click on import button to get a browse file option for importing file.
After importing we need to deploy the project by clicking on the deploy button as shown in below.
Once deployment is done now we can to find our app in deployments.
Now our app is ready to schedule and it can be scheduled by clicking on the Scheduled button shown like below.
- Here we can set date and time to create our Schedule.
After completing our Schedule go to deployments tab and click on the Run now option, Now our app is ready to run.
In Monitoring tab we can check whether desktop Agent is in Ready state or not as agent starts to trigger in ready state only. Once the Schedule time is reached desktop agent is triggered automatically.
Now we can Monitoring the Job status in Monitoring tab. Initially it is in Running status once its reached to scheduled period a MessageBox (which we have integrated in our workflow) will be triggered.
Click on OK button in MessageBox to see the changed job status(Running to Successful),as shown like below image.
Note: We can set the scheduled time to 5 minutes also so that agent is triggered for every 5 min which changes the job status.