Skip to main content

Desktop Automation Using Smart Buddies

Overview

This document outlines the essential requirements and considerations for configuring and supporting Desktop Automation using Smart Buddies. The automation is executed within Windows user sessions, and there are specific rules and best practices to ensure successful and reliable execution.

Key Points for Desktop Automation Setup

These key points outline the necessary configuration and operational practices to ensure the successful execution of Desktop Automation using Smart Buddies. Adhering to these guidelines will help minimize potential errors and interruptions during automation processes, providing smoother and more efficient performance. Below are the detailed requirements:

Single Instance Execution

  • Each Smart Buddy can only be associated with a single Windows User Session and can execute only one instance of Desktop Automation at a time.

Dedicated Windows User Session

  • If multiple desktop automations must be executed concurrently, each should be executed by a separate Smart Buddy. Each Smart Buddy executing desktop automation should have a dedicated Windows user session to run automation.    

Active and Unlocked Sessions

  • The session must remain actively connected to a desktop/screen/monitor, and the user interface must be visible and not minimized or locked during the automation process. If the session becomes locked or minimized, the automation will fail.

No Concurrent Jobs

  • Do not assign additional jobs to the Smart Buddy while executing desktop automation. Running multiple processes on the same Smart Buddy can cause performance degradation or automation failure.

Avoid Interaction with System Resources

  • During the execution of desktop automation, manual or programmatic interactions with the system resources (e.g., keyboard, mouse, or screen) should be strictly avoided.
  • Any interference, whether manual (e.g., user inputs) or programmatic (e.g., software triggering mouse/keyboard events), may cause the automation to fail or behave unexpectedly.

Recommendations

  • Ensure each Smart Buddy has a dedicated automation environment that is not used for other tasks.
  • Monitor the user sessions to ensure they remain active and unlocked during automation runs.
  • Avoid using the same resources (e.g., input devices) in a way that might interfere with the Smart Buddy's operations.
  • Consider using remote desktop session managers or other tools to monitor session activity and ensure compliance with the requirements.

Conclusion

The guidelines must be strictly followed for reliable desktop automation using Smart Buddies. Any deviations, such as locked sessions or concurrent resource usage, will likely result in automation failures. Ensuring an uninterrupted and dedicated session for each Smart Buddy is essential for the smooth execution of automation.