The basic worklist in Workspace can be configured to use the Overdue column (ActivityInstance.Overdue) to show when an event has gone beyond it's expected duration. The expected duration of an event can first be set as part of the General Properties of a User Event when designing a workflow. More information on that is available here:

http://help.k2.com/onlinehelp/K2blackpearl/UserGuide/current/webframe.html#RTM_Reference_-_Default_Activity__General_Properties_.html

Once an event has an expected duration, the Overdue column will rate it based on when it was started, either Available (Green), Due (Yellow), or Overdue (Red). While an event is within is expected duration, it is considered Available and has a green flag. Once it hits the expected duration, the flag will turn yellow and the event will be considered Due. 24 hours after it is set as Due, the event is considered Overdue and is given a red flag. More information on these flags is available here:

http://help.k2.com/onlinehelp/K2blackpearl/UserGuide/current/webframe.html#K2_Worklist-My_Worklist.html

Once the expected duration is set up, the worklist can be configured to sort by the Overdue column. Follow this guide on how to do it:

http://help.k2.com/onlinehelp/K2blackpearl/UserGuide/current/webframe.html#Columns_Tab.html

Unfortunately, this robustness does not extend to the Worklist Control available in SmartForms as well as the Worklist Webpart for SharePoint. It is limited to the four columns that are visible in the control to sort the the list and the Overdue column is not available in the Filtering. As such, if you would like to sort by Overdue in a Forms scenario, I would suggest instead creating a List View using the Event Instance SmartObject. Its contents is available here:

http://help.k2.com/onlinehelp/K2blackpearl/UserGuide/current/webframe.html#Reference-WorkflowContextBrowser_EventInstance.html

This SmartObject gives access to both the Start Time and the Expected Duration. As such, you could easily filter the list based both on the current user and whether the item is due by adding the expected duration to the start date.

I see the Duration field on the Event Instance smartobject, but not the expected duration.  Do I need to build a composite smartobject with the Activity Instance smartobject?

Or are expected durations only applied to the entire workflow, and not the individual user tasks?

Also, it is important to remember the concept of a DUE DATE does not exist in K2. Expected duration is only an amount of time that things are expected to take, but that isn't in a date format but rather in a span of time.

To get a due date, you would have to calculate the expected duration (which is a design time value that is hard coded) perform some date manipulation based on the start date of the process or activity depending on where you are measuring expected duration.

In that scenario, I would consider just calculating a due date and setting it to a data field. Storing that off in a smartbox based smart object along with some sort of Foreign Key value (such as serial number) that you could then join task information and the calculated due date together.

Out of the box, there isn't any place due date is calculated or exposed in a way that can be used in the manner you seek.

S.