Deadlines and Delays for Process Models
Deadlines are designed to ensure that activities or follow-ups to activities are carried out within a given time period. Delays, on the other hand, establish that activities or follow-ups to activities cannot be carried out before the end of the given time period.
Deadlines and delays are created in the Time periods view area.
Property | Comment | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Name | Deadline name. | ||||||||||||
Duration | Time period between the start and end point in days, hours, minutes, and seconds, after which an action is executed and the 'DeadlineExpired' event is triggered. | ||||||||||||
Trigger points | |||||||||||||
Start points |
Activity and start time of deadline. It is possible to have several start points. The start point reached first is valid in each case. Times, activity-dependent:
|
||||||||||||
End points |
Activity and end time of deadline. It is possible to have several end points. The start point reached first is valid in each case. Times, activity-dependent:
|
||||||||||||
Cancellation points |
Optional: Activity and time at which the deadline is removed. Times, activity-dependent:
|
||||||||||||
Behavior | |||||||||||||
Behavior if instance is still running |
|
||||||||||||
Behavior if instance has already been triggered |
|
||||||||||||
Behavior if instance has already been stopped |
|
||||||||||||
Action | |||||||||||||
E-mail notification |
Notifications after end of the deadline. Properties
Administrative e-mails must be enabled and configured in order to activate e-mail notification. |
||||||||||||
Work item steps |
|
||||||||||||
Events |
List of all events to which a script can be assigned. The button at the end of the row opens the script editor. Event 'DeadlineExpired': event handler function that can be used to implement a behavior that is defined in the script after the deadline and cannot be configured by the options above. If there is no script, only the configured actions will be executed. |
||||||||||||
Process history | List of times at which messages are logged. Enabled: Messages are shown with comments in the Progress area of the process history. |
Property | Comment |
---|---|
Name | Delay name. |
Duration |
Time period between the start and end point in days, hours, minutes, and seconds, after which the delay lock is removed and the 'DelayFinished' event is triggered. |
Trigger points | |
Start points |
Activity and start time of the delay. It is possible to have several start points. The start point reached first is valid in each case. Times, activity-dependent:
|
End points |
Activity and end time of the delay. It is possible to have several end points. The start point reached first is valid in each case. Times, activity-dependent:
|
Cancellation points |
Optional: Activity and time at which the delay is removed. Times, activity-dependent:
|
Behavior | |
Behavior if instance is still running |
|
Behavior if instance has already been triggered |
|
Behavior if instance has already been stopped |
|
Events |
List of all events to which a script can be assigned. The button at the end of the row opens the script editor. Event 'DelayFinished': event handler function that can be used to implement a behavior that is defined in the script after the delay and cannot be configured by the options above. If there is no script, only the configured actions will be executed. |
Process history | List of times at which messages are logged. Enabled: Messages are shown with comments in the Progress area of the process history. |
A permitted editing time for a work item can be configured for participants. This is displayed at the work item and marked if exceeded.