43 docs tagged with "Administrator"

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

How agents run your jobs, how agent pools route work to whichever agent is available, and how to read an agent state or diagnose a job waiting for one.

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.

Moving a bundle of workflows, calendars, frequencies, properties, thresholds, resources and tags between environments or tenants — what the bundle contains, what export deliberately leaves out, and the overwrite and all-or-nothing rules import applies.

How a connection stores the configuration and credentials an external system or a legacy run-as account needs, which connection types exist today, how secrets are stored and masked, and how to attach one to a job.

How to build, run, and export reports so you can track job activity, agent health, and schedule outcomes.

How to build a child workflow as a container job, then deploy it so other workflows can reuse the same set of steps.

How Classic's Batch Users map to OpCon Continuum connections, and the steps to set one up.

How to add your own tenant-global metadata fields to jobs, what each definition field controls, where values are set, and which input types are available.

How to define custom fields so you can capture and track additional information on jobs across your environment.

How promoting a Classic schedule between instances maps to versioning and deploying an OpCon Continuum workflow.

What an environment is as a deployment target for workflows and service requests, the fields and service health it reports, and why a newly created one may still be provisioning.

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.

The job types that wait for, move and manage files today, with Wait for File and SMAFT File Transfer walked through in full — including the allowed-path rule that stops a wait before it starts.

A checklist of hands-on tasks so you can learn OpCon Continuum administration by setting up agents, connections, and access in a test environment.

How to add, configure, and group agents into pools so work runs on the right machines and stays available.

How to create, edit, and secure connections — both the endpoint and login for an external system and the batch user a legacy job runs as.

How to create and manage environments so you can separate and promote work across development, test, and production.

How to set up notification groups, triggers, and actions so the right people are told when an agent, workflow, or job needs attention.

How to enable, disable, and update plugins so you can extend OpCon Continuum with built-in and external capabilities.

How roles, permissions, and scopes control who can see and change what, and how to assign them.

How to create and manage workspaces so you can organize work and control access by team or function.

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

How notification groups, triggers, and channels decide who gets told when an agent, relay, workflow, or job changes state.

How Classic Departments map to OpCon Continuum workspaces for keeping a team's or application's content separate.

How plugins package the job types your jobs can run, which plugins are enabled by default for a tenant, and why a job type you cannot build with is usually a disabled plugin.

How to prepare agents with the interpreters, drivers, and permissions each connector needs before running connector jobs.

How to build a workflow and a service request, deploy them, and hand business users a guided form so they can trigger the automation themselves.

What a relay is, how to register, install, and health-check one, and how to rotate its credentials so legacy LSAM machines can run jobs dispatched from the cloud without inbound firewall changes.

What you can report on, how to build a report from columns, sort rules, and filters, and how to save, re-run, and export the results.

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 roles, the permission catalog, and workspace and environment scopes shape what each person sees in Continuum, and the refusals that apply to every event.

How Classic frequencies and calendars map to OpCon Continuum's pattern model, where holidays and working days are decided now, and how to confirm a schedule before it goes live.

How to register, install, and maintain a relay so your on-prem legacy LSAM machines can run jobs dispatched from the cloud.

How to set up and test database connections so jobs can run SQL against your databases securely.

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

How Classic's fixed job-type catalog maps to OpCon Continuum job types and connectors, including legacy LSAM commands.

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

What carries over from OpCon Classic and what does not, which capabilities to check against your own automation before you move, and what to have ready for the conversation with your Continuous contact.

How Classic machines and machine groups map to OpCon Continuum agents and agent pools, including how existing LSAM machines keep running through the relay.

How workspaces group and isolate workflows, properties, thresholds, resources, scripts, and service requests, what stays global, and why access comes from role scopes rather than workspace membership.