  Related Topics
How tags work
A web template is coded according to what FirstClass content it must display using X-FC tags and other IS script variables. Depending on the nature of the tag, X-FC tags pull data directly from one of two places:
• the en.rez resources file (mainly guide text)
• the server.
Data pulled from the server comes from a number of places:
• the current object (for example, the "To" or "Subject" fields of a message or the list of items in a conference)
• the session data, which is the information about the server or the current user (for example, the user's full name, the server site name, or the server time zone, and so on)
• preferences (for example, any data located on the.sitepref form and the user Preferences form).
Generally, the most common X-FC tags used in FirstClass web templates fall into three categories:
• X-FC FIELD
• X-FC ITEM (and corresponding tags, such as, X-FC-LIST-ITEM)
• X-FC BODY
For a complete list of all X-FC tags and other IS script variables, see About the IS script Library.
In this section, we provide examples of some of the more common tags (and other random tags) in the Message template and break them down into their component parts.
Warning
Randomly pasting any of the following code examples into a template may not work as desired. Do not consider any of the code shown in these examples as complete.
Message tag examples and their definitions
 • <X-FC-FIELD FORM.6.9 STRING>
Maps to the "Subject" field text, where FORM means the current form, 6 is the "Subject" field ID, 9 is the property ID (label/guide text), and STRING designates the output of this tag as a string.
• <X-FC-ITEM DATA[Subject]>
This tag represents the actual "Subject" user-input field.
 • <X-FC-FIELD FORM.10.9 STRING>
Maps to the "Cc" field text, where FORM means the current form, 10 is the "Cc" field ID, 9 is the property ID (label/guide text), and STRING designates the output of this tag as a string.
• <X-FC-RECIPIENT-COUNT CC>
Outputs the number of recipients in the CC list.
• <X-FC-FIELD LANG.7528.13 STRING>
Outputs the lang.rez string resource #7528, index 13 (in this case "Delete Recipient").
• <X-FC-RECIPIENT CC $RECIPIENTNUM DATA[Name]>
Extracts the name of the $RECIPIENTNUM th CC name.
• <X-FC-RECIPIENT CC $RECIPIENTNUM DATA[Name] DIRNAME>
Extracts the name of the $RECIPIENTNUM th CC name. DIRNAME applies bolding, italics, and other formatting to the recipient based on whether or not they are online, able to accept Instant Messaging, and so on.
 • <X-FC-FIELD FORM.12.9 STRING>
Maps to the "Attachments" field text, where FORM means the current form, 12 is the "Attachments" field ID, 9 is the property ID (label/guide text), and STRING designates the output of this tag as a string.
• <X-FC-LIST-COUNT>
Outputs the # of (unhidden) attachments for this message.
• <X-FC-LIST-ITEM-URI `$ATTACHMENTNUM` BASE>
Outputs the URL to the $ATTACHMENTNUM th attachment. The BASE argument removes the file name from uploaded file attachments, which is necessary when doing operations (for example, deleting them).
• <X-FC-LIST-ITEM `$ATTACHMENTNUM` DATA[Subject] LENGTH>
Outputs the length of the subject (in bytes) of the $ATTACHMENTNUM th attachment in the list.
• <X-FC-LIST-ITEM `$ATTACHMENTNUM` DATA[Subject]>
Outputs the subject of the $ATTACHMENTNUM th attachment in the list.
• <X-FC-LIST-ITEM `$ATTACHMENTNUM` DATA[Size] SCALED>
Outputs the size of the $ATTACHMENTNUM th attachment in the list. The SCALED argument tells Internet Services to use the appropriate symbol given the size of the attachment (for example, K, M, G, T).
 • <X-FC-BODY>
This tag represents the actual "Body" user-input field.
|