Mark Buelsing
river guide
Posts:241
 |
| 09-15-2011 05:14 AM |
|
I am getting a ton of use out of Dynamic Forms. Great product Data Springs!
Here is my question.
Is there a way I can make a DF form that I could expose to my users that would allow them to change the to: address of a completion event dynamic email?
I would also like to be able to let them enable or disable the completion event itself. I think I will need a long list of completion event emails and then let the users fill in the email address or disable the unneeded emails too. If disabled (not deleted), they would be available to be enabled and altered again later. Assume I have full access to the database to set this up.
Thanks a bunch!
|
|
|
|
|
Don Gee
river guide
Posts:273
|
| 09-15-2011 06:28 AM |
|
Hi Whetstone,
I can't see a way for users to get direct control of the completion events cause that would involve making them into admins etc. What about solving the problem through the idea of having a table that they would have control over and this table has data that they can update or change as with 'email address', 'enable email field', ete. All content in an email: To Field, From Field, Email Body, etc can be filled from data in a table. This table could have data for many different users but each user only views his own data in that table. The completion event would be a sql event that runs off of that table. Different users would have access to only the set of data that is theirs in that table. The only thing is though if this scenario is what you are looking form then it is more a job of Dynamic Forms, Dynamic Views, and Opt-In-Email than a completion event in Dynamic Forms that works best for doing this. Is this like what you are trying to do? |
|
|
|
|
Mark Buelsing
river guide
Posts:241
|
| 09-15-2011 07:00 AM |
|
Clever idea, how would I enable multiple emails to be sent to different people, each with differnet content, all happening at the form submit on one form?
Can one completion event send multiple different emails like that?
I envisioned multiple completion events - that are dynamic emails. And the user can use a DF to open and edit the to: address of a chosen dynamic email and enable it to be sent. This could be accomplished with an update stored procedure I believe. I just need to understand the way the completion events are stored in the database in order to write the update stored procedures. Does that make sense? |
|
|
|
|
Don Gee
river guide
Posts:273
|
| 09-15-2011 07:53 AM |
|
Hi Whetstone,
I think it is ok to share this but what you are asking we do here. We have a small staff so we handle all the basic emails to people who get trials for all the products with different emails. We have follow ups with basic emails for when the trials expire. .. so you see where I am heading. I don't know all you are trying to do but with Dynamic Forms, Dynamic Views, and Opt-In-Email, we do a lot of the grunt work that it sounds like you are trying to achieve. Right now I don't have enough specifics from you to really direct you properly but consider this; with a table with enough flag fields in the table and with users belonging to different roles you can design what set of data they control in the table such that all the emails go out to the different entities that are needed. Stored procedures would fire to set flags to keep the scheduler of the opt-in-email from sending duplicates. It's complex. Does this give a start. You may have a bigger project than just one table allows.
Thanks |
|
|
|
|
Candace
river guide
Posts:2431
|
| 09-15-2011 09:23 AM |
|
Hi guys,
Let me jump in here with some thoughts. We did a project where the content of the email was 'dynamic' using stored procedures so that portions were added as the user marked various checkboxes of info they wanted to receive. It was a complex project so you might need Premium Support for this. We can either work the implementation for you, or set up some time for training and you do the actual work. It depends on how complex your form is but if we can get the 1st item going, then you might be able to duplicate it for other scenarios.
With regard to the email address -- will you have a field that the user can choose from? Let's say you have a dropdown/combobox called Department and the user can choose to send the email to Sales Dept., Technical Support, or Billing. You can set the option values of each dept. to the actual email addresses and in your completion event, use $(Department) in the Email To box. An alternative is to have a hidden field, let's call it EmailTo, and set up a client side event in the Department field so if they choose X, then EmailTo will have value of a@b.com. Your completion event will then use $(EmailTo) in the Email To box.
On the other hand, if you want your user to specify their own in the EmailTo field, you can just use the $(EmailTo) token in the email to box of the completion event.
Hope that helps!
Candace
|
|
|
|
|
Mark Buelsing
river guide
Posts:241
|
| 09-15-2011 09:04 PM |
|
Don and Candace, you two have shared some nice ideas. I'm going to think on this a bit, I think one of these ideas might work for me. I truely mean that.
I am still curious though. I know the completion events are stored in the database. Why couldn't I create a form (call it form B) that has a SQL completion event that is a stored procedure that updates the "send to" entry in the completion event record in form A?
If so, I could essentially create a "setup" (form B) that I could expose to my chosen users that would allow them to configure who gets the emails when Form A is submitted.
My app has some users that are considered to be administrators of the app and a lot of regular users too. These mentioned administrators are not website administrator accounts. That is why I'm working so hard to give them the ability to do something that an website administrator could do. - namely - change the send to address of a completion event. |
|
|
|
|