Templates
HTML & Email Templates
html and email templates are built using a browser based html editor they support attachments, as well as dynamic variables to pull in dynamic data each of these templates serve a distinct role html templates are used to create interactive web pages that consolidate multiple reports and ai driven insights into a single view, typically accessed instantly via a salesforce button email templates are designed for outbound delivery, enabling you to send personalized communications, reports, and summaries directly to a recipient's inbox through automated solutions or schedules html templates html templates enable you to bring multiple reports into a single page that can be easily accessed by your users using a button on a salesforce record unlike email templates, html templates are used to build web pages that serve up content from report builder, often to provide a single view of multiple reports accessible via a salesforce button html templates are typically triggered by a salesforce button to provide an instant, single view of multiple reports (like an account summary) without sending an email key features bring reports, dashboards, documents, and even ai analysis into a single view design directly in the browser using our html editor make use of all standard variables and include additional attachments initiate directly from a button on a salesforce record create html template navigate to templates > html click add complete the template name description html body (you can use the rich text editor or source) attachments this can be any supplementary document or presentation for your solution click save to finish email templates email templates are pre configured blueprints built and styled directly in the browser using an html editor they are primarily used for sending out communications, reports, and ai driven analysis to an inbox via solutions or schedules while html templates are for browser viewing, the "html output type" in solutions allows email templates to include advanced features like conditional formatting or record handlers directly in the body of an email key features dynamic customization you can use standard variables to pull in specific data, such as a recipient's first name, to personalize the message media and attachments they can include attachments like pdfs or excel files and can also incorporate agent analysis directly in the body of the email advanced formatting by using the "html output type" in a solution, email templates can display advanced features like conditional formatting or record handlers (e g , displaying data as blocks instead of rows) directly within the email automated tracking when used for marketing campaigns, they can be configured to update the status of a record (such as a campaign member) once an email is opened or sent while similar to html templates in design, email templates are specifically for outbound delivery rather than building internal web pages for browser viewing create email template navigate to templates > email click add complete the template name description html body (you can use the rich text editor or source) attachments this can be any supplementary document or presentation for your solution click save to finish variables general variables you can include these variables for use in your email these can be used to personalize each message you send advanced features include burst report variables and marketing email variables variable token description {{username}} name of the running user {{solutionid}} id of the solution {{solutionname}} name of the solution {{timestamp}} timestamp when the solution ran {{datetime}} formatted date and time when the solution ran {{date}} formatted date when the solution ran {{datevalue}} date value when the solution ran {{yesterdaytimestamp}} timestamp of previous day's date when the solution ran {{yesterdaydatetime}} formatted previous day's date and time of when the solution ran {{yesterdaydate}} formatted previous day's date of when the solution ran {{yesterdaydatevalue}} previous day's date when the solution ran {{currentmonthname}} current month name when the solution ran {{currentmonthfirstdayofmonth}} formatted first day of the current month when the solution ran {{currentmonthfirstdayofmonthdatevalue}} first day of the previous month date value when the solution ran {{currentmonthlastdayofmonth}} formatted last day of the current month when the solution ran {{currentmonthlastdayofmonthdatevalue}} formatted last day of the current month date value when the solution ran {{previousmonthname}} previous month name when the solution ran {{previousmonthfirstdayofmonth}} formatted first day of the previous month when the solution ran {{previousmonthfirstdayofmonthdatevalue}} first day of the previous month date value when the solution ran {{previousmonthlastdayofmonth}} formatted last day of the previous month when the solution ran {{previousmonthlastdayofmonthdatevalue}} formatted last day of the previous month date value when the solution ran {{nextmonthname}} next month name when the solution ran {{nextmonthfirstdayofmonth}} formatted first day of the next month when the solution ran {{nextmonthfirstdayofmonthdatevalue}} formatted first day of the next month date value when the solution ran {{nextmonthlastdayofmonth}} formatted last day of the next month when the solution ran {{nextmonthlastdayofmonthdatevalue}} formatted last day of the next month date value when the solution ran for any date value variables, you can apply a custom format to this value using the datetool examples $datetool format("dd mm yyyy", $datevalue) = 31 12 2024 $datetool format("eeee, mmmm d", $yesterdaydatevalue) = thursday, december 1 item variables these variables enable you to decide where you would like place item information when you have than one item in your solution for example, if you include two reports you could use the following variables report 1 variable token description {{itemid1}} id of the first report {{itemname1}} name of the first report {{itemgrandtotalcount1}} total records in the first report {{itemhtml1}} html of the first report report 2 variable token description {{itemid2}} id of the second report {{itemname2}} name of the second report {{itemgrandtotalcount2}} total records in the second report {{itemhtml2}} html of the second report available variables include variable token description {{itemid1}} id of the first report {{itemname1}} name of the first report {{itemgrandtotalcount1}} total records in the first report {{itemhtml1}} enables you to control where to put the report content {{itemagentprompt1}} agent prompt for the first item {{itemagenthtml1}} enables you to control where to put the item agent analysis {{agentprompt1}} enables you to control where to put the agent prompt {{agenthtml1}} enables you to control where to put the agent analysis {{itemfilepassword1}} password for the attachment (if configured) marketing email variables these variables can be used to in conjunction with a solution that is set up to send a marketing email if you include these variables in a transactional solution (so one that includes a report, dashboard, or document), then these variables will be ignored variable token description {{web link url}} url for a view in a browser window it will open in a new window {{unsubscribe url}} url for an unsubscribe link placing this link on your email template enables your recipient to click the link and opt out of receiving future emails {{manage preferences url}} placing this link on your email template enables your recipient to choose which kind of email categories they would like to be a part of, or opt out of burst variables when you include a burst report in your solution, all fields from that report are available as variables the format for the variables is {{field api name}} for example, if you had a field account name , then the variable name would be {{account name}} to get a list of all variables, run your burst report and open the variables window