# Process Steps Sequence

1. The business process automation script developer uses the desktop software Sherpa Designer and the local Sherpa Robot to create and debug the automation script. The finished automation scripts are manually transferred to the users' or robots' workstations by copying the robot's configuration file or using the remote publication feature to publish a new version of the script from Sherpa Designer to Sherpa Orchestrator.
2. The server component Sherpa Orchestrator maintains communication with the robots running on client machines, stores robot configurations and script versions, shared global variables and credentials, logs and screenshots of robot operations, Orchestrator audit logs, users, roles, and tenants of the Orchestrator itself, licenses for all platform components, and script execution statistics.
3. Users and administrators of Sherpa Orchestrator access resources, settings, and statistics through the Orchestrator web application, available via a web browser. Sherpa Orchestrator includes the Nginx web server, PHP interpreter, and a relational database (default is MariaDB, option - Postgre).
4. Local users launch the Sherpa Attended Robot to execute locally stored scripts as needed. During the execution of the script, the Sherpa Attended Robot can send the Orchestrator the current status, tasks, logs, values of global variables and credentials, or receive tasks, values of global variables, and credentials from it.
5. On a schedule, via an API call, a robot command, or another supported trigger, Sherpa Orchestrator instructs the Sherpa Coordinator Service of the corresponding terminal server to create an RDP connection to the local or remote account designated for the unattended robot, with multiple such accounts being hosted and actively used on a single terminal server. Access to the unattended robot account is performed using the login and password provided by the Orchestrator. After logging into the account, the corresponding instance of the Sherpa Unattended Robot is launched, connects to the Orchestrator, receives the task to execute the script, and the script itself, stored in the Orchestrator. During the execution of the script, the Sherpa Unattended Robot can send the Orchestrator the current status, tasks, logs, values of global variables and credentials, or receive tasks, values of global variables, and credentials from it, as well as commands for "soft" or "hard" termination of the script. After completing the script execution, the Sherpa Unattended Robot logs off from its account.