Duration Equals

This task is a conditional comparison tool. It checks whether two Duration variables are equal and returns a boolean result — true if they match, true if both are null, and false if only one is null.

Use Case: SLA Compliance Validation

Imagine you're processing EDI transactions and your integration ruleset needs to verify that the actual processing time for a shipment matches an expected or contracted service duration (e.g., a 48-hour lead time agreed upon in a trading partner agreement).

You could:

1. Calculate the actual duration between order receipt and shipment confirmation and store it as SourceDuration1.
2. Store the expected SLA duration (e.g., 48 hours) as SourceDuration2.
3. Use Duration Equals to compare the two. If it returns true, the shipment met the SLA exactly; if false, trigger an alert or downstream workflow to flag the discrepancy.

Other scenarios where this action is useful include:

• Routing logic: Branch a ruleset differently depending on whether two time intervals are identical (e.g., retry intervals, polling cycles).
• Deduplication checks: Confirm that a calculated time window matches a known interval to avoid processing the same file twice.
• Data validation: Ensure a duration field parsed from an inbound document matches an expected fixed value before passing it downstream.

In short, it's most valuable anywhere you need precise, conditional logic based on time interval equality within a ruleset.