Scheduling and holidays: what changed from OpCon Classic
This page maps OpCon Classic concepts to their OpCon Continuum equivalents. It is a conceptual mapping under review, and it deliberately does not compare the two products' platform or job-type breadth. Use it to translate what you already know — not as the basis for a migration plan. Confirm specifics with your Continuous contact.
What this solves
A frequency is the thing you are most likely to get subtly wrong, because both products call it a frequency and both have calendars — so it feels like nothing changed. What changed is where the answer comes from. In OpCon Classic you reasoned about a frequency's bitmask and a calendar attached to it. In OpCon Continuum a frequency is a named pattern, what counts as a working day is the workflow's decision rather than a fixed Monday-to-Friday, and holidays can reach a schedule by three different routes. Get the routes mixed up and a month-end job lands on a holiday.
What you get. Where each Classic idea went, the three places a calendar can apply, and how to prove a pattern is right before anything runs on it.
Related topics
- Define frequencies (Builder)
- Schedule a workflow (Builder)
- Frequencies — the full pattern reference
- Calendars
- Build a workflow: what changed from OpCon Classic