Product Updates

The Workflow ViewThe Processes page isn't limited to a job-by-job perspective. Switch to the workflow view to step back and see a running workflow as a whole, in the interactive, illustrative layout that longtime OpCon users know as the PERT view, and switch between your dev and production environments with a single click to see what's running where.What's new is the timeline. Rather than simply telling you a job ran on a given machine and finished with a given exit code, the timeline surfaces every status change in the workflow as it happened, in order:See each job move through its statuses — waiting to start, attempt to start, job running, finished OK or failed — and understand why, such as dependencies being met or a threshold dependency being honored Press play to replay the workflow's execution and watch the statuses advance Work at a granular level to see exactly how each job was evaluated, when, and how it finishedWatch Cordy use the workflow view and timeline to trace execution 

The Event LogWhen an event comes into OpCon, answering basic questions — what was it, who submitted it, how, and why didn't it run — has historically required knowing OpCon well enough to know where to look. OpCon Continuum introduces a centralized event log that tracks every event the platform processes, along with the context you need to make sense of it.Every processed event is recorded with the submitting user, the source, the environment, and the exact time it happened Filter by status to see only failed, expired, or completed events Search by ID, or expand an entry to see what the event was and what happened to it Failed events show the error, so a self-service button press that didn't run tells you both who pressed it and why it failedWatch Cordy walk through the new event log. 

The Job ViewTroubleshooting a failure in OpCon today often means checking several places — job output, the SAM log, detailed messages under job information, the agent log, the critical log. The Processes page in OpCon Continuum consolidates the list and matrix views and puts the information you need for a failed job in front of you instead of behind it.Filter to show only jobs containing errors, or narrow by any other status Job output is surfaced automatically for every job — no digging through multiple clicks Filter and search by tags, so you can scope the view to a set of jobs such as everything in production In-app notifications alert you to errors with a bell in the interface, not just by email or text, and acknowledgment is tracked so you know someone has seen itBecause Continuum works in memory rather than returning to the database for every request, all of this loads without the waits and refreshes you may be used to.Watch Cordy troubleshoot a failed job in the new Processes page. 

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.

The New Workflow DesignerOpCon Continuum brings the entire workflow-building experience into one place. Instead of moving from screen to screen, you work on a single responsive canvas with all of your settings docked on the right — name the workflow, choose a workspace, set your options, and save a draft without ever leaving the page. Terminology has been standardized along the way, so what you may have known as Schedule Master or Studio is now simply Workflows, and departments are workspaces. Watch Bruce build a workflow from scratch in the new designer. 

Versioning & DeploymentChange control for workflows is no longer a separate application. The capabilities customers valued in OpCon Deploy — versioning, controlled promotion between environments, and transformation rules — are now built directly into OpCon Continuum.Workflows live in the database as a draft until you commit them as a version Every saved version records the user and the notes describing what changed Deploying is a separate, deliberate step through Manage Deployment, where you choose which version goes to which environment Set the rule to "latest" and each committed version deploys automatically Transformation rules swap agents and values as a workflow moves between environments Effective and expiration dates let a deployment take effect on a specific date or run only during certain months Auto-build continues to work as it does today, respecting your override settingsWatch Bruce commit a version and deploy it. 

Calendar-Style Frequency BuilderFrequencies now live in their own dedicated area of the toolkit rather than being created on and tied to individual jobs. That means a frequency continues to exist even if no job is using it — no more losing a frequency because it was removed from the last job that referenced it.How frequencies work hasn't fundamentally changed, but how you build them has been simplified:A calendar-style builder that follows the same patterns you already use when scheduling in Outlook or a personal calendar — choose how often to repeat, then refine from there A live forecast for that specific frequency, visible as you work, so you can confirm the dates before you save The option to layer in a specific calendar for additional datesWatch Bruce walk through the new frequency builder. 

Code ViewCode View exposes the JSON structure behind a workflow, giving you a direct window into every job it contains. If you know scripting, you'll recognize it immediately. If you don't, it's still useful:Ctrl+F searches across the entire workflow and takes you straight to each match Find-and-replace applies the same change across many jobs in one pass The JSON can be copied out or exported for use elsewhere, and pasting it back in applies your changes It's a fast way to bring older workflows up to standard, or to add a large number of jobs at onceWatch Bruce use Code View to search, edit, and document a workflow. 

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.

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. 

When your examiner asks to see provisioning activity for a given period, you can now produce a single, comprehensive package rather than assembling records one by one.The Custom Audit Package report (found under Reports > Personnel Events) lets you:Select a date range and choose which event types to include Download a ZIP file containing individual event details, access request details, file attachments, and an Audit Package Summary overviewFaster Exam Response, Less Pre-Audit Scramble.Pulling together provisioning evidence has traditionally been one of the more time-consuming parts of exam preparation. The Custom Audit Package gives you a single, structured output you can hand directly to an examiner, reducing the back-and-forth that comes from assembling records across multiple reports and event types.Where to Find It:Reports > Personnel Events > Custom Audit PackageTry it before your next exam cycle.Go to Reports > Personnel Events > Custom Audit Package and run a test package for a recent date range to see what your examiners will receive.

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. 

We've expanded OpCon RPA's execution capabilities to give you greater control over where and how automated tasks run on Windows system, whether you're working on a single-user desktop or a multi-user server environment.What's new:Single-user Windows systems — OpCon RPA can now switch between locked user sessions, so automation keeps running even when a workstation is locked or another session is active. Multi-user Windows Server systems — Tasks can now be directed to the appropriate user session on shared server environments, ensuring automations run in the right context every time.These improvements make OpCon RPA more reliable and flexible across a wider range of deployment scenarios, reducing the need for manual intervention and giving your automations the execution context they need to succeed. 

Watch the video to see a walkthrough of automating newly designed reports in Solution Manager. 

Watch the video to see the changes made in accessing and using reports in Solution Manager. 

Watch the video to see the UI changes to Solution Manager. We’ve made updates focused on improving clarity, consistency, and ease of use. 

We’ve refreshed the Solution Manager UI to provide you more visual information without changing the features you rely on. Most things are still in the same place, but they’re clearer, quieter, and more consistent.What’s changed:Important information and actions are easier to spot Cleaner use of color, with clear status indicators Higher‑contrast text for better readability Clearer labels and buttons—less guessing, fewer tooltips Consistent behaviors across the product, like select‑all checkboxes in tablesWatch the video for more information! 

The updated Reporting feature in Solution Manager was designed from the ground up to keep everything you need in one place. Reports are now stored in a separate database which means they run much faster than before. All reporting actions and settings live within the feature Clear navigation between Reports and Settings using tabs Key information and actions appear where your eye lands first, including easy access to downloads Reports now export as CSV files, making data easier to use in databases and other tools Fewer reports to manage, thanks to consolidation and more robust filteringWatch the video for more information! 

We’ve updated the Studio page to make common actions easier to find and faster to use. The most‑used actions are now emphasized at the top of the page, while secondary actions remain available with clearer, more consistent labels.Actions are grouped more intentionally, and critical actions like Delete are always placed consistently and visibly. Watch the video for more information! 

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.  

📆 In relation to the OpCon release cadence, this feature was made available to OpCon Cloud customers in the winter of 2025. For on-prem customers, it was also included in the annual/winter release. The OpCon RPA client is now available, providing users with a powerful standalone tool to create and manage automation tasks. Users can design automated workflows using bots to record activities and leverage Optical Character Recognition (OCR) capabilities. These recordings integrate seamlessly with OpCon, enabling centralized management and orchestration of automation efforts. We are committed to continuously enhancing and improving the RPA client throughout the year.​ 

📆 In relation to the OpCon release cadence, this feature was made available to OpCon Cloud customers in the summer of 2024. For on-prem customers, Otto is not available. Otto, the AI Assistant, is now available via web chat. Otto offers access to an evolving knowledge base, email support capabilities, and assistance with daily operator tasks. It also provides guidance on troubleshooting job failures, including accessing logs and job output details. These capabilities are designed to streamline operations and enhance productivity.​Otto can perform skills on your behalf such as:Add a daily job Build a schedule Delete a daily job Get failed daily jobs and/or schedules Restart failed jobs Update a job, machine, or schedule statusHere are a few of the resources included in Otto’s knowledge base that are searched when you ask a question:OpCon product and integration documentation OpCon FAQs Industry use cases OpCon REST API specificationsSince the initial release of Otto, it has learned new skills:Retrieve a single log file by name Summarize build results for a schedule on a specific date and return a link to the log details page 

📆 In relation to the OpCon release cadence, this feature was made available to OpCon Cloud customers in the spring of 2024. For on-prem customers, it was included in the annual/winter release. Solution Manager now supports the majority of 508 Accessibility standards, delivering key enhancements such as improved screen reader compatibility, intuitive keyboard navigation, high-contrast modes, and text resizing options. These updates mark significant progress toward a fully inclusive experience for all users.✏Note: Solution Manager meets all L1 guidelines of Web Content Accessibility Guidelines (WCAG) 2.0.Accessibility support has been added to the following places:Main navigation Solution Manager Home Solution Manager Library Solution Manager Calendars Solution Manager Global Properties Solution Manager Logs Solution Manager Frequencies And many more pages

📆 In relation to the OpCon release cadence, this feature was made available to OpCon Cloud customers in the fall of 2024. For on-prem customers, OpCon Relay is not used. Solution Manager is now accessible over the public internet, removing the need for a VPN connection. The Netcom Relay acts as a middleman between your cloud instance of OpCon and the agents installed on the machines across your network. This update simplifies access, offering a secure and seamless experience from anywhere without requiring additional network configurations. The relay provides flexibility and convenience while maintaining robust security and delivering software through modern methods.Relay now supports the following job types:SAP MFT (Client & Server) zOS ACS✏Note: If you run OpCon on-prem there is no need for VPN. Currently, it is not possible to run Relay for an on-prem client by default. 

📆 In relation to the OpCon release cadence, this feature was made available to OpCon Cloud customers in the spring of 2024. For on-prem customers, it was included in the annual winter release. OpCon users can define a custom landing page upon logging into Solution Manager. Select the rocket icon displayed at the top right corner of each page to set your default landing page. Any of the following pages can be selected as the homepage, but only one page can be active at a time:Self Service Vision Operations Each page in Library Studio