The plan doesn't offer workflows so the alternative would be to use the "web form to email" option.
This article should help with this requirement.
Hope this helps!
That you. This looks very hopeful, but I still have some uncertainty.
The articles tells me to enter code like this:
I'm guessing that's in the form tag.
My form tag currently has this statement:
Is the suggested code supposed to replace what's there or be merged with what's there?
Oh no, I thought I had this one solved. I just looked at the form output that is being returned to me. Three fourths of the fields have labels like CAT_Custom_132902.
The client is not going to be able to make sense of this.
My action line said:
Looking at the commented out code (but really just shooting in the dark), I changed it to
This gave me back the Thank you for your submission page, but one hour later, I have yet to receive the contents of the form submission.
My gut tells me /Default.aspx?A=Form is the part of the code that determines what gets sent in the email. Is there something I should be doing to make it use the custom labels?
The default.aspx versus formprocessv2.aspx are basically 2 different ways of submitting webforms.
As described in http://kb.worldsecuresystems.com/834/cpsid_83480.html?bc-partner the default.aspx method (also known as form to email) is mostly used for the plans that do not have webforms included.
Webforms on the other hand use formprocessv2.aspx and are more complex that simple form to emails (they also create contacts, cases, have access to the CRM), what you need to keep in mind though is they are entirely different methods.
Now, regarding your implementation, there is one more requirement regarding the form to email, the "Email" parameter must be the email address of an user that exists either in your CRM database or is registered as the local admin for that site, otherwise the email will not be sent (see the notes in the KB article regarding "&Email=You@YourDomain.com") - could this be the case?
“the "Email" parameter must be the email address of an user that exists either in your CRM database or is registered as the local admin for that site, otherwise the email will not be sent . . . - could this be the case?”
That is exactly the case. Under WebBasics, I don’t even see a customer database, and there can be only one administrator, a post that my boss refuses to relinquish, making it impossible for me to add the designated recipient of the form submission.
We have found a temporary solution until the client can be coaxed into an upgrade. Submissions will go to my boss, who will set up an email rule to redirect them to the client.
Thanks to everyone who offered advice.