Comments on: A tribute to the humble “leave form” – Part 4

By: A tribute to the humble leave form – part 6 | SharePoint Magazine

A tribute to the humble leave form – part 6 | SharePoint Magazine — Fri, 06 Nov 2009 08:45:07 +0000

[...] MSWord based form. We then added some data entry controls and tidied up the formatting. In part four, we published this form to SharePoint [...]

By: seotest

seotest — Thu, 04 Dec 2008 01:39:08 +0000

thanks, i like your concept, please keep in touch

By: pculmsee

pculmsee — Sat, 04 Oct 2008 07:57:01 +0000

Hi Maneer, only just saw this comment sorry.

I will be addressing this issue in future articles, but not necessarily in the way you are imaging. It's kinda hard to explain now, but stick with me and we will eventually get there

By: Carmos

Carmos — Fri, 26 Sep 2008 10:59:17 +0000

Paul, thanks for the walkthru. I have my Leave Form working and look forward to further installments. Must be an Aussie thing coz I enjoy the humour. Hitting your blog now.

By: Maneer Khan

Maneer Khan — Thu, 18 Sep 2008 23:10:11 +0000

The topic. A tribute to the humble “leave form” was interesting indeed and provide guidlines for amature sharepoint users like me to get a grip of such forms. However i would also like to shed light on complex forms, which are required by major corporates to be embedded in the same manner as the one listed.

If for example in the leave form we add sections; one for employee to fill; second for the manager to approve; third for the HR department to evaluate and finally a user who can simply view the form. Now the question arise how can we prevent each entity not to interfare in sections not related to their domain. I mean user must not be able to fill in the approval section for manager and similarly the HR section. How can we overcome such obstacle in infopath forms?

Could you guide us the same manner as you did with the leave form above.

Thanks,
Maneer