Hotspot Button

HCL Domino Domino Forum
1

Hi all,

I am creating hotspot buttons in a new memo.

  1. How can I have the answers/ replies sent not only to myself, but also to those who clicked on the buttons? So that they can also have a copy of their replies.

Current formula/ function that I have:

email:=yemailaddress”;

@MailSend(email;“”;“”;@Name([Abbreviate] ; @UserName + " has chosen Yes " ));

@Prompt([Ok] ;“Finished” ; “Thank you.”)

  1. Can I prevent my users from seeing the formula/ function as it seems that recipients can see them if they edit the button?

Thank you so much.

2

Subject: Hotspot Button

Not sure if you can stop the users from seeing the formula. But for the first question, just specify the @Username in the copyTo parameter. Also, your first right bracket should to be after the @Username, not after the ‘Yes’. So you could change the line to read:

@MailSend(email; @UserName;“”;@Name([Abbreviate] ; @UserName) + " has chosen Yes " );

3

Subject: RE: Hotspot Button

Hi,

It works. Greatly appreciated. Thank you.

4

Subject: Hotspot Button

Why don’t you describe a little bit more what it is you are actually trying to do? Perhaps give a little background.

To me it sounds like you are attempting to create a survey of some kind, possibly with multiple answers in each survey (as you write “buttonS” in plural).

If that is the case, there are much better ways to solve the problem. I would not use a memo, but a custom form that is being sent as a mail. That form have a number of fields (checkboxes, dropdowns, textboxes, whatever you need) as well as a submit button. That button will contain code to mail the results to you, as well as a copy to the submitter (person filling out the survey).

5

Subject: RE: Hotspot Button

Hi,

Thanks for the reply. Greatly appreciate.

Basically, there is a series of events/ programs organized for the recipients. I’m trying to ask them if they will be attending. If not going, why not (reason for record purpose)?

By the way, I’m newbie to lotus notes. Only know how to create Yes/ No buttons with input box (for reason).

Didn’t know that forms can be created.

What you have mentioned seems great - a custom form that is being sent as a mail with number of fields (checkboxes, dropdowns, textboxes, whatever you need) as well as a submit button.

How can I do it? And would this type of form allow the recipients to specify their preferences (which are their first choice/ 2nd choice)? It would be great if possible.

Thank you.

6

Subject: RE: Hotspot Button

You may want to take some classes in Notes development, or even pick up a book. Since you are still on Notes 6 (or 7) “Lotus Notes and Domino 6 Programming Bible” by Rocky oliver, Brian Bentz and several other well-known Notes developers is a great pick:http://www.amazon.com/Lotus-Notes-Domino-Programming-Bible/dp/0764526111

You can solve this problem in several different ways. It is exactly this kind of things Notes is realy good at.

This is how I woudl have solved it:

Create a new database to hold the responses.

Create a survey form (the form where the users select the events they will attend, and reason for not going).

On the save/submit button, you add some code that will take the responses and build a number of new documents, using another form (let’s call it “Event Response”).

Each event response document will contain the name of the user, the name of the event (perhaps you have an event ID as well?), the response (attending/not attending) and the reason for not attending.

So if there are 5 events on the survey/sign-up form, you create five separate documents.

Thsi way it will be much easier later to generate views/reports of what events specific users attended/declined, etc.

The original survey form does not need to be saved after you save all the values/choices to the event response documents. But you could save it as a history, if you like.

Now when you have this database built, simply mail the survey form to the users. Make sure you used the option “Store form in Document” on the form.

Just make sure your code in the submit button point to the correct database.