Imagine you're tasked with creating an automation for customer service representatives to use throughout your company at the start of the work day. You need to present the user with a login banner, launch the standard applications, and authenticate. Then you'll present another message to the user that the start-day process is complete.
In this solution, you'll use applications, such as email and a Customer Service Management program. You'll use standard Windows forms to communicate and interact with your users. And you'll use an automation to control the workflow, timing, and details of the process. The automation launches each application, supplies authentication, and arranges the applications on the user's desktop. All of these elements are contained in a Robot Studio project.
The following figure shows the basic elements of a Robot Studio solution:
A solution is the overall process you build in Robot Studio, comprised of applications, automations, and Windows forms. Solutions are stored in containers called projects.
An automation is the robotic process you create in Pega Robot Studio to perform tasks and enact workflows. Automations can be either attended or unattended.
Attended automations require manual supervision. For example, an automation might launch and log into all the applications a user needs to start their day. During processing, the automation might require the user to accept a security banner and enter a single set of credentials.
Unattended automations can run in the background on a server, with no supervision. For example, when an automobile insurance claim is submitted, an automation can analyze the submitted information, look up and verify policy holder information, and then update web, cloud, or on-premise applications with the new information. Unattended automations optimize system resources and reduce peak loads, often by queuing updates for off-hours.