Leave Application Workflow Using Sharepoint Designer

Question

Hai All,

I need to create a leave application Workflow, User sends the application to the Intermediate officer (who is the application validator) tis inter mediate officer can either accept or reject the application. If the application is approved, then this leave application will forward to the decission officer.

I need to create a workflow in Sharepoint designer can anybody guide me or suggest me how to do it, plzzzz

Answer 1

A good tutorial that will help you in your learning of Sharepoint Designer workflow is the one provided by the Sharepoint Designer team here ("Training Site Template - Part 2: Workflows") .

---

Serge Luca; blog: http://www.redwood.be

Answer 2

You first need to create the "leave application" thing that you're talking about.  Is that a Word doc?  A custom list item?  An InfoPath form?  I would create an InfoPath form that has all the info and logic built in to help your workflow easily do the routing.  SPD won't just be able to do it all by itself.  You have to create the "leave application" first and go from there.

---

SharePoint Architect || My Blog

Answer 3

Hai Clayton,

actually i create an UserControl (webusercontrol) for the leave application, on the click of submit button i add those leave application datas to a custom list (say Leave application). On the leave application data which contains the reporting person. i need to send a notification to the particular reporting person and the task should be assign to him. after his approval only i need to send the leave application data to the Final decission officer.

Thanks in Advance.

Answer 4

1. Create an SPD workflow on the Custom List that is set to start automatically when a new item is created
2. Step 1 - create an action called Assign To-Do Item that is set to the reporting person field of that current item.  This will pause the workflow until the task is completed
3. Step 2 - create a condition that if the item is rejected, then send an email notification and stop the workflow.  Else, if approved, Assign To-Do Item to Final decision officer

---

SharePoint Architect || My Blog

Answer 5

Hai Clayton,

Thanx for your reply, i will check it and update you.

Thanx in Advance

Answer 6

Gets you almost all the way there but uses INFO PATH, which I guess some people use.
I like your approach to persist the data to a custom list but, of course there is a practical list item count
limit and it probably won't take too long to get there. I've written a few vacation/attendance applications.
An example, 300 person company 5 years 35,000 day records.  More if you live in a civilized part of the world.

http://sharepointmagazine.net/technical/development/a-tribute-to-the-humble-leave-form

Answer 7

You "guess" some people use?  When it's part of the Office Suite and fully-integrated with SharePoint at no extra cost and based solely on XML, then yeah, "some" people use it.

---

SharePoint Architect || My Blog

Answer 8

Yeah, I've never seen good infopath usage so I have to "guess"

The point stands, about a leave form that is limited to 2000 item persistance.
That calls into the question of the sanity of building a leave form in sharepoint at all, but the article I linked to is a very good read.

Attendance needs evaluation on a per day (or smaller) unit. The reason is the Approval is not a blind yes or no, it has to be based on something and that is usually a combination of workload, timing and similar talent that will or will not be available at the requested time. This is the realm of resource management which is much more complicated than it appears and can get highly political and personal. Using sharepoint to solve it is the "bring a butter knife to a gunfight" situation. If each employee had their own Excel sheet in a document library that was their attendance record, and that record was constantly added to and had recurring workflows "on change" that may work better, then you could let Excel Services do some lifting. At least the Excel intergation part would scale. HR staffing, Payroll and Accounting are ultimitely the consumers of the information the leave form and it's WF collects. That makes the EASE of infopath/sharpoint a little less of a priority when solving the correct problem. 
Being based on XML is irrelevent. Most of the worlds goods are ordered, delivered stocked, bought sold moved around by EDI, text is text, bits is bits. there is no XML magic that makes it better. If XML schemas were standardized beyond every individual's whim then XML would be truely useful inspite of itself.