Book Image

SAP Intelligent RPA for Developers

By : Vishwas Madhuvarshi, Vijaya Kumar Ganugula
Book Image

SAP Intelligent RPA for Developers

By: Vishwas Madhuvarshi, Vijaya Kumar Ganugula

Overview of this book

SAP Intelligent Robotic Process Automation (RPA) enables businesses to automate repetitive work and integrate automation capabilities across SAP and non-SAP systems. This book provides end-to-end coverage of business process automation using SAP Intelligent RPA and shows how to build multiple SAP Intelligent RPA projects from start to finish. Some of these projects may build upon the work done in previous chapters to showcase the Agile development process in SAP Intelligent RPA. As you progress, you'll cover the SAP Intelligent RPA factory, Desktop Studio, Cloud Studio, and the Bot store. You'll also learn about the building blocks of the SAP Intelligent RPA solution and creating bots from initial application declaration to workflow design and deployment, along with making bots run in attended and unattended modes. You'll also learn about SAP Process Automation, the new SAP service that is going to replace the SAP Intelligent RPA service soon. Finally, we will discuss the migration path for your SAP Intelligent RPA projects to SAP Process Automation and showcase that the RPA development remains similar in both services. By the end of this RPA book, you’ll be able to create and manage complex bots that are capable of interacting with SAP and non-SAP systems.
Table of Contents (39 chapters)
Free Chapter
2
Part 1: Introduction to SAP Intelligent Robotic Process Automation
9
Part 2: Installing and Setting Up SAP Intelligent RPA
12
Part 3: Developing Bots with Desktop Studio
21
Part 4: Generating and Updating the JavaScript Code
26
Part 5: Building and Running Projects
30
Part 6: Orchestrating Workflows with Cloud Studio
34
Part 7: SAP Intelligent RPA Store, Roadmap, and SAP BTP Automation Services

Chapter 22:

  1. Ensure that the agent hostname specified in the environment is correct. It generally takes a couple of minutes to download the package to the agent's machine. If it is not available even after a few minutes, restart the agent.
  2. The triggers are created for the package, and updating the package version in the environment will be sufficient to change the package in the agent's machine. Once created, the trigger need not be updated for the package version.
  3. Check the date range specified while creating the trigger. The package is not available after the date range specified. You can update the trigger to specify the new date range.