Skip to main content
  • 16 Product updates

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