OpCon RPA 1.2.0 removes the need for a signed-in user on the RPA host — which addresses the review finding customers raise most often: an account left continuously signed in on the RPA host.
What’s New
Unattended execution
eb Macro and Scan Document tasks now run in a host process that the RPA Agent starts on demand, with no interactive Windows session and no RPA Client connected. They run on a host where nobody has signed in, including immediately after a reboot. These task types can also be given an Execution Context for the first time, in a credentials-only form, so a task runs as a specific Windows account instead of depending on who happens to be at the machine. Robot Tasks are not affected — every Robot Task continues to run in an interactive session through the RPA Client.
RDP session bootstrap
Robot Tasks drive a desktop, so they need one, and they can now get one on demand. Before a run, OpCon asks the RPA Agent whether the task’s execution user already has a usable session; when none exists, OpCon opens a Remote Desktop connection to the RPA host, signs the account in, waits for the Agent to report the user ready, and starts the task. A new Log off user After Execution Behavior signs that session out afterwards, so no session is left standing between runs — and because RPA cannot sign a user back in, it pairs with an RDP login user for the next run. To use it, configure a target host and a pool of Windows credentials on the OpCon RPA integration and set RDP Login User on each Robot Task; leaving it unset keeps the previous behavior. For more information, see Unattended Session.
Two additions round out the release
Export and import recordings
Recordings and the user variables they depend on can now be exported into a single file and imported on another machine, so you can move work to a replacement host or share a task with a colleague. Export from Export Settings on the Tray Client dashboard, choosing whole tasks or individual versions including drafts, and optionally protect the file with a password. Import resolves name conflicts one task at a time and prompts for any Windows credential the incoming tasks need — credentials are deliberately never included in the exported file. For more information, see Importing and Exporting Tasks.
Force native clicks in the Web Macro recorder
The recorder now offers a Force native clicks option, which replays every click recorded while it is on as real mouse input rather than as a scripted click. Only a native click carries the user activation a browser requires before it will open a new tab or window; previously the recorder decided this on its own and could not detect a button that opens a window from script, so those clicks replayed as scripted events and silently did nothing. The option can be changed while recording, and the Native click (send as real mouse input) option on the Action - Click window lets you change a single recorded click without recording again. For more information, see Native Clicks in Web Macros.
These additions let your team run RPA on hosts where nobody signs in, with deliberate control over the identity each task runs as, the clicks a web recording replays, and how work moves between machines.
Also in this release: corrected wildcard matching for window titles, element text, and file search; cleaner session sign-out and status reporting; browser tab handling in web recordings; high-DPI rendering, credential store, and recorder shortcut fixes; the completed removal of VisualCron references; and 128 dependency security updates. See the full 1.2.0 release notes for details, including upgrade and compatibility steps.