Search help files, ask questions, get answers, and engage with your peers
Start here and get connected
Start discussions, ask questions, get answers
Find answers to questions in articles and help files
Submit ideas and suggestions
Read the latest news from our product team
Explore and RSVP for upcoming events
Connect with like-minded peers
Contact technical support, billing, invoicing, legal, and OpCon license keys
Set API certificate:This article will show you how to set an auto-signed certificate or your own signed certificate to your OpCon Rest. You'll find three scenarios :1. Generate a new self-signed certificate if no certificate found.2. Generate a new self-signed certificate if the existing certificate is expired.3. Set your own signed certificate. 1. No certificate found:In some cases the OpCon API is not reachable because the certificate is not find by the API, in this case you may only have to apply this procedure to allow the API to use it own auto-generated self-signed certificate : 1. Stop the RestAPI service: SMA OpCon RestAPI 2. Open a command prompt as Administrator 3. Navigate to the SAM folder (for installation on the system drive C:\Program Files\OpConxps\SAM) 4. Run the following command SMAOpConRestApi.Controllers.exe -setcertificate (for older version replaceSMAOpConRestApi.Controllers.exe by SMAOpConRestApi.OwinService) 5. Verify the process completed successfully, the log
This article explains how to use the OpCon API and PowerShell to calculate the average runtime of a job based on historical data and update the Max Runtime field accordingly. This is useful for ensuring that job monitoring thresholds are accurate and reflective of actual performance.OverviewThe Max Runtime field in OpCon can be used to trigger alerts when a job exceeds its expected duration. However, this field is not automatically updated by OpCon. By using the OpCon API, you can automate the process of calculating average runtimes and updating this field.Step-by-Step Process1. Retrieve Historical Job DataUse the OpCon API to retrieve job history for a specific job over a defined date range. Example PowerShell code:$startDate = (Get-Date).AddDays(-7).ToString('yyyy-MM-dd')$endDate = (Get-Date).ToString('yyyy-MM-dd')$url = "$baseUrl/jobhistory?startDate=$startDate&endDate=$endDate&jobName=MyJob"$history = Invoke-RestMethod -Uri $url -Headers $headers -Method Get2. Calculate Ave
This article provides practical PowerShell examples for interacting with the OpCon API. These examples are based on real-world use cases discussed in the OpCon community and training sessions.Getting API VersionUse this script to retrieve the current version of the OpCon API. This endpoint does not require authentication.Invoke-RestMethod -Uri "https://<your-server>/api/version" Authenticating and Storing TokensAuthenticate with the OpCon API and store the token for future use. $body = @{ username = "yourUsername" password = "yourPassword"}$response = Invoke-RestMethod -Uri "https://<your-server>/api/tokens" -Method Post -Body $body -ContentType "application/json"$token = $response.token Evaluating ExpressionsEvaluate property expressions using the API to test date formats and dependencies.$headers = @{ Authorization = "Token $token" }$body = @{ expression = "DATEADD(DATE(), -1, 'D')" }Invoke-RestMethod -Uri "https://<your-server>/api/expressions/evaluate" -Met
The OpCon API provides a way to send legacy or external events, similar to traditional messaging events used in older versions of OpCon. This feature is useful for backward compatibility and for integrating with systems that still rely on legacy event formats.Use CasesTriggering legacy event handlers configured in OpCon. Sending console display messages for monitoring purposes. Integrating with external systems that use legacy event formats.Example RequestBelow is a PowerShell example that demonstrates how to send a legacy console display event using the OpCon API:$body = @{ events = @( @{ id = "1" eventType = "ConsoleDisplay" message = "Legacy event triggered via API" } )} | ConvertTo-Json -Depth 3Invoke-RestMethod -Uri "$url/events/legacy" -Method Post -Body $body -ContentType "application/json" -Headers @{Authorization = $token} ConsiderationsThe API will confirm submission of the event but does not validate the success of the eve
The OpCon API provides a powerful endpoint for evaluating expressions, which is especially useful for testing property expressions, date formats, and conditional logic used in Self Service, job dependencies, and other automation scenarios.Why Use the Expression Evaluation Endpoint?This endpoint allows you to:Validate expression syntax before using it in production. Preview the evaluated result of date and property expressions. Test conditional logic used in disable/hide rules or job dependencies.Endpoint OverviewThe endpoint used for evaluating expressions is:POST /expressions/evaluateExample 1: Evaluating a Date ExpressionTo evaluate a date expression like `$DATE`, send the following JSON payload: { "expression": "$DATE"}A successful response might look like:{ "expression": "$DATE", "status": "Success", "result": "2024-04-17"} Example 2: Evaluating a Conditional ExpressionYou can also evaluate logical expressions. For example:{ "expression": "$DAYOFWEEK == 'Monday'"}This will re
The OpCon API allows users to programmatically add jobs to schedules, enabling dynamic automation and integration with external systems. This guide provides a step-by-step overview of how to use the API to add jobs to schedules, including required fields and example requests. Required InformationTo add a job to a schedule using the API, you will need the following information:Schedule name or ID Job name or ID Frequency and instance details Any instance properties or overrides Authentication token with appropriate permissionsExample RequestBelow is an example of a POST request to the /schedule-actions endpoint to add a job to a schedule:POST /api/schedule-actions HTTP/1.1Host: your-opcon-serverAuthorization: Token your-auth-tokenContent-Type: application/json{ "scheduleName": "DailyProcessing", "action": "AddJob", "jobName": "DataImportJob", "frequency": "Daily", "instanceProperties": [ { "name": "InputFile", "value": "data_2024_01_01.csv" } ]}TipsEnsure the job a
If I wanted to build a job on the 11th day(any) of a quarterly period after weekends or holidays. What’s the best way to do that? For example, a frequency that would build on the following days this year.01/13/202504/11/202507/14/202510/14/2025
Swagger is a powerful interface for exploring and testing the OpCon API. It allows users to interact with API endpoints directly from a browser, making it ideal for learning, debugging, and validating API calls.🔐Accessing SwaggerTo access the Swagger interface, use the following URL format:https://<YourServername>/api/doc/index-html Replace <your-server> with the actual server name hosting your OpCon environment. This URL opens the Swagger documentation and testing interface for the OpCon API.🌠Features of SwaggerSwagger provides the following capabilities:Browse available API endpoints grouped by functionality. View detailed request and response formats. Authenticate using tokens to test secure endpoints. Execute API calls directly from the browser✅Authenticating in SwaggerTo test endpoints that require authentication, use the 'Authorize' button in Swagger. When prompted, enter your token prefixed with the word 'Token' followed by a space.Token <your-token-here>Ensu
Authentication is a critical first step when working with the OpCon API. It ensures that only authorized users and applications can interact with the system. There are two primary methods for obtaining an authentication token:1. Via Solution Manager (Web Interface)2. Via API Call (Programmatic Access) 1. Authentication via Solution ManagerThis method is ideal for users who prefer a graphical interface and need a quick way to generate a token for testing or manual API calls.Steps:Log into Solution Manager. Navigate to your User Profile. Click on 'External Token'. Click 'Generate Token'.Copy the token and use it in your API requests.✏Note: If you do not see the 'External Token' option, check your user permissions or OpCon version. 2. Authentication via API CallThis method is suitable for automation and scripting. You can generate both user and application tokens programmatically.Example PowerShell Script to Generate a User Token:$url = "https://<your-opcon-server>/tokens"$body = @{
As of June 17, 2025, AT&T has officially discontinued its email-to-text and text-to-email services, impacting many organizations that rely on these channels for alerts and service messages. This change affects any system configured to send SMS notifications via email, including the Symitar Paging System, which can no longer deliver texts to AT&T phone numbers through email.For credit unions and financial institutions using Symitar®, this disruption could mean missed alerts and communication gaps—especially for teams that depend on automated notifications for operational workflows.SMA’s Workaround: Twilio SMS Notification ScriptTo help clients navigate this change, SMA Technologies has developed a workaround using Twilio, a cloud communications platform. The solution is available as an open-source script on GitHub:https://github.com/smatechnologies/twilio-sms-notificationsThis script enables OpCon users to send SMS alerts directly through Twilio, bypassing the now-defunct email-
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.