Timer events can either be added to the process flow by themselves, or they can be added within an Appian Smart Service to trigger an Exception Flow or an Escalation. In the process flow, timer events can be used to schedule a process activity, or to only continue the flow when certain conditions are met. (If the event is configured in an escalation or an exception, the configuration settings list different wordings.)
- The delay or schedule added to an activity or a process flow only begins once the node or event has been activated.
- The timer event must be active in order for the schedule to be triggered. If an End Event is configured to terminate the process, the timer is also terminated.
Configuring a Timer Event
- In the Process Modeler Palette, click the Activities category.
- lick the Timer node and drag it onto the Process Modeler canvas.
- Configure the Timer node.
- Double click the Timer node on the Process Modeler canvas.
- Right-click the Timer and select Timer Properties.
- The Timer Event dialog box is displayed.
Click the Setup tab.
- Use the Scheduled Delay group of options to set a timed delay (either by entering a number or using a logical expression). This option is selected by default.
- To enter a timed delay, type a number in the first timed delay field (or click the Expression Editor button to use an expression). Select Minute(s), Hour(s), Day(s), or Month(s) from the time-span list.
- TIP: To keep timer events from counting weekends, use the caladddays() function.
- For example, if you want to trigger an event after four days, excluding weekends, enter the following expression in the Delay for field:
- (Optional) You can click the Delay until option to enter a future date and time.
- To set a future date to resume the process, type a date and time using the following format:
dd/mm/yyyy hh:mm a.
- Click the Expression Editor button to calculate a date using one of the date and time functions available on the Functions tab.
- (Optional) Click the Timer Recurrence option to trigger the event on a repeating schedule by selecting from the following options:
|To repeat the task
|Every n number of days, every weekday, or at a certain time of day, in a specific time zone.
|Every n number of weeks, at a specific time and time zone, on a specific day of the week.
|At a certain time, in a certain time zone, on the nth day of the nth month, or on the nth day of the week (such as the 3rd Sunday) of the nth month.
|At a certain time and time zone, every year: on the nth day of a month, or on the nth day of the week(such as the 3rd Sunday) of the nth month.
|Every n number of minutes (minimum 5 minutes) or n number of hours.
||At an interval
Configuring the Time Zone Used
The time zone used in a recurring event can be configured in the following different ways.
- You can configure the time zone context for each process of a process model in its Process Model Properties. This is indicated by the timezone process property (pp!timezone) listed as a default value of the expressionable combination box in the Timer Recurrence group box.
- You can also type the name of a time zone ID to use in the expressionable combination box. When selecting a Continental US time zone, we recommend using the following standard time zone IDs.
||Time Zone ID
The available time zone IDs appear using autocomplete.
- You can create an expression that returns the proper time zone to use, using the Expression Editor.
Creating a Timer Condition
- Select the Show Advanced Options checkbox in the lower margin of the Timer Event dialog box. The Timer Conditions group of options is displayed.
- Click the New Condition button on the toolbar. A row is added to the Event Conditions list, containing three fields to configure.
- Click the first list box and select the process variable you wish to use for comparison.
- In the second list box, select the operator you wish to use for the condition. The following options are available.
||not equal to
||less than or equal to
||greater than or equal to
- In the third condition field, type the value you wish to compare against a process variable. If these values match, the condition evaluates as true and the timer event starts.