30 docs tagged with "Operator"

How Classic's notification setup maps to OpCon Continuum's notification groups, triggers, and channels, and how to prove an alert arrives before you depend on it.

How to connect the pieces you already know -- a workflow, a frequency, a wait for file, dependencies, and a failure event -- into one unattended nightly core export.

How each user is routed to the dashboard that matches their role, and what the Administrator, Operator, and Business dashboards surface.

How to read an event's fields and use status, source, and correlation ID to trace a whole chain of related actions back to what caused it.

How a job or process on a legacy LSAM machine raises an OpCon Continuum event by writing a file of event syntax into the agent's MSGIN directory — the Default event environment it needs, the line format and the credential pair Continuum verifies, which events are applied, how each one is attributed and where a rejected line goes.

How to wait for an inbound file from a partner, validate and process it, and handle failures, without a person watching for the file to arrive.

A checklist of hands-on tasks so you can learn OpCon Continuum by monitoring a run and responding to jobs in a test environment.

How to find objects across ten entity types from one place, save a search to re-run it, and use the bulk actions and exports available.

How a built workflow moves through waiting, running, pending-term, and terminal statuses, so you can tell a job that is working as designed from one that is genuinely stuck.

The authoritative list of every job and workflow status, what each one means, and which lifecycle actions a job or workflow in that status will accept.

A reference to job statuses and the operator actions available for each, so you know how to respond during the daily run.

How to group jobs into Vision cards with SLAs so you can see at a glance whether critical work is on track to finish on time.

How to build Vision cards with service-level agreements so an at-risk critical path is visible before the deadline is missed.

How Solution Manager Operations/Vision map to OpCon Continuum's Workflow View and Job View, and the operator actions available.

How to monitor the daily run so you can track progress and act on jobs that need attention.

A guided reading order for the Operator pages, grouped into modules that build on each other.

What each waiting, running, failed, or held job state means during the daily run, which action to take in response, and how to read a completed job's exit code.

How to build a failure-triggered recovery dependency and event so a failed run retries or reroutes on its own, before an operator needs to step in.

How reporting moves from Classic's reporting service to OpCon Continuum's built-in report builder — what you can report on, how a report is saved and exported, and what has no report in this build.

How to diagnose and respond to a failed connector job so you can get a stalled workflow moving again.

How to respond to a failed job by reviewing the cause and choosing the right recovery action.

How to respond to a stuck or failed Wait for File job so a waiting workflow can continue or be escalated.

How one workflow builds as several named schedule instances for the same date, each carrying its own property values — how instances are defined, how a build targets them, how they are named and displayed, and how dependencies, conflicts and events address one instance.

How to search across OpCon Continuum so you can quickly find jobs, workflows, and other objects.

How to create a notification group, target the jobs that matter, and prove it works, so a failure overnight never goes unnoticed.

How to work the Processes page, including the Job and Workflow views, filters and search, single and bulk job actions, and job detail.

How to use the event log to trace what happened during a run using correlation IDs and event statuses.

How Vision boards, tag cards, and SLA targets show whether the right work is finishing on time, and how each card is evaluated.

What OpCon Continuum changes for Administrators, Builders, Operators, and business users, and which of those areas are still maturing.

How to use the Processes page to watch the daily run and act on jobs -- filter, search, and take single or bulk actions.