Configuring Dependency Conditions for Event Workflows

Overview

Dependency conditions for workflows allow you to control when and how workflow sequences are executed using advanced, rule-based logic. By applying dependency conditions, you can ensure that specific workflow blocks—such as engagement, invitation, or registration-related sequences—are triggered only when defined criteria are met.

This article explains how to configure, manage, and apply dependency conditions within workflows.

Step-by-Step Approach

1. Access the Event Workflows module

• From the Event dashboard, navigate to Workflows.
• Select either Event Workflows or Event Automation Workflows.

2. Select a workflow sequence

Access any of the available workflow sequence blocks, including:

• Engagement Sequence
• Invitation Sequence
• After Registration Sequence
• Before Registration Sequence
• On Waiting List Sequence
• Finalization Sequence
• Initiation Sequence

• Select the required workflow sequence block.
• On the Workflow Sequence tab, click the + icon to add a condition.
• In the Manage Conditions pop-up, you can:
• Create a new dependency condition
• Update an existing dependency condition
• Remove an existing dependency condition

3. Configure conditions using available objects

Define dependency conditions using the following available entities:

• Event Object
  • Select Event fields, field criteria, and field values
• Participant Object
  • Select Participant fields, field criteria, and field values
• Event Settings Object
  • Select Event Settings fields, field criteria, and field values
• Product Object
  • Select Product fields, field criteria, and field values
• Workflow Object
  • Select Workflow fields, field criteria, and field values
• Activities Object
  • Select Activities fields, field criteria, and field values

4. Combine conditions using logical operators

Use logical operators such as AND and OR to combine multiple conditions and define complex execution rules for workflow sequences.

5. Save and apply the dependency

• Save the configured dependency conditions.
• Publish the workflow to activate and apply the changes.