Product Updates

📆 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 ‘25 release.   The password management workflow has been improved to enhance user autonomy and simplify account access. Users can now reset their own passwords quickly and securely, reducing reliance on administrative assistance. This update streamlines the process while maintaining robust security measures, providing a more efficient and user-friendly experience.​Require email for users Forgot My Password Link Password Recovery Validation 

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.

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.