Deadlines and Delays for Process Models

yuuvis® RAD designer 10.x

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.

Properties of deadlines

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:

Activity creation: Time at which an activity is created via yuuvis® RAD.
Activity end: Time at which an activity is completed via yuuvis® RAD.
Scope start
Scope end
Work item personalization: Time at which a participant in yuuvis® RAD client has accepted the activity as a task.

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:

Activity creation: Time at which an activity is created via yuuvis® RAD.
Activity end: Time at which an activity is completed via yuuvis® RAD.
Scope start
Scope end
Work item personalization: Time at which a participant in yuuvis® RAD client has accepted the activity as a task.

Cancellation points

Optional: Activity and time at which the deadline is removed.

Times, activity-dependent:

Activity creation: Time at which an activity is created via yuuvis® RAD.
Activity end: Time at which an activity is completed via yuuvis® RAD.
Scope start
Scope end
Work item personalization: Time at which a participant in yuuvis® RAD client has accepted the activity as a task.

Behavior

Behavior if instance is still running

No change
Extend the duration of the existing instance
Create a new instance

Behavior if instance has already been triggered

No change
Create a new instance

Behavior if instance has already been stopped

No change
Create a new instance

Action

E-mail notification

Notifications after end of the deadline.

Properties

Property	Comment
Send to current participants	Active: All participants receive an e-mail.
Send to current substitutes	All substitutes of the user receive an e-mail.
Additional recipients	Additional recipients from the organization.
Subject	Subject of the message
Message	Message content Placeholders can be used for the subject and content.

Administrative e-mails must be enabled and configured in order to activate e-mail notification.

Work item steps

No changes
Forward
Assign substitute
Clear personalization
Clear personalization and forward
Clear personalization and assign substitute

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.

Delay properties

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: Activity creation: Time at which an activity is created via yuuvis® RAD. Activity end: Time at which an activity is completed via yuuvis® RAD. Scope start Scope end Work item personalization: Time at which a participant in yuuvis® RAD client has accepted the activity as a task.
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: Activity creation: Time at which an activity is created via yuuvis® RAD. Activity end: Time at which an activity is completed via yuuvis® RAD. Scope start Scope end Work item personalization: Time at which a participant in yuuvis® RAD client has accepted the activity as a task.
Cancellation points	Optional: Activity and time at which the delay is removed. Times, activity-dependent: Activity creation: Time at which an activity is created via yuuvis® RAD. Activity end: Time at which an activity is completed via yuuvis® RAD. Scope start Scope end Work item personalization: Time at which a participant in yuuvis® RAD client has accepted the activity as a task.
Behavior
Behavior if instance is still running	No change Extend the duration of the existing instance Create a new instance
Behavior if instance has already been triggered	No change Create a new instance
Behavior if instance has already been stopped	No change Create a new instance
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.