Try OpenEdge Now
skip to main content
Application Developer's Guide
Developing an application : Determining duration, due date, and overdue periods : Setting overdue actions in a workstep : Action details for overdue and last overdue tasks
 
Action details for overdue and last overdue tasks
The following table lists the Overdue Actions and On Last Overdue actions in detail.
Table 7. Action details for overdue and last overdue tasks
Action
Parameters
Workstep Type
Notes
For overdue actions
Send E-mail
<email-ids><subject>
<content><charset>
Activity, Adapter, and Subprocess
E-mail ID may also be specified as @DS1 to dynamically get the mapped dataslot value. Specify multiple target email-ids by using comma separated values.Using <charset>, it is possible to specify the content for default or specific character set; <content> and <charset> are optional.
Change Priority
<pri><INCREASE>
<DECREASE>
Activity, Adapter, and Subprocess
Priority can be set to a specific value or specified as increase/decrease. The increase or decrease is executed based on the numerical value of the priority.
Extend Duration
<hrs><mins><secs>
All Activities, Adapter, and Subprocessworksteps with defined duration.
When the workstep duration is less than the configured daemon time, it may be possible that, for the "Extend Duration" action, the new due date is already past when the action is executed. In this case, the workstep due date is set to the last minute of the current day (that is, 11:59:00 PM).With a nested workstep, the new due date must also be updated to the actual subprocess instance.
Execute JavaScript
<js>
Activity, Adapter, and Subprocess
Open the Script tab to enter JavaScript that is executed at each overdue.
For last overdue actions
Change Performer
<performer><mappedDS>
Activity and Flow
Reassign or make workitems available to a user that is hardcoded or a user that is mapped to a dataslot, based on the value shown in Change performer text box. Also supports JS and EJB performers. If the performer of the workstep is Single User, on overdue, then it is reassigned to another Single User. Note: Group (Any/ All ) not supported in Change Performer action.If the performer of the workstep is All members of Group, then on overdue it is reassigned to another Single User.
Group (Any/ All ) not supported in Change Performer action. For example, on overdue, task assigned to each group member is now assigned to the single user. Therefore, if the Group had say 3 members, then on overdue, the single user has 3 tasks in the list of assigned tasks.If the performer of the workstep is Any member of a Group, then on overdue it can be reassigned to a Single User or a Group (Any/All).
Note: Irrespective of the performer type, on overdue, the task is moved to the list of the new performer's "Available tasks". For example, if the original performer is "Any member of groupA, then on overdue, the performer is changed to ebms, the task is present in the Available task list of ebms.
Complete workstep
NA
Activity and Subprocess
With Adapter workstep, force complete is supported only for asynchronous adapters (ASYNC EP).