Multi Step workflow now flowing - PWA 200[ - SP Designer 2007]

[Doug_F]

I am playing with SP Designer in a PWA site, trying to create a custom
workflow for Tasks (PWA tasks, not Project 2007 tasks). MOSS is not
installed. .Net 3.0 is installed on my dev box and on the Project server.

I built a single step workflow:
If assigned to = null, set AssignedTo to <named person>

Works great.

Added a second step
If % complete >= .67, set AssignedTo to <a different person> (*)

Workflow steps set to run in sequence.
Workflow set to start in first save and trigger at each update.
The workflow flag in the task view shows 'complete' after a few seconds.

I create a new task with no assigned person and save it, <named person> is
set.
I edit the task, set the % Complete to 70, nothing changes.
Additonally, the task view shows the workflow as 'in process' forever.
Refreshing never flips it to 'Complete'. Killing IE and restarting still
shows as in process. If I click the Workflow link, I am taken to a different
view and the workflow shows as complete.

???? I be cornfused...

I'm going to play some more. Any pointers are appreciated.

Doug

(*) The field is called % Complete. You enter data as whole numbers like 70
for 70%. The comparison value in the workflow, however, seems to want to be
the decimal value for the percent (ie .67 = 67%). I played with a single
step workflow based on the % Completed and this seems to be true.

 

[Doug_F]

Soooo... I create a new 2 step workflow.
Step 1: If status = 'Not Started' set to 'In Process'
Step 2: If % complete >= 0.85, set status to 'Completed'.

Created new task with status = 'Not Started' and the workflow set it to 'In
Process'.
Edited it, set the % complete to 90, and the workflow set the status to
'Completed'.

I'm going to start over, rebuild my first 2 step rule, and try again.

Doug

 

[Doug_F]

Rebuilt the original workflow with one change (ok 2 changes).

In the original workflow, once the % Complete crossed 65%, the task was
reassigned to me. In the revised workflow, I reassigned to <different named
person>

The second change was the step names. In the first workflow, I used 'Step
1' and 'Step 2'. In the revised workflow, I created meaningful names like
'Set Assigned' and 'Reassign'.

So the workflow is now working, BUT it is not leaving the 'In Process'
status. Ie, the workflow seems to be stuck running. It does show 'Complete'
after the initial task save but when I bump up the %Complete, it updates the
task to the second assigned to name but then seems to keep running.

Back to playing - any input on workflows is appreciated.

Doug

 

[Doug_F]

Seems I'm overly impatient...after 4 or 5 minutes, the workflow is now
showing Complete.

So now I'm going to change the second step back and try and re-assign to me
instead of another user. If that works this time around...maybe I just
wasn't waiting long enough for the rule to execute. If it doesn't work
again, then it's something about reassigning to yourself.

Doug

 

[Doug_F]

Patience is a virtue
Patience is a virtue
Patience is a virtue.

Workflow works like a charm...I keep forgetting that sometimes in PWA you
just need to wait...

For what it's worth, building workflows with SP Designer is pretty darn easy.

Now I just need to figure out how to modify default.master...that one looks
a bit more interesting.

Sorry for the multi-post ramble but I find that I prefer threads that have
lots of information and an end point. I play off-line until I get
frustrated, then search for help, then start posting...maybe I should let
problems sit overnight too...

Hope this helps somebody some day.

Patience is a virtue
Patience is a virtue
Patience is a virtue...

Doug

 

[Rod Gill]

Thanks for the Blog and your information!

--

Rod Gill
Project MVP

Project VBA Book, for details visit:
http://www.projectvbabook.com

NEW!! Web based VBA training course delivered by me. For details visit:
http://projectservertraining.com/learning/index.aspx

 

[Doug_F]

Or maybe a 'Flog' 'Forum Blog'...

Now I need to add in some drama and spice up the submissions a bit.

It was a dark and stormy night.

The server room, in contrast to the evening weather, was quite; just the hum
of drives and fans and the gentle blinking of status light - a high tech
sanctuary in the midst of chaotic nature.

Suddenly, an application crashed disrupting the peace in the room, almost as
if a glass penguin had been smashed to bits....

Sorry, can't wait for the weekend...

Doug