This documentation supports the 20.02 version of BMC Helix Platform.

To view the documentation for the current version, select 20.08 from the Product version menu.

Adding a Timer event to a wait step

A Timer element interrupts a wait step and let the process make a decision about how to proceed after the wait step times out. This element can be used only with the User Task and Receive Task elements that are termed as wait steps.


Application business analysts can customize the objects developed in their own applications and that are marked customizable by the developers, but cannot customize the objects developed in com.bmc.arsys. For example, objects in core BMC applications like Foundation, Approval, and Assignment cannot be customized.

To add timer event

  1. Log in to BMC Helix Innovation Studio and navigate to the Workspace tab.
  2. Select the application in which your process exists.
  3. In the application, click Processes tab.
  4. Click the process name where you want to add events.
    The system opens Process designer and displays the process diagram on the canvas.
  5. To add Timer event in the process, perform the following steps:
    1. On the canvas, drag and drop Timer event to the User Task element or the Receive Task element as per the process requirements.
    2. In the Properties pane, enter the timer description, select the Timer Type

      Time Type describes the time within which a task must be completed before the system ends a task.

      • Interval Timer: Time specified in months, weeks, days, hours, and minutes. 
        If you select Interval Timer, provide the Interval Definition value.
      • Time Expression: Time specified as a timevalue expression.

        You can use any of the following values in the expression:

        • Current time: Specifies that the event should be triggered at a future time. 
        • Current time and an integer: Specifies that the event should be triggered after specific time (in seconds) from the current time. For example, when you specify Current Time + 1000, the event will be triggered after 1000 seconds from now.
        • Current date: Specifies that the event should be triggered at a specific date. For example, if you schedule the timer to 30 March, the event will be triggered on 30 March at 00:00:00 hours.
        • Current date and an integer: Specifies that the event should be triggered on a specific date in the future. For example, if you schedule Current date + 2, the event will be triggered after 2 days from the current date. 
  6. Click Save.

The following image illustrates an example of a timer event:

Related topic

Defining the application business logic through processes

Was this page helpful? Yes No Submitting... Thank you