My question is how is it possible to send a form (developed in Domino Designer) via email?
I followed this guide and set up the necessary form & database properties, but when i click "Preview in Notes" i still can not forward/send my form (as an email) via a new message.
If you've followed the directions that you linked, then a button that uses #MailSend with no arguments will send the email with its stored form. But the receiving user's mailbox must have the "Allow use of stored forms in this database." property checked, otherwise the stored form will be ignored.
See my answer to a previous question for more details.
As it turns out, you can not do such. You have to send the form from lotusscript.
Related
I have a request to create a Get support button in an application.
The button will have to open the Lotus Notes application(which is installed in a generic fixed location), to auto-complete the e-mail to, subject, body of the e-mail and also, the most important part, to add an attachement to the e-mail.
I managed to open the Lotus Notes with the fields completed with the command:
mailto:support_adress#domain.com?subject=First%20Email%20&body=this is the body
The problem is with the attachement. Due to security concerns, mailto doesn't support attachements.
So the question is, can I do it with an Lotus Notes Script( which can be executed from my application)?
If yes, can anyone guide me to some usefull informations or examples to start learning to create a script which would do it?
Yes, you can do it with LotusScript:
get user's mail database
create a new document in backend
add fields "SendTo" and "Subject"
create RichText field "Body" and attach file to it
open document in UI
Someone please let me know what exactly #Command([MailForward]) command does?
In my organization, I take care of several existing notes based applications. Here, one of the users is getting error message when clicks on 'Email Quote' button in one of the applications. The button contains the formula '#Command([MailForward])'. As the user clicks on the button, he gets following error:
Here in the organization, all the users use 'Outlook/Exchange' for emails, and notes emailing is not enabled. Other users of the application are able to click the button and send quotation via mail. The issue is with this specific user only.
I think there is some configuration settings in location entry or person document (names.nsf) that I am missing. Please guide me.
Thanks
Romil Handoo
#Command([MailForward]) is a command that takes the current Notes document that you are looking at and attempts to create a new email with that document included in the body. This is similar to what you see when you forward an email in Outlook.
Since you aren't using Notes for your mail, this action will not work. The error message you are receiving is there because the current user doesn't have a Lotus Notes mail file configured.
I have create a form in Notes Designer version 9.0 and i am unable to forward this form to any users, as i do not find Forward Button under Create Menu.
Not sure if am looking at right options to forward the form, please help.
Thank You
Venu
There are two classic approaches to publishing a form for users to fill out.
Set the Store Form in Document property on the form (see here), and add mail fields (SendTo, Subject, etc.) to it. Add a button that is only visible to you and use #MailSend code in that button to send a document to the people you want to fill out the form. Add another button that is visible to the recipients, and use #MailSend code in that button to send the document back to you, or to a mail-in database. The form will accompany the document wherever it goes. (It will be stored in a field called $Form.)
Just put the form in a database on your server, and set the ACL so that your users can create documents in that database. Send an email message to all the users containing a button with code that executes #Command([Compose]...) with the options set to point to the correct server, database, and form.
Note that both of the above techniques assume that the people you want to fill out the form have Notes clients. If that's not the case, then what you'll want to do is this:
Just put the form in a database on a server that is running the Domino http task, and set the ACL so that your users can create documents in that database. Send an email message to all the users containing a link in the form http://server/path/databasename.nsf/formname?OpenForm
While sending email from lotus notes to Gmail using Lotus Script, buttons are not visible in Gmail.
As Anders says, Any standard or custom Action Buttons (at the top) will not be available in Gmail. You would need to code your own Gmail interface to reproduce.
If you are talking about buttons in the actual rich text of the mail, these will definitely not get translated when the mail leaves and you should get a message saying...
"The following items cannot be sent or saved in MIME (internet mail) format."
That would be a clear sign that you are going to need to take another look at your assumptions.
If you are planning a migration, you do need to check your assumptions (and your vendor's promises) carefully, there is a lot of infrastructure and functionality that is taken for granted in the Notes/Domino stack and just not available, or significantly different, in others.
Stored forms are a feature that is unqiue to Notes. They contain Notes design elements, formulas and scripts that execute Notes functions that are provided by the Notes API DLLs that are only available in the Notes client. GMail doesn't know anything about them. Outlook doesn't know anything about them.
But if you want to send them to someone who has a GMail address but who also has the Notes client, then there is a way to do it manually using the "Send this email to other Notes mail user(s) through the Internet" feature, which appears in the Advance tab of the Delivery Options dialog that you can bring up when sending a message. There is no simple API for automating the mechanism that is used, but it can be done. It requires creating a new empty database file with a special name (encap.ond), saving your document into that database, and then attaching the the file to a new message, which will be the one that you actually send. I don't recall if any special headers are required for this, so if you want to pursue it you will have to do some investigation by using the manual process and checking out the full headers of the message on the receiving side.
When I make a meeting in Outlook, the recipient gets a approve/reject button in the top of the email. I'd like to do a similar thing with SharePoint: when a task is created, an email is sent to the person the task is assigned to, and the email asks the recipient to either accept or reject the task. I've seen demos of people doing this with a custom ASPx page, but I'd like to make it directly in the email. How should I go about doing that?
I'm used to making workflows in Visual Studio, so I'm happy with code examples for setting up an email and/or parsing the response
Cheers
Nik
The approve/reject buttons in Outlook shows up because the email is in the iCalendar format. I dont know if this is the best way, but you can send out your own iCalendar emails using C# code and set the response email to a mail server you control. From that mail server you can process the email and use the SharePoint WebService API to approve the item in SharePoint.
I like JMD's suggestion but I don't know how you'd interact with SharePoint from the mail server.
It might be a easier to send an HTML-formatted email with two links (...) for the Accept and Reject buttons. You could use CSS to format them so that they look like real buttons.
You could then create an ASPX page (or better an IHttpHandler implementation) to perform an action based on parameters passed to it via a URL. You'd want to pass in the site, web and list details and the list item ID along with a value to indicate whether the item is approved or rejected.
Then set the URLs of your "buttons" in the email to call your handler and pass in the appropriate parameter values.
The downside to this is that the "buttons" would be part of the message body and not part of the Outlook chrome but, on the other hand, they would be usable from any email client.