I read a couple books on WWF but still have a basic question.
If I have a Work Flow for service requests, I will want to track things like
who it is assigned to, when it was submitted, when it was closed, the current
status (submitted, assigned, closed).
This is because we are going to want to have a web page that shows: request
title for
all open requests Assigned to Bob.
How do you do this in WWF, create a database to track the fields you need to
report on, use the WF tracking stuff, or what? Prior to WWF I'd just do my
own database.
thanks,
Cowboy (Gregory A. Beamer) - 04 Dec 2007 16:35 GMT
What you are dealing with is attempting to query the persisted state of a
workflow. As a starting point, look at this free chapter:
http://www.apress.com/book/downloadfile/3386
(click on PDF link to see file)
Once you have the information persisted, you can query it. Now, this does
not show all of the metrics you wish to look at, but it should give you the
basics of the methodology.

Signature
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
*************************************************
| Think outside the box!
*************************************************
>I read a couple books on WWF but still have a basic question.
> If I have a Work Flow for service requests, I will want to track things
[quoted text clipped - 14 lines]
>
> thanks,
Chuck P - 05 Dec 2007 14:48 GMT
Bad link
> http://www.apress.com/book/downloadfile/3386
Cowboy (Gregory A. Beamer) - 06 Dec 2007 21:55 GMT
Try going to the book and clicking the download link for Chapter 08 (lower
left side of the menu area):
http://www.apress.com/book/view/9781590597781

Signature
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
*************************************************
| Think outside the box!
*************************************************
> Bad link
>
>> http://www.apress.com/book/downloadfile/3386
Chuck P - 10 Dec 2007 15:55 GMT
That was one of the books I read. The chapter didn't really discuss the
things I was interested in doing (i.e., creating web pages that query, who it
is assigned to, when it was submitted, when it was closed, the current status
(submitted, assigned, closed)).
Opening thousands of workflows using the books method would be a little slow.
I'm guessing what you should do, is when a WF is open and a task is
completed, update the db fields you will be routinely querying.
I'm also guessing the WF tracking stuff is not that great if you will be
doing querys. Doing something like get the average time a WF was open would
be a real expensive query in the db structure that is used.