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

Home
Building and Configuring Workflows
Workflow Foundations
Workflow Foundations
This section provides you with general information about workflows, from information you need to develop them to running them.
Process Execution Model Overview
The process execution model defines the structure of a workflow, and has several process steps that can be programmed and triggered during a workflow instance.
Workflow Process Steps
Process steps are part of every process-oriented workflow.
Preprocess
The preprocess step starts after the load step ends. This step performs any initialization work required for the process.

Workflow IPI
Get Started
Tutorials
Orientation
Configure Your Environment
Security
Resource Information and Configuration
Data Administration
Forms and User Displays
Building and Configuring Workflows
- Workflow Design Basics
- Workflow Foundations
  - Workflow Foundations
    This section provides you with general information about workflows, from information you need to develop them to running them.
    - Tasks
      Workflow tasks are accessible when a workflow has been put into a run time state. When a workflow is running, the task information is available to the computers and operators assigned to that task or task step, as well as to administrators.
    - Workflow Execution Engine Overview
      This application consists of a workflow execution engine, which is the core component of the process management system. The engine is responsible for interpreting workflows, controlling multiple workflow instances, and sequencing subprocesses and activities.
    - Persistence in Workflows
    - Building and Configuring Workflows
      Workflows consist of programs that can carry out complex activities, respond to events and data changes, and write values back out to the data models or through external connectors.
    - Process Execution Model Overview
      The process execution model defines the structure of a workflow, and has several process steps that can be programmed and triggered during a workflow instance.
      - Workflow Process Steps
        Process steps are part of every process-oriented workflow.
        Load
        The load step is the first step in a workflow cycle. It is used to perform a one-time only setup for the workflow instance.
        Preprocess
        The preprocess step starts after the load step ends. This step performs any initialization work required for the process.
        Presubprocess
        This step performs any initialization work required for the subprocess.
        Task Step (Subprocess) Configuration
        A subprocess is part of a user-defined process in a workflow.
        Postsubprocess
        The postsubprocess step starts after the subprocess, and at the end of every subprocess listed.
        Postprocess
        The postprocess step completes a workflow before the unload step starts.
        Unload
        The unload step is the last step in a workflow cycle.
      - Resource View
        The Resource View provides you with more information at a glance of certain properties associated with workflow and schedule resources.
- Task Management for Administrators
- Task Configuration
- Task Step Configuration
- Global Subprocesses
- Basic Activities
- Schedules
- Faults
- Test Workflows
- Debug Workflows
- Track Data
- Web Services Service Provider
- Legacy Workflow Web Service
- Categories
- Completion Codes
- Actuals
- REST APIs
eSOP
ActiveX Task Controls
Service Interfaces
Operator Task List in the Workflow Client
Best Practices

Preprocess

The preprocess step starts after the load step ends. This step performs any initialization work required for the process.

If the workflow is set on a continuous loop, this step becomes the first step reinitiated after the postprocess step ends. The continuous loop then runs between the preprocess and postprocess steps. The only time this loop breaks is if an end command is used or an unhandled fault occurs. The workflow then continues through the rest of the steps to the unload step.