Thank you all for an incredible response! The microsoft website was 
particularly useful. There was no way for me to rummage up a workflow at short 
notice.. so with some negotiation, I am going on a Sharepoint Designer course 
in London in July :) Yipppeee!
 
Uzma


Subject: RE: [OzMOSS] 3 Step WorkflowDate: Fri, 23 May 2008 09:35:43 +1000From: 
[EMAIL PROTECTED]: [email protected]






You should get everything you need to learn from this article. It’s very 
detailed, involves several core SharePoint methodologies, and can all be 
achieved OOTB with a little help from SP Designer.
 
http://office.microsoft.com/en-us/sharepointdesigner/HA102564171033.aspx
 

Regards,Paul
Online Developer, ICTCEO Sydney


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tamlyn KempSent: 
Friday, 23 May 2008 9:32 AMTo: [EMAIL PROTECTED]: RE: [OzMOSS] 3 Step Workflow
 
Hi.  This sounds like something that SPD could do quite well, and OOTB.  
 
However you’ll have to use it to create tasks using the Collect Data From a 
User action.  This uses a tasklist.  You then need to tell the workflow in 
subsequent steps to reference the outcome of the task field and use the List 
Item ID which is outputted to a workflow variable to interrogate the result of 
the task.
 
In the first step you’d create a Collect Data From a User task, assigned to the 
value of ‘Reviewer1’ which you set up as a person field.
In the second step you have a conditional branch.  If it’s fine you update the 
Approval field with something and then carry on to the next step of Approval.  
If it needs work you can send an email to the ‘user who created the current 
item’ with the comments from the reviewer.  Then stop the workflow.  Once 
they’ve updated they can manually re-start it.
 
In the third step, if it has been given the thumbs up by Reveiwer1, you could 
have a Reviewer2, or whatever.  You could even ask reviewer 1 to assign a 
Reviewer2.  Then if it’s got a value get them to review it, if it’s null skip 
it.
 
Eventually you can get to the actually approver.  Send them a task, and based 
on the outcome of that set the ‘Approved’ field in the document library, and 
send an email to the Person Who Created The Current Item.
 
Done.
 
Drawbacks:
SPD doesn’t do loops, if you want that then Nintex is good and lightif you’re 
thinking no-code, otherwise K2 but that’s pretty heavy.
Using the content of a task in the workflow requires using the Workflow 
Variable (accessible through Workflow Data) to do the match.  It can be 
confusing getting it to work for the first time.
The only way to surface information gathered in a task is through an email.  
You can’t insert it into a later task.
 
But hey, it’ll get you 80% of the way there with no code at all.
 
If this is really confusing, let me know and I’ll have a play and send some 
screenshots.
 
Tamlyn 
 
 
 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matthew 
CosierSent: Friday, 23 May 2008 10:19 a.m.To: [EMAIL PROTECTED]: RE: [OzMOSS] 3 
Step Workflow
 
If it’s purely workflow related, you would be better off going to a WF course 
and learning how to build them properly, outside of SharePoint designer.  That 
is, if you’re a developer.

Matthew CosierDev Centre Lead
M: +61 401 932 250 | E: [EMAIL PROTECTED] Blog: http://cosier.wordpress.com
 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Uzma NazSent: 
Friday, 23 May 2008 5:08 AMTo: [EMAIL PROTECTED]: [OzMOSS] 3 Step Workflow
 
Hey all,  Thank you so much for all the support you guys have given me so far.  
I have had 2 weeks instensive one to one training on Sharepoint and I had my 
first "solo flight" with the system and I am just amazed with what I can do 
with this product.  There is a requirement in another portal that is created 
that a document needs to go through a 3 part workflow.  For example:  Author 
creates a document and once happy with the document, checks it into MOSS.  The 
document is now in Draft Approval state.  The author then starts the approval 
workflow, which sends the file to a particular person for a peer review.  The 
peer reviewer looks at the document, suggests changes etc. and it is sent back 
to the author.  The author then sends the document to their manager (would be a 
normal approver), to get the document published as "Approved".  I have had a 
look at the out of the box workflow, the 3 step workflow and Heather Solomon's 
blog and cannot get to where I want. I have everything else perfected, content 
types, security... but this is the biggest snag.  I have Sharepoint Designer 
and understand some basics. Can anyone help me with this? I know it's quite a 
lot to ask, as I have an important presentation in about 12 hours time. It 
would give me great brownie points to have this workflow almost there, not 
totally complete, but at least started.  If I can get this done, I'll be able 
to go to a 5 day residential Sharepoint Designer course and save the company 
£75K (according to the Project Manager!)...  Will appreciate any help.  Uzma 



Get Started! 
______________________________________________________________________This 
email has been scanned by the MessageLabs Email Security System.For more 
information please visit http://www.messagelabs.com/email 
______________________________________________________________________
------------------------------------------------------------------- OzMOSS.com 
- to unsubscribe from this list, send a message back to the list with 
'unsubscribe' as the subject.Powered by mailenable.com 
______________________________________________________________________This 
email has been scanned by the MessageLabs Email Security System.For more 
information please visit http://www.messagelabs.com/email 
______________________________________________________________________
------------------------------------------------------------------- OzMOSS.com 
- to unsubscribe from this list, send a message back to the list with 
'unsubscribe' as the subject.Powered by mailenable.com 
------------------------------------------------------------------- OzMOSS.com 
- to unsubscribe from this list, send a message back to the list with 
'unsubscribe' as the subject.Powered by mailenable.com 



____________________________________________________________________________This
 e-mail is intended for the use of the addressed recipient(s) only and may 
contain confidential and privileged information. If you have received this 
message in error, please delete the message and any attachments and copies 
immediately; and notify the sender by return e-mail.Any views expressed in this 
message or any attachments are those of the individual sender and do not 
necessarily represent the corporate opinion of the Catholic Education Office 
(CEO), Sydney.The CEO Privacy Policy is located at 
http://www.ceo.syd.catholic.edu.au____________________________________________________________________________
 
------------------------------------------------------------------- OzMOSS.com 
- to unsubscribe from this list, send a message back to the list with 
'unsubscribe' as the subject.Powered by mailenable.com 
_________________________________________________________________

http://clk.atdmt.com/UKM/go/msnnkmgl0010000002ukm/direct/01/


------------------------------------------------------------------- OzMOSS.com 
- to unsubscribe from this list, send a message back to the list with 
'unsubscribe' as the subject.

Powered by mailenable.com

Reply via email to