Skip to main content

FieldLogs

Understanding Custom Operation Plans

A Custom Operation Plan is a set of tasks that are encapsulated into a single unit for ease of execution.

It can be used to define an ordered sequence of execution of a set of Templates.

They are executed by the user at will. They are not triggered by events in the system.

A Custom Operation Plan consists of one or more Custom Counters. A Custom Counter encapsulates an Action.

Op-COP.png

There may be cases where a Custom Counter encapsulates multiple Actions.

COP-Structure.png

A Custom Counter encapsulates an Action.

OP-CustomCounter.png

Action:

The Action to be performed is defined here. The Action can be the execution of a Template, in a Task assigned to a Task Queue or an individual assignee.

One or more instances of several Templates can be configured as the desired Action.

In the following example, the Action that is defined in the Custom Operation Plan is to execute one instance of the Template Battery Particulars.

COP-Action.png