Re: Absence Request Suggestions . . .

Patrick Halstead — Tue, 22 Feb 2011 06:06:05 GMT

Hi Shniggens,

Glad to hear you are hopping with your solution.

We've done quite a few Absence Request solutions. I guess it's kind of like a bank account - you need a ledger so you can go back and recalculate at any point. Then, if they cancel, you can just add a credit entry or something like that. The key here is to record the requests and prevent deletion. The SharePoint list can have multiple rows for each employee and each row would be the request info. You should be able to group the list and apply a Sum that calculates the total time taken. That means the starting balances should be negative so that the sum adds up correctly. You can also use this to add more vacation - it becomes a credit just like a deposit into your cehcking account.

Hope this doesn't sound too confusing...

Absence Request Suggestions . . .

shniggens — Mon, 21 Feb 2011 20:38:36 GMT

I have created an absence request form for our company using http://alecpojidaev.wordpress.com/2008/12/30/infopath-codeless-programming-walkthrough-2/ great blog to calculate the difference between dates (using an XML file to exclude holidays and weekends), QRules to submit total requested days to a SharePoint list that holds the number of total days an employee has remaining to request. This all works great.

I'm struggling to wrap my head around an ideal method of handling cancellations, changes, etc. For instance, once the user submits the form, I have QRules update the list of remaining days right away. What if the user wants to cancel? What if they merely want to adjust the days they requested?

I considered having a workflow subtract the requested days from the remaining days once the form was approved, but that still doesn't address how a user would change their request . . . or even cancel their request.

Have any of you ever developed a solution like this in InfoPath?

General

Re: Absence Request Suggestions . . .

Absence Request Suggestions . . .