×

Supercharge your Proficy solution! Download a free trial of Proficy Operations Hub, CSense analytics, and more. Explore our Proficy 2024 releases!

Home
eSOP
Task Construction for Procedures
Task Construction for Procedures
After templates have been developed for the various types of standard operating procedures in your organization, you can construct tasks to meet your specific operational requirements.

Workflow IPI
Get Started
Tutorials
Orientation
Configure Your Environment
Security
Resource Information and Configuration
Data Administration
Forms and User Displays
Building and Configuring Workflows
eSOP
- eSOP Orientation
- Client Layout Configuration for eSOP Users
- Design eSOP Workflows Overview
- Task Construction for Procedures
  - Task Construction for Procedures
    After templates have been developed for the various types of standard operating procedures in your organization, you can construct tasks to meet your specific operational requirements.
    - Create and link a task
      The first step in task construction is to create the task and then associate it with the applicable task template, as well as the applicable personnel and/or equipment. As part of this process, you can also specify other details related to the task as a whole, including expiration time and priority.
    - Configure category filtering in eSOP
      You can filter the Task List by preconfigured categories. These categories organize concepts or features into groups. When you apply category filters, you focus information within your Task List.
    - Configure task emails
      You can configure email messages to be sent upon initiation and/or expiration of an overall task or individual task steps, as required.
    - Add task steps
      After you have created and saved a task, you can create the individual steps for the task. As part of this process, you can also specify other details related to the step, including expiration time, and you can override task-level personnel and equipment associations, as required.
    - Configure work instructions for task steps
      For each step in a task, you can configure work instructions to be displayed in the Task List at run time.
    - Link external documents to task steps
      For each step in a task, you can add external documents to be available from the Task List during run time. Linked documents are only available to users once a task step starts running.
    - Configure task step emails
      You can configure email messages to be sent upon initiation and/or expiration of task steps, as required.
    - Define jumps for task steps
      You can configure jumps for your task if, during run time, task steps need to be skipped or repeated.
    - Schedule a task
      After you create a task, you can schedule it by designating the event that triggers it. If a task should be performed in response to more than one event, you can create multiple schedules for the task.
    - Activate a task
      When task construction is complete, you activate the task for use in your production run time environment by enabling one or more schedules associated with the task.
- Task Maintenance
ActiveX Task Controls
Service Interfaces
Operator Task List in the Workflow Client
Best Practices

Task Construction for Procedures

After templates have been developed for the various types of standard operating procedures in your organization, you can construct tasks to meet your specific operational requirements.

Task construction in eSOP involves configuration at both the task level and at the level of each step within a task.

The order in which you perform the steps to construct tasks may vary somewhat from the order presented in this documentation. For example, whereas you must create a task and associate it with a template and with personnel and/or equipment before creating task steps, you can create task steps before configuring email messages for the task itself.

Likewise, whereas certain steps (such as creating a task) are mandatory, others (such as linking related documents to task steps) may be optional based the specific scenario that the task or task step is designed to address.

Finally, additional construction steps may be required based on the specific needs of your organization as reflected by custom configurations implemented in the related templates.