Before You Begin
You must have access to create and manage workflows in Dazos
Identify all the conditions and their priority order
Determine which field will be updated and the possible values
Steps
Step 1: Plan Your Workflow
Hierarchy
Identify which conditions should take precedence over others. For example, if insurance type should override treatment program assignments, insurance-based workflows should have lower sequence numbers (run first).
Step 2: Create Your First Workflow (Highest Priority)
Navigate to Workflows in your Dazos account
Create a new workflow
Set your highest priority criteria (e.g., Insurance Type = "Commercial")
Configure the action to update your target field
In the Sequence field (usually located in the Basic Information section), enter "1" to ensure this rule always fires first.
Step 3: Create Your Second Workflow (Medium Priority)
Create another new workflow
Set your second priority criteria (e.g., Insurance Type = "State")
Configure the appropriate field update action
In the Sequence field, enter "2"
Step 4: Create Additional Workflows as Needed
For each additional condition, create a new workflow
Set the criteria for conditions that should only apply if higher-priority workflows haven't already triggered
Use AND/NOT conditions if necessary (e.g., Treatment Program = "Beauterre" AND Insurance Type ≠ "Commercial")
Set sequence numbers incrementally (3, 4, 5, etc.)
Example: Assignment Logic with Insurance Precedence
Here's how to set up workflows where insurance type takes precedence over treatment program:
Workflow 1 (Sequence: 1)
Criteria: Insurance Type = "Commercial"
Action: Update "Assigned To" field to "Beauterre Intake"
Workflow 2 (Sequence: 2)
Criteria: Insurance Type = "State"
Action: Update "Assigned To" field to "Intake Coordinators"
Workflow 3 (Sequence: 3)
Criteria: Treatment Program = "Beauterre" AND Insurance Type ≠ "Commercial"
Action: Update "Assigned To" field to "Beauterre Intake"
Expected Result
When multiple workflows could trigger simultaneously, they will execute in sequence order (1, 2, 3, etc.). This ensures that:
Higher-priority conditions are processed first
Field updates follow your intended hierarchy
Conflicts between workflows are avoided
💡 Best Practices
Always use the lowest sequence numbers for your highest priority workflows
Test your workflow sequence with sample data to ensure the precedence works as expected
Use descriptive workflow names that indicate their priority level
Consider using NOT conditions in lower-priority workflows to prevent conflicts
⚠️ Important Note
The sequence field only controls the order when workflows trigger at the same time. If workflows have different trigger criteria that don't overlap, sequencing won't affect their execution.