Hi,
I've used the Send Email trigger action quite a few times, but only at a basic level (i.e. putting in an email address or two and putting the content I want in the email in the provided 'body' area.
I've been having a closer look at the other options over the past few days, mostly trying to work out what is possible.
I've read the latest manual (we're on 3.28.3) and it doesn't really shed much light on the 'Asset to Send' feature.
In the bottom section of the Send Email settings, underneath the body content box, there is an 'asset to send' box. In there it says "The content you would like sent in the emails. Note : If asset is selected to send, then Body of the email will not be sent". My understanding is that you should be able to create a standard page that contains the text you want in your email and then just pop it in there. When I tried it, however, my emails came through blank. I must be missing something. I made sure the standard page was live and that it definitely contained content. I didn't leave any content in the 'body' box.
Is that 'Asset to Send' box related to the Asset to Send checkbox up above the general email setting section? I tried fiddling around with the settings under that too, but to no avail.
I'm also curious about the paint layout bit, and what sort of things that can help you achieve?
Some further instruction on this would be very much appreciated!
Thanks!
Margaret
Anyone?
I'd really like to know the secret to getting content from an asset to show in an email sent from a trigger… Just adding one to the 'asset to send' section doesn't seem to be enough.
Thanks!
Hi Margaret. As you suspected, the idea of the General Email Settings' Asset to Send option is to allow you to use the content of an existing asset in your system as the body of the email. The Asset to Send fields above the General Email Settings allow you to use the asset that fired the trigger as the Asset to Send (the content of your email) or to select an Asset to Send using GET/POST/SESSION parameters returning the Asset ID. It is important to note that these fields will overwrite any assets selected in the Asset to Send General Email Setting.
I am unable to replicate your issue on my 3.28.4 system - you should be able to just select an asset in the General Email Settings' Asset to Send field and it should be sent as the content of the email (so long as it is not being overridden by the other Asset to Send options). If you have any more info on your trigger setup it could be useful, otherwise you may need to submit a ticket and one of the devs can look into it for you.
Did you make sure that in your trigger manager that Triggers are turned on?
Thanks for your responses guys.
Yes Nic, the trigger manager is definitely turned on as we have other fully-functioning triggers successfully running. 
The trigger in question also works when I put content in the email body section - the problem is that it sends a blank email if I tell it to use another asset's contents.
The settings of the trigger in question are as follows:
[font="Courier New"]Status - Enabled
Blocking - No
Events
======
Asset Created
Conditions
==========
Tree location is set to the folder the assets are created in
Asset is of type Data record
Actions
=======
Send Email Trigger Action
Active User Recipient
---------------------
'Send to active user' NOT ticked
Group Recipients
----------------
None added
Role Recipients
---------------
None added
Recipient Source
----------------
None set
Asset To Send
-------------
'Override the Asset To Send…' NOT ticked and no parameters set
General Email Settings
----------------------
To: currently my email for testing purposes
From: our generic web team's email address
Subject: Web Feedback to Webmaster
Body: when completed trigger works, email sends properly
Asset To Send: While testing have tried adding a standard page here with just a single line of text saying 'feedback has been submitted'. Left it in block level/WYSIWYG format. Even tried making it live with public permission but that made no difference.
Design to Apply: None set (setting it to the same design applied to the standard page used in Asset To Send makes no difference)
Layout to Apply: None set
[/font]
Let me know if you need any other info.
Thanks!
Margaret
Hi Margaret. Thanks for the further trigger info. We have tested your setup on our system and have not been able to replicate the issue with the blank asset. One thing you might want to check is that the user who created the Data Record should have Read Permission on the asset that is being sent. I imagine that this is the case already but worth checking out.
[quote]
Hi Margaret. Thanks for the further trigger info. We have tested your setup on our system and have not been able to replicate the issue with the blank asset. One thing you might want to check is that the user who created the Data Record should have Read Permission on the asset that is being sent. I imagine that this is the case already but worth checking out.
[/quote]
Hi Josh,
The data records are actually being created by the public user - for our purposes using a customised asset builder (feedback form) to create data records (form submissions) was more suitable than a custom form.
The data records are left under construction but they have public user access.
The page I was trying to nest is live and has public user access.
Any ideas?
Thanks!
Margaret
Margaret, we've been able to replicate this issue using an Asset Builder. It seems to be a bug so I will lodge a report.
[quote]
Margaret, we've been able to replicate this issue using an Asset Builder. It seems to be a bug so I will lodge a report.
I'll also get someone to fix up your profile for you.
[/quote]
Ahhhhh fantastic - glad to know I'm not going mad. 
Thanks on both counts. Can you please let me know the bug report ID so I can track it?
Cheers,
Margaret
[quote]
Ahhhhh fantastic - glad to know I’m not going mad. Thanks on both counts. Can you please let me know the bug report ID so I can track it?
Cheers,
Margaret
[/quote]
No worries.
#4695 Send Email Trigger Action: Asset to Send Blank on Asset Builder creation