Send email with ConditionStart & ConditionEnd

[paulyp]

GDay all

I am trying to send an email with repeating sections all now going well although I need to use a5instance1,2 placeholder etc instead of [1],[2] etc placeholder ??? but that is not the question.

I am trying to conditionally send the repeating section based on the record existing (I am saving qualifications for contractors and some may have no qualifications whilst others may have 10 which are usually a PDF or Word document). Based on this, I am trying to use the ConditionStart & ConditionEnd in the HTML markup of the email. I am also nesting a ConditionStart & ConditionEnd inside the original ConditionStart & ConditionEnd.

Do I need to have a ConditionStart & ConditionEnd on each line ?
Is there a way I can suppress blank lines if there is no data or the Condition does not = true ?

Below is the code I have entered in the WYSIWYG of the Email HTML Editor and below that is what the email is sending through. Record 1 is totally filled out, Record 2 has a {cont_doc_type} of "Other" and Record 3 does not exist.

** CODE ENTERED**
{ConditionStart:other_filename_1:<%a5 isnotblank({cont_doc_type_a5instance1})%>}Document Type: {cont_doc_type_a5instance1}
{ConditionStart:other_filename_other_1:{cont_doc_type_a5instance1}="Other"} {cont_doc_type_other_a5instance1}{ConditionEnd:other_filename_other_1}
Filename: {cont_doc_filename_a5instance1}
Start Date: {cont_doc_start_date_a5instance1} Expiry Date: {cont_doc_end_date_a5instance1} Reminder Date: {cont_doc_reminder_date_a5instance1}{ConditionEnd:other_filename_1}

{ConditionStart:other_filename_2:<%a5 isnotblank({cont_doc_type_a5instance2})%>}Document Type: {cont_doc_type_a5instance2}
{ConditionStart:other_filename_other_2:{cont_doc_type_a5instance2}="Other"}{cont_doc_type_other_a5instance2}{ConditionEnd:other_filename_other_2}
Filename: {cont_doc_filename_a5instance2}
Start Date: {cont_doc_start_date_a5instance2} Expiry Date: {cont_doc_end_date_a5instance2} Reminder Date: {cont_doc_reminder_date_a5instance2}{ConditionEnd:other_filename_2}

{ConditionStart:other_filename_3:<%a5 isnotblank({cont_doc_type_a5instance3})%>}Document Type: {cont_doc_type_a5instance3}
{ConditionStart:other_filename_other_3:{cont_doc_type_a5instance3}="Other"} {cont_doc_type_other_a5instance3}{ConditionEnd:other_filename_other_3}
Filename: {cont_doc_filename_a5instance3}
Start Date: {cont_doc_start_date_a5instance3} Expiry Date: {cont_doc_end_date_a5instance3} Reminder Date: {cont_doc_reminder_date_a5instance3}{ConditionEnd:other_filename_3}

** EMAIL DATA RECEIVED **
Document Public Liability

Filename: Contractor Documents - IMG_5612.JPG
Start Date: 22/10/2014 Expiry Date: 28/10/2014 Reminder Date: 28/10/2014


Test Inputs
Filename: Y:\CCS\files\contractor\IMG_5487.JPG
Start Date: 08/10/2014 Expiry Date: 23/10/2014 Reminder Date: 23/10/2014

Filename:
Start Date: Expiry Date: Reminder Date:

Any advise would help and I hope this makes sense.

Cheers
Paul

[Steve Wood]

Re: Send email with ConditionStart &amp; ConditionEnd

If anyone was lost like me, this feature is in a UX component as an onClick Action Javascript titled "Send Email", and then the Message Body (HTML). You can insert a command such as "conditional section". Or alternately, the email can be from a template in the Repository under Project Properties. Ten years and I am still finding new stuff.

[Progytech]

Re: Send email with ConditionStart &amp; ConditionEnd

Thanks Steve, I was totally lost and now looking into that feature.

Sorry Paul, I have nothing to say about your issue, but looking forward to others replies.

[paulyp]

Re: Send email with ConditionStart &amp; ConditionEnd

Gday all
Really should proof read my posts :) !!!
I have recorded a Screencast in order to make it a easier to understand what I am trying to achieve and if anyone can help.
Thanks in advance
http://www.screencast.com/t/JUE7WBOAl

[paulyp]

Re: Send email with ConditionStart &amp; ConditionEnd

Gday all
Really should proof read my posts :) !!!
I have recorded a Screencast in order to make it a easier to understand what I am trying to achieve and if anyone can help.
Thanks in advance
http://www.screencast.com/t/JUE7WBOAl[/URL]

[Progytech]

Re: Send email with ConditionStart &amp; ConditionEnd

Hi Paul,
Thanks for the video, it does help, unfortunately I have not used ConditionStart/End features and have not idea how to eliminate the blank lines being left by the nested condition

{ConditionStart:other_filename_other_1:{cont_doc_type_a5instance1}="Other"}

Now, I do have a grid in which users can send emails that will have different subjects and body messages based on fields conditions, I decided to use an xBasics function to handle my conditions and then stored the message bodies in the alpha repository table a5Repository so if I need to change the message body, I can do it in the table without having to re-publish an update to the customer.

Here is my xb function:

'-- Send notifications email back and fort Providers and BCI from a single button.
'   We have 4 conditions that may affect where email will be sent and which message
'   body to use from the a5Repository table using a5w_GetFromWebAppRepository()
'   I start testing from the last condition
'   arSigned and work my way back to the first in the nested if...end if below.
function xbSendEmail as c (e as p)
	
	dim fromAddress as c = e._currentRowDataNew.AnnualReportfromReplyToEmail
	dim fromAlias as c = e._currentRowDataNew.CompanyName
	dim sendToAddress as c = e._currentRowDataNew.email
	dim bccAddress as c = e._currentRowDataNew.AnnualReportfromReplyToEmail
	
	dim ReportIsDueNow as L = convert_type(e._currentRowDataNew.ReportIsDueNow, "L")
	dim arReadyForReview as L = convert_type(e._currentRowDataNew.arReadyForReview, "L")
	dim arReviewCompleted as L = convert_type(e._currentRowDataNew.arReviewCompleted, "L")
	dim arSigned as L = convert_type(e._currentRowDataNew.arSigned, "L")
	dim arSignatureDate as d = convert_type(e._currentRowDataNew.arSignatureDate, "d")
	
	dim cfpStudentName as c = e._currentRowDataNew.cfpStudentName
	dim Provider1FullName as c = e._currentRowDataNew.Provider1FullName
	dim cfpProviderDueDate as d = convert_type(e._currentRowDataNew.cfpProviderDueDate, "d")
	dim CompanyName as c = e._currentRowDataNew.CompanyName
	
	dim emailBodyTemplate as c = ""
	
	dim ms as p
	ms.send_to = sendToAddress
	ms.send_to_cc = ""
	ms.send_to_bcc = bccAddress
	ms.from_email = fromAddress

	'-- Test record flags to build the message parameters from last flag to the first.
	if arSigned = .T. then
		'-- eMail sent from Provider
		ms.subject = "IEP Annual Report for " + cfpStudentName + " - Signed"
		emailBodyTemplate = a5w_GetFromWebAppRepository("IEP Annual Report - Signed")
		fromAddress = e._currentRowDataNew.email
		bccAddress = e._currentRowDataNew.email
		fromAlias = Provider1FullName
		sendToAddress = e._currentRowDataNew.AnnualReportfromReplyToEmail

	else
		if arReviewCompleted = .T. then
			'-- eMail sent from Company
			ms.subject = "IEP Annual Report for " + cfpStudentName + " - Review Completed"
			emailBodyTemplate = a5w_GetFromWebAppRepository("IEP Annual Report - Review  Completed")
		else
			if arReadyForReview = .T. then
				'-- eMail sent from Provider
				ms.subject = "IEP Annual Report for " + cfpStudentName + " - Ready for Review"
				emailBodyTemplate = a5w_GetFromWebAppRepository("IEP Annual Report - Ready for Review")
				fromAddress = e._currentRowDataNew.email
				bccAddress = e._currentRowDataNew.email
				fromAlias = Provider1FullName
				sendToAddress = e._currentRowDataNew.AnnualReportfromReplyToEmail
			else
				if ReportIsDueNow = .T. then
					'-- eMail sent from Company
					ms.subject = "IEP Annual Report for " + cfpStudentName + " - Due Now"
					emailBodyTemplate = a5w_GetFromWebAppRepository("IEP Annual Report - Due Now")
				end if '-- ReportIsDueNow = .T.
			end if '-- arReadyForReview = .T.
		end if '-- arReviewCompleted = .T.
	end if '-- arSigned = .T.
	
	'-- Make sure the email body template is evaluated to get the field values
	'   stored in the template from {} variables.
	ms.message_html = evaluate_string(emailBodyTemplate)
	ms.message_text = "Plain text version of the message"
	
	'-- No attachements needed by this process.
	'ms.attachments = "c:\files\mychart1.pdf,c:\files\mytext1.txt"

	'-- If for any reason the a5Repository record does not have a message body template, then
	'   exit this function.
	if alltrim(emailBodyTemplate) = "" then
		'Return a Javascript command
		xbSendEmail = "alert('The email body is empty.  Email was not sent.');"
		return
	end if

	'-- Send email here using Mandrill service.
	dim pResult as p
	dim mandrillKey as c = ""
	pResult = email_send_mandrill(mandrillKey,ms)
	if pResult.error then
		xbSendEmail = "alert('There was an error sending your email " + js_escape(pResult.result[1].status) + "');"
	else
		xbSendEmail = "alert('Your email was sent successfully to " + js_escape(sendToAddress) + "');"
	end if
	
end function

Here is a snapshot of my a5Repository table:
a5Repository.png
The reason I use the a5Repository table is because it is easier to get or store the record you need using the a5 functions a5w_GetFromWebAppRepository() or a5w_SaveToWebAppRepository().

Hope this give you some ideas.

[paulyp]

Re: Send email with ConditionStart &amp; ConditionEnd

Hi Edhy
thanks for the sample and yes, it has given a different approach to customize and sending the correct information based on data entered. I like the idea of the ConditionStart & End and think it gives a great deal of versatility and have tried every possible combination (excluding the correct one !!)

Thanks again
Paul

[Progytech]

Re: Send email with ConditionStart &amp; ConditionEnd

Hi Paul,

You are welcome, I am glad my sample it giving you some ideas, if you need more info, please let me know.

I like the idea of the ConditionStart & End and think it gives a great deal of versatility and have tried every possible combination (excluding the correct one !!)

Yes, I like it too, and normally it will work with simple approaches. I tried it first, but for some weird reason it was not working in my case, so I decided to go the Xbasics route in which I have full control of the situation and easier to copy for another grid or UX control.