What is Robotic automation with PEGA
PEGA is a leader for customer loyalty and operational excellence in cloud computing. The most recognized and profitable brands in the world rely on AI-enabled software. This is to optimize every consumer interaction on any channel while maintaining its brand promises.
Robotic automations can be used to automate the repetitive routine tasks in a workflow. PEGA robotics is introducing the ability to automate activities using existing applications' user interface. Through automating user behavior it can help speed up the manual activities.
Automations are being produced in Robotic Studio PEGA. The latest available update is 8.0, and can be downloaded from PDN. The minimum Running Automation specifications are PRPC 7.2.1 with PEGA HFIX-29471 or PRPC 7.2.2.
Types of robotic automation:
Two types of PEGA robotic automations exist:
- Robotic Desktop Automation (RDA)
- Robotic Process Automation (RPA)
Desktop Automation
Desktop automations are used to provide users with a seamless desktop experience by integrating and automating desktop (or web applications) with PEGA 7 applications. Web or web applications can be launched from flow behavior, and data between workflow and desktop applications can be transferred back and forth.
To get in depth knowledge pega you can enrol for free live demo pega online training
Desktop automations can help to reduce the repetitive work needed for copying and duplicating data through multiple applications. This can also reduce the amount of time a CRM agent has to spend on the phone with a client, and can also minimize data entry errors that can occur when entering multiple times the same data.
Process Automation
Process Automation PEGA cycles are used to automate the high volume repetitive back-end jobs. Case assignments are routed to a robotic queue from which a robotic automation VM can pick them up to execute the automations.
The job is similar to an agent but, instead of the requestor handling the task, the processing is performed through an automation. In the work basket instance a new dropdown 'form' was added to define a queue for robotic automation work. When Robotic style is selected from the dropdown, two additional fields will be displayed.
Automation Studio
PEGA Automation Studio makes use of Microsoft Visual Studio as its platform for development. Users on Microsoft Visual Studio platform will have an idea. It also uses standard Diagnostic and Debugging software from Visual Studio to check the unified solution.
Total queue length:
This value will be used to determine the maximum number of assignments that will be in the queue at a specified time.
Total execution time for automation:
This value is used to determine the maximum amount of time that the VM is supposed to take to run the automation.
You can handle Automation VM's in PEGA Robotic Automation Console. Robotic workbaskets turn red when the number of tasks reaches the maximum length of queue or the execution time of the automation. A sample application packages the automation console, and can be downloaded from the PDN page.
Robotic Studio Setup and Configuration
There are two setup options available:
- Run Time Installation
- PEGA Robotic Studio Installation
- Run Time Installation
The runtime software allows users to run automations on a desktop. Upon launching the runtime application, you can load the automation project and right-click the run time icon in the task bar. During client deployment, the RDA checkbox needs to be checked to allow the REST service (API) to handle PEGA 7 applications for automation requests.
Robotic Studio Installation
On top of Visual Studio, PEGA Robotic Studio is installed. Robotic Studio is used to construct automation processes. The files and installation instructions can be found at PEGA Academy in the PEGA Robotic Automation Architect Essentials (8.0).The course also includes a sample program and step-by-step guidance on how to produce an automation. Automations can also be invoked by running the debugger in a robotic studio from a PEGA program.
Configuring robotic studio
All runtime and Robotic Studio have configuration files that must be modified with the base URL of PEGA server. Cfg files are copied to the temp folder at runtime under C:/user / AppData / Roaming / OpenSpan. - time the Config files are changed, the files need to be modified or removed from this folder to pick up the latest Config changes.