You will now create the implementation of the human task component.
This action ensures that outstanding instances of this task (to-dos) will be cleaned up when the process that invoked the task is cleaned up.
By default, anyone can create instances of this human task (in other words, create to-dos), and anyone can claim those instances and work on them. However, you can restrict that. Select the Everybody cell in the Potential Owners row, and go to the Properties page. There is only one tab – Assign People. In the People assignment criteria list, select User Records by user ID as shown here:
Scroll down in the Assign People property view and set the user ID to that specified for the server at install time. If you did not change it, then it will still be admin.
In the People Assignment section you see that the table has changed:
In addition to specifying a duration for how long users have to process a task before it expires, you can also specify a series of escalation actions in case the task is not claimed in a certain amount of time after it is created (Ready state), or in case it is not completed in a certain amount of time after it is claimed (Claimed state).
Actions include creating a new to-do task for someone else, or sending an email notification. This is where you set these escalations up, using the green “plus” button when one of the state icons is selected.
There is an online sample that explores escalations.