Enhancement: New Define Comparison Operator Available in Workflows

Announcements Product News
, ,
1

:sparkles: Description

Workflows now includes a Define Comparison operator that lets you build richer conditions in a single step. Instead of chaining many separate comparisons, you can combine multiple criteria and condition groups using logical operators to control exactly when a path should run.

:red_exclamation_mark: Problem

The workflow builder supports only one comparison per operator node. Users can create complex comparisons in JSON, but the builder cannot render that logic in the UI, which makes ongoing edits and troubleshooting difficult.

:light_bulb: Solution

  • Add a single Define Comparison operator to evaluate multiple comparison types together (for example strings, numbers, timestamps, and booleans).

  • Build logic in a guided Basic experience with condition groups, AND / OR, and optional NOT.

  • Use Add Criteria and additional groups to model complex nested decision logic in one place.

  • Switch to the Advanced tab to view and edit the JSON representation of your condition.

:busts_in_silhouette: Who is affected?

Customers using Workflows who need more advanced conditional logic and want to simplify branching decisions.

:date: Important dates

  • Sandbox availability: Available Now!

  • Production rollout: Available Now!

6 Likes
2

I noticed that the String comparison operator type is missing the “Matches” operator in the criteria. Is that intentional? Otherwise this is very exciting. Can’t wait to start using it.

3

Agree with you @MattUribe

I believe the “matches” operator should have been included among the available list of operators, as it offers greater flexibility by allowing us to define custom conditions using regular expressions

4

@Arshad @MattUribe You can use the “Equals” drop down for matches as they behave the same way in workflows.

5

Having AND/OR condition groups in a single operator is a solid improvement. The Advanced JSON tab is a nice touch too, useful when the UI gets in the way. Good to see this added, thank you @Takato

6

@Takato Can you confirm whether the “matches” operator in “Define Comparison” operator supports regular expressions?