Run RPA Without OpConOpCon RPA no longer requires an OpCon environment to operate. Starting with release 1.1.0, tasks are stored locally on the RPA Agent rather than in the OpCon Script Repository, which means OpCon RPA can now be deployed and run in environments that don’t use OpCon at all.For existing OpCon customers, this also means a simpler setup experience. There’s no longer a dedicated OpCon user to create or an API connection to configure. The OpCon Settings tab has been removed from the RPA Tray Client entirely, leaving a streamlined settings page focused on RPA Agent configuration only.Whether you’re expanding RPA into a new environment or setting up for the first time, 1.1.0 removes the barriers that previously tied robotic automation to an OpCon installation.Copy TasksYou can now duplicate tasks directly from the Drafts and Archive views in the RPA Tray Client. You don’t have to rebuild from scratch.When copying a task, you choose how much version history to bring along:Cop
