A draft is a collection of email messages, labels or letters that share a common set of attributes. Those attributes include: the recipient list, the template, stationery and/or layout selections and the completed status, among other things. Drafts are the primary way you collect correspondences in fmSpark.
Stands for Hyper Text Transport Protocol. This is a text-based language which describes how content should be displayed, generally within web pages. However, in recent times this has become the standard for design of content-rich email messages as well.
You can keep a record of all your mailings to a particular contact as a Journal table in your contact's file. See Journaling for more.
For Letters and Labels, the Layout determines where each piece of text and image goes. This Layout refers to an actual FileMaker Pro layout. See Layouts for more.
Plain Text Part
The Plain Text Part is an email concept. Some recipients may have difficulty viewing your HTML Stationery-based email messages. Including a plain text part as an alternative ensures that they will be able to view at least a plain text version of your message.
Email messages can be sent using an HTML-based Stationery design: stationery is the email equivalent of the "layout" we use to print a letter. This is standard HTML, but needs to be careful to be "email safe". Section text placeholders can be substituted-for by using [text1]/[text2]/etc tags in the HTML. See Stationery for more.
The text of the message, letter or label that can change on a per recipient basis. For a letter and label this is the text and images of the letter or label. For an email, it's the Plain Text Part or the section texts in the HTML Part. See Templates for more.
Templates in fmSpark are each assigned a media type and out of the box fmSpark understands 3 media types: Emails, Letters, and Labels. We use the media type designation to make sure we only show you label templates when you elect to send labels, for example.
When you send a list of contact IDs to fmSpark, that "merge group" is called contacts. fmSpark can be taught to accept lists from other merge groups so that you can send lists of "prospects", "sales", "projects', etc. and use merge fields associated with these groups instead of the contacts group. Of course these groups may have their own contact merge fields, but groups have their own table occurrences and merge fields in fmSpark. Merge groups may also have their own templates, but a template may also belong to more than one group.
Page URL: http://docs.proofgroup.com/fmSpark/en/1.0/Glossary