InfoPath 2010 came with a lot of promises for developers, Being a part of the Technical Preview team for InfoPath 2010, I will try to higlight main features that I found out to be part of InfoPath 2010.
1) Single click Publish:
2) Rules Management, copy pasting of rules.
3) Creating forms for sharepoint lists.
4) New controls like people picker, time and date control
will write the rest of the blog tomorrow
Monday, April 5, 2010
Friday, April 2, 2010
Differences between Browser enabled and Client forms
The first thing that is ask before designing a form is whether the form is going to be browser enabled or client form. The answer to this question seals the fate of many features that are never proposed or better to say not even thought of. The differences between these two form types are many. while as client forms offer many more versatile features, the browser enbled forms offer large coverage and is cost effective. Below are some of the differences between browser enabled and client forms.
1) Browser enabled forms require InfoPath Form Services to be installed on the server, While as client forms require infopath client to be installed at the user's end.
2) In Browser enabled form templats we can use sharepoint Object model code to communicate to sharepoint, Client form templates dont support it.
3) Client forms support cross site and cross server connectivity, that is lacking in Browser enabled forms.
4) Client forms support Picture Control, Browser enabled ones dont.
5) Client forms support header and footer sections on printed forms, Browser enabled ones dont.
6) Message boxes are supported in client forms only.
7) in client forms there is direct provision of supporting save, saveas using managed code, not avaiable in Browser enabled ones.
1) Browser enabled forms require InfoPath Form Services to be installed on the server, While as client forms require infopath client to be installed at the user's end.
2) In Browser enabled form templats we can use sharepoint Object model code to communicate to sharepoint, Client form templates dont support it.
3) Client forms support cross site and cross server connectivity, that is lacking in Browser enabled forms.
4) Client forms support Picture Control, Browser enabled ones dont.
5) Client forms support header and footer sections on printed forms, Browser enabled ones dont.
6) Message boxes are supported in client forms only.
7) in client forms there is direct provision of supporting save, saveas using managed code, not avaiable in Browser enabled ones.
Subscribe to:
Posts (Atom)
