Set up timeout duration for processes in Identity Manager

This article is valid for Smart ID 20.11 and later.

This article describes how to set a timeout for a process task in Smart ID Identity Manager, in order to execute an action if a user has not finalized a user task after a specified time.

For example, this could be used in a user task in an approval step process, where the request is to be rejected if the task hasn't been approved within the specified time. Another example is when a shown form with an error message can only be accepted when the user clicks OK. Then the task could be finished after the timeout. 

Step-by-step instructions

Timeout durations can be set in different tasks. There are two ways to set timeouts in Identity Manager, either a local timeout for a specific task in a process, or a global timeout that can be used in all processes. 

Set global timeout duration

To set a global timeout duration:

1. Log in as an administrator to Identity Manager, and go to the Admin tab. 
2. Select Configure system properties and then Timeout for running Processes.
3. Set a Timeout duration, according to the table below, and save it. The default value is PT2H (2 hours).
   

Set timeout for a process task

1. In Eclipse, select the process and then the task that shall have a timeout attached to it. 
2. Add a Timer Boundary Event to the task and configure it as follows:  
   
   1. Go to Properties > Main config. 
   2. In Time duration, specify the time. As soon as the process step is reached, the timer starts counting down and as soon as the specified time has passed, the trigger will happen. Do either of these options:
      1. Enter the time in minutes, hours or days, according to the table below. 
      2. Enter the juel-Expression: ${timeoutDuration}. 

Time duration value examples

The time duration must be set up according to the specification in https://en.wikipedia.org/wiki/ISO_8601#Durations. 

Here are some example values: 

Example image

This image shows some examples of tasks with a Timer Boundary Event: