Understand Any-Order Behavior
Any-Order Behavior finds a required set of events for the same EventOwner, regardless of the order in which they occur.
For example, find applications where Identity Verified, Address Verified, and Consent Received all occurred. You can also require the matched set to occur within a specified duration.
An Any-Order query uses two baskets:
Event basket:The actions you want to find. Every required event occurrence must match.
System filter basket:Optional conditions that qualify the match, such as duration or a maximum occurrence count.
You do not connect events with arrows or add Start, End, Any, or branching controls. Where an event appears in the basket does not determine when it must happen.
Example set:Identity Verified + Address Verified + Consent Received
All these orders can match:
- Identity Verified → Address Verified → Consent Received
- Consent Received → Identity Verified → Address Verified
- Address Verified → Consent Received → Identity Verified
Other records can occur between these actions without interrupting the match. You do not need a wildcard. Unrelated records are ignored rather than included as required actions in the matched set.
When to use it:Use Any-Order when the required actions matter, but their order does not. Use Sequence Behavior when you need to enforce which action happened first.