Inbaskets

Hi Tommy -

Take a look at the WFMETRICS table within LOGAN - that contains the information you are seeking. I actually built a solution for a client about 2 years ago to do exactly what you are seeking. WFMETRICS contains most of the data you will need, or you can build your own custom table derived from WFMETRICS etc. This client used the reporting solution I built so the user could pinpoint (at any given time), whose inbasket contained the workunit. No more calls back to Finance or Procurement asking "where is my requisition". :-).

Escalation is the way to move workunits from one inbasket to another - take a look at the user action node configuration.

We built 2 custom batch programs. The first one shows, by workunit, who the originator was, each IB a workunit has been in/where it's currently sitting. Also shows how long a workunit has been sitting in a IB.
The second program handles all our escalations. We didn't like how PF handled escalations (up 1 level and stop), so we created our own process. Our process will climb from the janitor to the CEO, up the HR Supervisor chain.

I am also interested in this topic. I was querying the table WFMETRICS (from the API Builder in Process Flow if that matters) and it seemed to me that the work units I could see where those that have already been completed.
I am much more interested in the ones that are not completed and sitting in (someone who I'm trying to find)'s inbasket.
Any help/suggestions?

Unprocessed approval tasks only sit in WFMETRICS table when the work is assigned to a user instead of assigned to a task. Unprocessed approval tasks (at the Task level) should be in the WFQUETASK table.

Thanks, that is helpful. Now, I am using a work category to filter within the task to make the req go to the correct user via assigning that user to a task but filtering by the oCat value...
So by looking in WFQUETASK I can now see which task the unprocessed work unit is currently at, but is there a way I can dig even deeper to see the actual user it is assigned to within the task?
Does that make sense?

Thanks guys. This came in handy for something I am building.