Recently active topics

A customer asked, “Does the AddJob action exist? How do I find a list of possible actions?”This is a great question because understanding the correct API endpoints and available actions is essential for smooth automation.Refer to the article Adding Jobs to Schedules via the API to see an example of a POST request to the /scheduleActions endpoint to add a job to a schedule.List of Available ActionsHere is a list compared to the normal event syntax:Event Syntax API Action JOB:ADD {“addjobs”} JOB:BAD {“markJobsFailed”} JOB:CANCEL {“cancelJobs”} JOB:FIXED {“markjobsfixed”} JOB:FORCESTART {“forceRestartJobs”} JOB:GOOD {“markJobsFinishedOk”} JOB:HOLD {“holdjobs”} JOB:KILL {“killJobs”} JOB:RELEASE {“releaseJobs”} JOB:RESTART {“restartJobs”} JOB:RESTARTHLD {“restartJobsOnHold”} JOB:SKIP {“skipJobs”} JOB:START

What is a Container?A container is the other half of the sub schedule. While the sub schedule controls the flow of the job, the container job enables it to auto-build and run independently. It consolidates the sub-schedule into a singular object. The contain acts as a wrapper around the entire process, allowing interaction from a single job aspect. How to Create a Container JobIn Solution Manager, create a job. Below is how to create a job in Studio with an existing schedule displayed:Enter the Name of the Job.Select from the Job Type dropdown Container.Once you’ve selected Container, you will define the Master Sub-Schedule.If necessary, you can edit the Sub-Schedule Jobs or the Sub-Schedule.Enter any Documentation and/or Tags.Click on Frequency and move the appropriate Frequency from the Inactive column to Active.This frequency dictates when the schedule is built.✏Note: One of the benefits of a Container job is using it in conjunction with an On Request frequency. For example, if you

The difference between a normal schedule and a sub schedule is the checkbox within the Master Schedule Definition:Simply check the Sub Schedule check box under Schedule Settings and click Save.On a functional level, a lot of things change when you change a Schedule to a Sub Schedule.Sub schedules do not allow auto build or auto deletion. It will not become an independent schedule.When you view the newly created sub schedule, it looks the same from the perspective of the flow: all the jobs, dependencies, and frequencies remain the same.

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 /scheduleactions endpoint to add a job to a schedule:POST /api/scheduleactions 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 and

During our November 13th Connections session, Bertie van Hinsbergen shared a lot of information about the enhanced EASE Connector within the PowerPoint deck. Click below to access the slide deck. 

Why Use Global Properties for Notifications?Hard-coding email addresses directly into notification workflows creates several issues. Instead, use Global Properties to store recipient lists in a centralized, easily maintainable way.Benefits of Using Global Properties for Email Distribution ListsCentralized ManagementAll recipient addresses are stored in one location. Updates propagate automatically across all workflows.Environment-Specific ControlConfigure different recipient lists for development, staging, and production without changing workflow logic.Improved ScalabilityAdding or removing recipients is as simple as updating the property.How to Implement Global Properties in Notifications (in Solution Manager)First create the Global Property for alerts by navigating to the Library and clicking Global Properties.Click Add.Enter the Name of the Global Property.Enter the email address(es) in the Value field. Separate the email addresses by a semicolon.Click Save.Now, navigate to the Libr