<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Disqus - Latest Comments for Maneer Khan</title><link>http://disqus.com/people/f4c1655b4c34ebc13acfde1ec92c8861/</link><description></description><language>en</language><lastBuildDate>Thu, 18 Sep 2008 12:10:11 -0000</lastBuildDate><item><title>Re: A tribute to the humble &amp;quot;leave form&amp;quot; - Part 4</title><link>http://sharepointmagazine.disqus.com/a_tribute_to_the_humble_quotleave_formquot_part_4/#comment-2424344</link><description>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. &lt;br&gt;&lt;br&gt;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?&lt;br&gt;&lt;br&gt;Could you guide us the same manner as you did with the leave form above.&lt;br&gt;&lt;br&gt;Thanks,&lt;br&gt;Maneer</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Maneer Khan</dc:creator><pubDate>Thu, 18 Sep 2008 12:10:11 -0000</pubDate></item></channel></rss>