To get started with Nimble Create, Create a New Template. From here you can author your content and apply your formatting.
Create a New Template
Before creating a template from scratch, we recommend exploring existing templates
In the tab bar, click, or in Salesforce Classic, click
- Click Templates.
In Template Name, enter the unique name by which to identify the Template.
Sharing Mode, select:
Systemif you want to see all records regardless of ownership. Typically you will select
Userif you want to see only records that you own.
Description, enter the purpose of the Template.
SOQL Queryenter the SOQL to use with the template. This query will be used to determine which data is accessible within the template and is essential to building your template.
SELECT is a list of the fields you want to be available in the template
FROM is the base tab/object that contains those fields mentioned above. Generally your template will refer to just one object. If you need to access more than object, you can use subtemplates, or include related fields in the SELECT line using ‘__r’ notation, or by writing a SUBSELECT. These are advanced topics that are covered in more detail.
WHERE is a set of conditions to restrict the results returned. A typical restriction is to limit the results to a single record. In the example above, we show the use of a parameter, which is explained in more detail below.
In the WHERE clause you can filter using parameters (:param1) that will be passed in from the template. You can use up to 9 parameters, but using a single parameter is most common.
Advanced Template Settings
The following fields are also available for use within your template.
CSS File - a Static Resource file that contains font, color, and sizing specifications. Typically a developer will help to set this up for you as a one-time task and you can use it for all templates in the future.
Inline CSS - When this is checked, it will inline the base CSS from the static resource above.
This is handy for emails, so each client will render the styles correctly.
Having this unchecked will apply no styling, which would be useful for outside of emails where you have your own stylesheet
Best practices for CSS are to put the stylesheet rules in a Resource file (.css) instead of specifying inline style instructions. For example you could put an instruction in the .css file that the whole document should be Times New Roman. An Inline approach would mean that every paragraph would require the font be specified explicitly. In a document with 10 paragraphs, this means 10 font instructions instead of just one instruction in the resource file. Having the instruction once reduces error and increases consistency.
Gmail is a website that has its own .css resource file. Each email from Nimble Create is delivered with its own private css resource file. When two resource files are on the same page they overlap and compete with one another. In order to ensure that Gmail’s website always looks the way Gmail wants it, they disable the email’s resource file entirely. Gmail allows Inline CSS because it cannot contaminate the rest of the Gmail web page, even though Inline CSS is not a best practice.
The solution in Nimble Create is to use the “Inline CSS” checkbox. This allows a template author to specify stylesheet instructions in a resource file, but at runtime the instructions are applied to each element as an Inline style instruction.
The Inline CSS checkbox does not work in conjunction with in Nimble Create Extensions, so care should be taken when developing a template to decide how style instructions should be incorporated into the template: as a resource file, as inline, or a combination of the two.
Parent Template - Allows you to set some basic appearance around the template.
Bulkify Subtemplates - If you include a sub-template in your template, check this box to reduce the chances that the template will encounter Salesforce limits.