Skip to main content
  • 25 Product updates

OpCon RPA 1.2.0: Unattended Execution, RDP Session Bootstrap, and New Functionality

OpCon RPA 1.2.0: Unattended Execution, RDP Session Bootstrap, and New Functionality

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 NewUnattended executioneb 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 bootstrapRobot 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 releaseExport and import recordingsRecordings 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 recorderThe 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.

Related products:OpCon
OpCon Continuum: Workflow Designer
OpCon Continuum: Versioning & Deployment
OpCon Continuum: Frequencies
OpCon Continuum: Code View Option
Permission Assist 6.5: Define Who Must Approve Personnel Events Before Provisioning Begins

Permission Assist 6.5: Define Who Must Approve Personnel Events Before Provisioning Begins

Administrators can now configure exactly which organizational roles are required to approve or verify each personnel event type before provisioning starts.You can require approvals from any combination of the following roles:Supervisors Personnel Managers Defined Managers (including managers for Company, Division, Department, Office, and Title Manager) Security Team membersEach approver reviews and responds independently. The event only advances to the next step when all required responses have been received, giving you a clear and enforced chain of approval rather than relying on informal coordination.Demonstrate a documented, enforced approval process to your examiners.Regulators and examiners expect financial institutions to show that access provisioning follows a defined process. Configurable approval rules let you align Permission Assist directly to your institution’s access governance policies, so you can confirm exactly who was required to approve an action and that the system enforced it before provisioning occurred.Where to find it:Configure approval rules per event type in your workflow settings. Go to System Configuration > Taskboards > Personnel Events and approve or verify a personnel event for step-by-step guidance. Log in to Permission Assist and visit your workflow settings to configure approval rules for each personnel event type. Have questions about aligning rules to your policies? Reach out to your Customer Success Manager.

Related products:Permission Assist
Permission Assist 6.5: Automate Your IAM Workflows with the New Permission Assist REST API

Permission Assist 6.5: Automate Your IAM Workflows with the New Permission Assist REST API

Permission Assist 6.5 introduces a REST API that lets your external systems connect directly to Permission Assist, removing the need for manual data entry between platforms. No new infrastructure is required.With the API, you can now trigger key workflow actions programmatically, including:Importing user and permission data using automation tools instead of manual effort Creating personnel events such as onboarding, offboarding, role transitions, and leaves of absence Initiating application imports on demand from HRIS platforms, ticketing systems, and automation toolsEvents created through the API follow the same approval and provisioning workflow as events created manually, so your existing rules and audit trails stay intact.Works with Tools You Already HaveThe API is compatible with OpCon, VisualCron, PowerShell, and other automation platforms your institution may already have in place. If you are running OpCon, this opens the door to a fully automated identity governance workflow without adding new vendors or infrastructure.Before You Get StartedReview the hardware and software requirements to confirm your environment is ready for the 6.5 update.API DocumentationFull endpoint details, authentication requirements, and example payloads are available at docs.sycorr.com/6.5/api/Ready to connect your first system?Start with the API documentation or reach out to your Customer Success Manager to discuss your integration use case. View API docs. 

Related products:Permission Assist
Permission Assist 6.5: Generate a Single Audit-Ready Report for All Personnel Event Activity
OpCon RPA 1.1.0: Standalone Deployment, Task Copy, and Task Delete

OpCon RPA 1.1.0: Standalone Deployment, Task Copy, and Task Delete

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:Copy all versions, including the working draft Copy a single version as the new task’s Version 1, starting with a clean history Copy a version as a draft for further refinement before publishingThis makes it easy to turn a proven automation into a reusable template, branch a workflow to experiment safely, or spin up a variation without touching the original.Delete TasksRelease 1.1.0 adds a Delete action to the Drafts and Archive views, giving your team a straightforward way to keep your automation library clean and current.Safeguards are matched to what’s being removed:Deleting a published task from the Archive removes the task and all of its versions, with a clear warning that the action can’t be undone Deleting a draft removes only that draft. No other versions are affectedDelete and Run controls are also automatically disabled while a task is running, so there’s no risk of accidentally modifying an active automation. 

Related products:OpCon
OpCon RPA 1.0.2: Desktop Session Switching and Execution Context
OpCon 26.0: Changes in Solution Manager for Clarity and Consistency
OpCon 26.0: Reporting Features in Solution Manager
OpCon 26.0: Solution Manager Studio Page Updates
Meet OpCon 26.0 - More Insight, More Consistency, Full Capability

Meet OpCon 26.0 - More Insight, More Consistency, Full Capability

We're excited to share that OpCon 26.0 launches in February with a milestone we've been working toward: Solution Manager is now feature complete.All remaining core features from Enterprise Manager—including legacy BIRT reports and final job subtypes—are now fully available in Solution Manager. If you've been waiting to make Solution Manager your primary tool, this is the moment.What This Means for YouWith feature completeness achieved, we're shifting our focus to streamlining the user experience. Throughout 2026, you'll see continued improvements to workflows, reduced clicks, and faster navigation. This release sets the foundation for that work.What Else Is New in 26.0Unified OpCon Experience - Solution Manager, OpCon RPA, and OpCon MFT now share a consistent look and feel. Standardized layouts, clearer information hierarchy, and predictable interactions make it easier to move between tools and train new users.Stronger Reporting - All EM Reports in SM: Legacy BIRT and Enterprise Manager reports are now accessible directly in Solution Manager, eliminating the need to switch between tools New Reporting Engine: Faster report generation and improved stability, even during peak times Custom Scheduling (Cloud): Run reports once, twice, or at exact times you choose Enhanced Reliability (Cloud): Reports backed up across regions for greater availability Direct Log Access: Report logs now visible directly in the log viewer Precise Date Filtering: View reports using exact date ranges Clear Status Indicators: See when reports last ran and get alerts if they failModernized Interface - We've updated Solution Manager with consistent layouts, improved visual hierarchy, and standardized interaction patterns across all features. The result: less time navigating, more time automating.What Hasn’t ChangedYour schedules and jobs continue to run exactly as they do today. This is an enhancement to the platform, not a disruption to your workflows.What to Do NowCloud customers: Plan to use OpCon 26.0 when it goes live next month On-Prem customers: Contact your account team to schedule your upgrade or download it when it's available next monthFull release notes arrive in early February.  

Related products:OpCon
Standalone Robotic Process Automation (RPA) Client for OpCon
Otto -- The AI Chatbot
Accessibility Support: 508 Standards
Public Internet-Accessible OpCon (Netcom Relay)
Configure a Default Homepage (Rocket Icon)
Access Management Improved Workflow (Password Management)
OpCon Release Schedule

OpCon Release Schedule

OpCon Release Schedule: What to ExpectAt Continuous, we aim to provide a predictable, transparent release cadence that helps our customers plan, test, and adopt OpCon updates with confidence. This document explains how releases work, when to expect them, and what actions our customers should take.Our Release ProcessEach OpCon release follows a structured lifecycle designed to ensure quality, stability, and customer readiness: Ideation: We gather ideas from customer feedback, partner input, and internal insights. Refinement: Ideas are reviewed, scoped, prioritized, and scheduled into upcoming release windows Publishing: Approved features are documented and communicated ahead of testing and release. Work Window: Engineering builds, validates, and stabilizes features and fixes. User Acceptance Testing (UAT): Approximately 2-3 weeks prior to production release, UAT is conducted to validate functionality and support overall release readiness. While we follow this lifecycle consistently, timelines may adjust when necessary to address quality, security, or operational considerations.Release Cadence OverviewRather than fixed calendar dates, OpCon releases follow a quarter-based cadence, with production releases typically occurring in the second month of each quarter. This approach provides a consistent planning framework while allowing flexibility as needed.Release Type Typical Timing Q1 Release 2nd month of Q1 Q2 Release 2nd month of Q2 Q3 Release 2nd month of Q3 Q4 Release 2nd month of Q4  Cloud-Hosted vs. Self-Hosted OpCon Cloud-Hosted OpCon Quarterly feature releases New functionality delivered incrementally throughout the year Ideal for customers who want faster access to innovation with minimal operational overhead Self-Hosted Annual feature release (equivalent to a long-term support release) Quarterly maintenance releases focused on fixes and stability Designed for customers who prefer controlled upgrade cycles What This Means for YouOpCon’s release cadence is designed to help customers stay informed and plan adoption on their own timelines. Ahead of a release window: Review published release notes and upcoming changes to understand potential impact to your environment Leading up to production release: Be aware of upcoming updates and plan any internal readiness or communication as needed After production release: Review delivered features and fixes to determine when and how to adopt new functionality This cadence is designed to provide predictable delivery while allowing flexibility, so that our customers can adopt updates on their own timelines.Frequently Asked QuestionsDo I need to upgrade every quarter?No. Customers can choose when to adopt feature releases within the 36-month support window.Are maintenance releases required?Maintenance releases are recommended for stability and fixes, especially for self-hosted environments.Will release dates change?Specific dates may adjust, but the quarterly cadence remains consistent.

Related products:OpCon
Important Update: Microsoft’s Deprecation of Basic Authentication for Exchange Online

Important Update: Microsoft’s Deprecation of Basic Authentication for Exchange Online

Microsoft is making a significant change that could impact your OpCon environment. Beginning September 2025, Microsoft will retire legacy authentication methods (Basic Auth) for Exchange Online, requiring all users to transition to Modern Authentication (OAuth 2.0).Why This MattersOnce Microsoft deprecates Basic Authentication, any OpCon job using SMTP Basic Auth for email notifications will fail to authenticate, causing emails not to send. Identifying affected systems now will help ensure you transition smoothly to Modern Authentication without disruptions.What This Means for YouIf your OpCon environment relies on email notifications sent via SMTP Basic Auth to authenticate with Exchange Online, your jobs may fail to send emails once this change takes effect. That means critical notifications might not reach your teams, potentially disrupting your automation workflows.🔹 OpCon Cloud customers using the Relay component are NOT affected.To ensure a smooth transition and assess the impact on your environment, we need your input.How to Check Your SetupPlease confirm the following:Are you currently using email notifications in OpCon? Is the SMTP account for OpCon notifications a Microsoft Exchange Online account? If “yes” to both of the above, what is your OpCon version?Action RequiredIf you answered “yes” to both Question 1 and 2, please reply to support@smatechnologies.com as soon as possible with your OpCon version to open a support ticket.How to Find Your OpCon Version (On-Prem Customers only)On your OpCon server, go to Control Panel Navigate to Programs > Programs and Features Locate SMA OpCon and check the version number📢 Don’t wait—confirm your setup today!If you have any questions, feel free to discuss them in the comments below or reach out to SMA Technologies Support.

Related products:OpCon