From ac8a70c3f815792dba1174e9e882aacbda5bd834 Mon Sep 17 00:00:00 2001 From: Hugo Zwaal <58431933+hugomendix@users.noreply.github.com> Date: Mon, 8 Dec 2025 10:51:29 +0100 Subject: [PATCH 1/2] Conditional timer event Added a note, explaining that when the timer expression evaluates to null/empty, then the timer scheduling is skipped and execution continues with the next activity. --- .../application-logic/workflows/workflow-elements/timer.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/timer.md b/content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/timer.md index 9340c39d07e..31aac4684ad 100644 --- a/content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/timer.md +++ b/content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/timer.md @@ -56,6 +56,10 @@ The **Timer** properties are described in the table below: | Duration | You can set a certain duration for the timer. With the **Continue after** setting, you can indicate the number of seconds, minutes, hours, days, weeks or months the timer's duration is. Possible values for the setting are:
| | Expression | You can set a certain date and time for the timer by writing an expression via the **Continue at** setting.

For example, you can write `addDays([%CurrentDateTime%], 1)` to set tomorrow as the due date and time. To set a static date and time, you can use the expression `parseDateTimeUTC('2023-12-10T17:12:00.000', 'yyyy-MM-dd''T''HH:mm:ss.SSS')`.

You can also create a more complex timer. For example, you can set a timer based on a Boolean value (in this example, `isVIPUser`) from the provided workflow context entity: `if $WorkflowContext/isVIPUser then addDays([%CurrentDateTime%], 2) else addWeeks([%CurrentDateTime%], 2])`.

For more information on available expressions in Mendix, see [Expressions](/refguide/expressions/). | +{{% alert color="info" %}} +When the expression evaluates to `empty` or `null`, then no timer will be scheduled. In case of a standalone activity, execution continues at the next activity. In case of a timer boundary event, the boundary event is simply skipped. +{{% /alert %}}| + ### Recurrence Section {#recurrence} {{% alert color="info" %}} From 334388a3c1f52ac6ea79b224b91c923aca69ba0b Mon Sep 17 00:00:00 2001 From: Yiyun Liao Date: Mon, 8 Dec 2025 16:53:45 +0100 Subject: [PATCH 2/2] Language review --- .../application-logic/workflows/workflow-elements/timer.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/timer.md b/content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/timer.md index 31aac4684ad..44d85c82905 100644 --- a/content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/timer.md +++ b/content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/timer.md @@ -57,8 +57,8 @@ The **Timer** properties are described in the table below: | Expression | You can set a certain date and time for the timer by writing an expression via the **Continue at** setting.

For example, you can write `addDays([%CurrentDateTime%], 1)` to set tomorrow as the due date and time. To set a static date and time, you can use the expression `parseDateTimeUTC('2023-12-10T17:12:00.000', 'yyyy-MM-dd''T''HH:mm:ss.SSS')`.

You can also create a more complex timer. For example, you can set a timer based on a Boolean value (in this example, `isVIPUser`) from the provided workflow context entity: `if $WorkflowContext/isVIPUser then addDays([%CurrentDateTime%], 2) else addWeeks([%CurrentDateTime%], 2])`.

For more information on available expressions in Mendix, see [Expressions](/refguide/expressions/). | {{% alert color="info" %}} -When the expression evaluates to `empty` or `null`, then no timer will be scheduled. In case of a standalone activity, execution continues at the next activity. In case of a timer boundary event, the boundary event is simply skipped. -{{% /alert %}}| +When the expression evaluates to `empty` or `null`, no timer is scheduled. If the timer is a standalone activity, execution continues with the next activity. If it is a timer boundary event, the boundary event is skipped. +{{% /alert %}} ### Recurrence Section {#recurrence}