Send to Mail Recipient as Button Function - InfoPath Dev
in

InfoPath Dev

Send to Mail Recipient as Button Function

Last post 12-15-2006 08:49 AM by dfurlong. 5 replies.
Page 1 of 1 (6 items)
Sort Posts: Previous Next
  • 09-20-2005 09:10 AM

    • Irmgard
    • Not Ranked
    • Joined on 09-20-2005
    • Germany
    • Posts 2

    Send to Mail Recipient as Button Function

    Hi All,

    this is the first time for me in this very interesting forum.
    I work with InfoPath for 1 month and I try to put the command "send to mail recipient" on a button control.
    The same function is already built in the standard sample form "issue tracking".
    I already had a look into the form code of the button "send as e-mail" and tried to translate it into my template but I did not succeed in it.
    I have made several data connections as the form has to be sent stepwise to several persons. I also included view rules with user rules. But as we want to handle the form it requires in our case that the fields should be put into the mail header (as it is in the form sample issue tracking".
    Is there anybody who can tell me how to solve this?
  • 09-21-2005 12:28 AM In reply to

    Re: Send to Mail Recipient as Button Function

    Hi Irmgard and welcome to our forum,
    We would be happy to help out here but we need to understand your requirements a little better first. It sounds like you need to send e-mail to multiple people in a specific order. You can set rules to submit to each e-mail data connector based on some kind of workflow status to control the stepwise functioning. What is the current problem? Does it send at all, or is it a matter of sequencing the sends? If you feel comfortable, please feel free to send a sample of your form to [email protected] and we'll take a quick look.

    Patrick Halstead [InfoPath MVP]
    InfoPathDev
    Patrick Halstead
    Project Manager at Qdabra
  • 09-21-2005 04:09 AM In reply to

    • Irmgard
    • Not Ranked
    • Joined on 09-20-2005
    • Germany
    • Posts 2

    Re: Send to Mail Recipient as Button Function

    Hi Patrick,
    thanks for the quick reply.
    I will send you a sample to the support's e-mail address.
    What I did is as follows:
    We have a from "request for vacation". This should be filled out by the applicant. Therefore I created a default view (Urlaubskarte). After filling out he should send this to his supervisor (this is actually realized by a submit button). Supervisor receives the request and accepts (or declines) this. On receipt he has a defined view (Vorgesetzter). By choosing the button "genehmigt" (or "zurückweisen") he forwards the request to the human resources department (or back to the applicant).
    Then the HR dept. receives the request (view: Resturlaub), finding out all data, put the data into a special HR-system and sends back a form to the applicant with the remaining vacation days.
    Presently the design of all views is not yet finished.
    I defined also user rules as well as submit buttons.
    But when submitting the form I would like that the form is to be found as e-mail attachment and the view within the e-mail is the actual view. Thus all participants especially the HR dept. are able to additionally choose e-mail addresses out of Outlook (2003) and when receiving the e-mail (before opening the attachment) they also have a first look on the first view.
    This function is the one that I found in the MS sample template "issue tracking".
    That is really the only thing: I don't want to use the submit button I want to use this e-mail function.

    I hope that I could make this thing clear for understanding.
    Thank you in advance


  • 06-23-2006 11:05 AM In reply to

    Re: Send to Mail Recipient as Button Function

    Irmgard,

    i have developed 2 forms with the same functionality that are inquiring about. I noticed that this is a quite old post, so you may have this figured out already. I used the rules of the submit button to determine which data connection to use. It also has 2 buttons for each section, one for approved in which case the form is submitted on to the next level of approval and denied which would submit the form back to the originator. If you still need help on this, I can help. Just post your reply back here.
  • 06-23-2006 12:18 PM In reply to

    Re: Send to Mail Recipient as Button Function

    Another suggestion for a more dynamic data connection would be something i found was helpful to me as a solution.

    I have a dropdown list that comes from a data connection.

    the data connection is part of a sharepoint list that is created and maintained throughout the month or year. it is a contacts list. i pull two parts from the contacts list. the name and the email address. when i make my dropdown list i use the data connection to populate the list. in the display field i use the name, and in the value field i use the email address.

    i then create a submit email data connection that uses the dropdown lists value for the send to field in email.

    I attach a button and use the data connection to submit, whatever the dropdown box it listed as it will send to that selection. I use this for multiple forms i have created so there is only need to make and update one list in sharepoint. This does not need to use sharepoint, any database list could work as well.


  • 12-15-2006 08:49 AM In reply to

    Re: Send to Mail Recipient as Button Function

    I know this is an older thread, but I am having a similiar issue. I have a form that a user 'submits' and it goes to three e-mail addresses wiht a specific subject line. That worked right off with no difficulties.

    I then chose the button off the controls and placed 2 more buttons side by side. I set up two more data connectors and associated the one I called Approve to the first button, and then the reject data connector to the Reject button.

    Unfortunately whenever I change something on one button, it impacts all of my buttons. How do I keep the buttons from linking to one another?
Page 1 of 1 (6 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.