OpCon Release Notes
This page lists changes for each OpCon release, organized by release season and version. Each entry is prefixed with one of the following indicators:
- ✳️ — New feature or enhancement
- ✅ — Bug fix
Compatibility notes at the start of each version identify companion components that require updating before or alongside that OpCon release.
Spring 26
26.1.2
NOTE: For compatibility, the following packages require updating if used on-premises:
- ACS AzureWebservices - 25.0.2
- ACS Ease - 25.0.3
- ACS WebServices - 25.0.2
- Deploy – 26.0.0 or higher
- Enterprise Manager - 26.0.1 or higher
- Relay - 26.1.2 or higher
- ServiceNow Connector – 25.0 or higher
- WebServices Connector – 21.6 or higher
Core Engine & Infrastructure
✅ OC-7278: Schedule Built for Wrong Date Fixed an issue with build date selection.
✅ OC-7316: Question Mark in Resolved Values of [[$NOW]] and [[$TIME]] Resolved values of the $NOW and $TIME global properties no longer contain an unexpected question mark before AM/PM (for example, 12:27:01?PM now correctly displays as 12:27:01 PM). This affected SAM logs, console display events, notifications, and any other location where these properties were resolved.
✅ OC-7321: Job Output Retrieval Through Relay Over TLS Resolved an issue where JORS (Job Output Retrieval Service) requests routed through SMANetComRelay over TLS would fail with a "Client Certificate with Serial Number not found in repository" error in environments where TLS client certificate validation was not configured.
26.1.1
NOTE: For compatibility, the following packages require updating if used on-premises:
- ACS AzureWebservices - 25.0.2
- ACS Ease - 25.0.3
- ACS WebServices - 25.0.2
- Deploy – 26.0.0 or higher
- Enterprise Manager - 26.0.1 or higher
- Relay - 26.1.0 or higher
- ServiceNow Connector – 25.0 or higher
- WebServices Connector – 21.6 or higher
Core Engine & Infrastructure
✅ OC-6412: Request Router Request Processing Fix Fixed an issue where SMARequestRouter could occasionally skip processing requests submitted by SAM, causing automated schedule builds, deletes, checks, and forecasts to be silently missed. Users may have noticed automated schedule builds skipped or not running for upcoming run dates, missing SMASchedMan log files for affected schedules, or repeated "has not yet been submitted by SMARequestRouter" warnings in the SAM critical log. SMARequestRouter now performs a periodic recovery check that detects any previously skipped requests and re-dispatches them, with log entries confirming both the detection and the recovery for operator visibility.