×

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
Basic Activities
Flow Control Activities
These activities are used to create multiple execution layers within workflow logic.
If/Else Activity
The If/Else activity changes execution of the workflow to one of multiple exit branches based on the resolution of a condition.

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
- Task Management for Administrators
- Task Configuration
- Task Step Configuration
- Global Subprocesses
- Basic Activities
  - Activities Used to Create Workflows
    Activities comprise the main building blocks or steps that perform the actions in a subprocess or workflow.
  - Third-party Activities
    Workflow can utilize third-party activities that are compatible with Microsoft Windows Workflow Foundation.
  - Predefined User Activities
    A user activity defines part of a user-defined process in a workflow process step. For a workflow to run, all user activities must be valid (contain no errors) and enabled (active).
  - Data Access Activities
    These activities are used for passing information and data between workflows and activities.
  - Workflow Control Activities
    These activities are used for creating changes in a workflow, such as starting or stopping activities, during run time.
  - Message Queue Activities
    These activities are used for working with a messaging queue in order to co-ordinate work between workflows and activities.
  - Flow Control Activities
    These activities are used to create multiple execution layers within workflow logic.
    - Delay Activity
      The Delay activity allows a pause or a time out in a sequence or process while a workflow is running. When the activity has met the specified criteria, the process or sequence can then complete the next set of activities assigned to the process.
    - Break Activity
      The Break activity ends the execution of For Each and Parallel activities, exiting the activity at the point following the break. So, if there are any activities following the Break activity, they do not execute.
    - While Activity
      The While activity repeats the execution of a workflow subsection as long as a specified condition is true. The condition is checked each time the activity begins.
    - Parallel Activity
      A Parallel activity contains two or more sequences that execute at the same time. All branches complete before the activity completes, unless a Break activity is used.
    - For Each Activity
      A For Each activity repeats the execution of a section of the workflow several times for a number of target instances in a collection.
    - If/Else Activity
      The If/Else activity changes execution of the workflow to one of multiple exit branches based on the resolution of a condition.
      - Add a condition to an If/Else activity
  - Event-based Activities
    These activities are used when you require workflow logic to start an event during run time.
  - Keyword Activities
    You can use keywords to replace text in work instructions and email subjects and bodies. This text is replaced with keyword values in a workflow at run time.
  - Operator Activities
    These activities are used by operators when a workflow is running the Task List.
  - eSOP Activities
    These activities are used when working with the eSOP Editor.
- 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

If/Else Activity

The If/Else activity changes execution of the workflow to one of multiple exit branches based on the resolution of a condition.

An If/Else branch can have multiple exit branches, each of which has a condition. Conditions on multiple exit flows are calculated from left to right. The flow executes on the first exit branch whose condition evaluates to True. There are no conditions on the last branch of the activity, as it is automatically set to True.

Tip: The subprocess property value Visible Property can be used for this activity.

If/Else Branch

The If/Else branch contains one or more sequences as branches. Each branch has a condition that is evaluated to a boolean result. If the condition evaluates to True, the sequence for that branch is queued as the next activity for the workflow instance to execute. Conditions are evaluated from left to right, and the first sequence with a condition evaluating to True is executed. If no condition is specified, the branch serves as an Else and always executes.