Some Basic Concepts

Foresight Operational Monitor looks on all reported events for one particular business activity as a job. An input file into an Automator workflow or a script is a job.

Individual parts of the process become collection points that reports one or more events about the Job to the Foresight Operational Monitor.

In an Automator workflow, for example, a job starts with a file in the originating input folder, a collection point might be a Response Generator component, and it might have events like taking a DTL file in or putting a 997 file out. A component that has file movement without input and output lines (TPARouter, for example) generates a new job.

In a non-workflow, if you are writing a script that calls several different programs in order, each time you run that script is a job, each of the programs you are running are collection points, and each of those collection points reports information on what has happened as events.