D
Dave
Hi;
I'm evaluating InfoPath as a replacement for a ton of forms we currently
have in Outlook. Some of the functionality we need for various forms are:
1. When submitted, the completed form is emailed to someone for
review/manual action. Is this possible within InfoPath itself or does the
forms "submit" action have to call a script or web service to do this work
for it? If so, do we have to design these ourselves from scratch?
2. Access to our Outlook address book from within the form so users can add
addressees (for example, adding their supervisor to a vacation request form
in addition to the "vacation person" who gets the form by default).
3. The ability to "daisychain" emailing of the form when multiple approvals
are required. As an example, person A would submit a form requesting
something and it would go to person B. Person B would approve and the form
would move on to Person C. Person C would approve and the form would go to
whoever processes the request, or C would deny, add a comment, and the form
would return to Person A with the appovals/denials/comments.
Can InfoPath do these things, and just as important, is it relatively easy
to set up?
Also, InfoPath's Help only states that an XML file is created when someone
fills out a form. What happens when, 10 minutes later, someone else fills
out the form? Is the new info appended to the XML or does it overwrite?
Also, I assume the XML file is placed where the form resides, say in a shared
network directory? How are these files managed? Do they simply pile up, do
they get purged somehow?
Thanks for any advice, )
Dave
I'm evaluating InfoPath as a replacement for a ton of forms we currently
have in Outlook. Some of the functionality we need for various forms are:
1. When submitted, the completed form is emailed to someone for
review/manual action. Is this possible within InfoPath itself or does the
forms "submit" action have to call a script or web service to do this work
for it? If so, do we have to design these ourselves from scratch?
2. Access to our Outlook address book from within the form so users can add
addressees (for example, adding their supervisor to a vacation request form
in addition to the "vacation person" who gets the form by default).
3. The ability to "daisychain" emailing of the form when multiple approvals
are required. As an example, person A would submit a form requesting
something and it would go to person B. Person B would approve and the form
would move on to Person C. Person C would approve and the form would go to
whoever processes the request, or C would deny, add a comment, and the form
would return to Person A with the appovals/denials/comments.
Can InfoPath do these things, and just as important, is it relatively easy
to set up?
Also, InfoPath's Help only states that an XML file is created when someone
fills out a form. What happens when, 10 minutes later, someone else fills
out the form? Is the new info appended to the XML or does it overwrite?
Also, I assume the XML file is placed where the form resides, say in a shared
network directory? How are these files managed? Do they simply pile up, do
they get purged somehow?
Thanks for any advice, )
Dave