DCR 2.0 supports time.
The Condition and Response relation supports time. The graph uses time to control the Condition and Response relation.

Time in DCR graph

The Condition between Start and Activity 1 says that Activity 1 can be executed when Start has been executed and 2 time units has passed.

The Response between Start and Activity 2 says that Activity 2 must be executed no later than 5 time units after Start has been executed.

Simulation with time

In DCR process engine 2.0 this semantics is implemented. When you simulate graphs with time constraints a new

Simulation Time
When executing the Start event

Executing event

the deadline and delay is shown.

Time can be advanced by, say, 1, resulting in

Advancing time
The task panel shows the deadline for any activity

Deadlines on activities

The definition of a time unit is up to the system using DCR to define. We assume that a time unit of 1 day or 1 hour would make sense in many situations.

A typical time pattern

Time will typically be used in a pattern where there is a deadline for an activity, expressed as time on a response relation. If this deadline is not met, an exception activity will occur.

Time pattern

If the “must do event” is not completed before 4 time ticks the “Escalate” event will occur as it has the “Automatic” user assigned and is pending. Therefore the Lazy user should execute this event which will (a) exclude the “must do event” and (2) include the “handle escalation” event.