ISML
B2C Commerce ISML tags are extensions of the tag-based language conforming to SGML standards. They are commands inserted into a document that determine how B2C Commerce embeds live data into a page, and how to format this data together with the regular HTML code.
Each B2C Commerce tag has a specific name that always starts with the prefix "is," such as <isprint>
or <isset>
. Tags must be included within angle brackets (<
and >
), and can have several attributes that can be set to control the behavior of the tag. All tags and their attribute names are not case sensitive. However, the values of attributes are often case sensitive.
Salesforce recommends that you use lower-case as good programming practice.
The syntax shows literal values in quotes and variables without quotes. Unless otherwise noted, each attribute is included exactly one time. You can only use expressions or strings as documented. Using expressions if they are not explicitly allowed causes exceptions.
Tag & Location | Syntax & Notes |
---|---|
Allowed locations:
|
Collects category context from a page for active data. Should only be in one template used to render a page. |
Allowed location:
|
Allows collection of active data from pages with a |
Allowed locations:
|
Disables analytics for single pages. |
Allowed locations:
|
Injects |
Allowed locations:
|
Only used inside |
Allowed location:
|
Cache a page. The tag can be located anywhere in the template. However, we recommend that caching statements are placed at the beginning of a template. If the tag occurs several times in one template, the one set to |
Allowed location:
|
Add documentation to the template. As a best practice, include an initial comment that describes the purpose, the requirements, and the effect of a template from both a business point of view and a technical perspective. Using |
Allowed location:
|
Include the output of a pipeline in the page. |
Allowed location:
|
Define the MIME type of the output document. Don't specify The default for emails when using the SendMail pipelet is To make sure all characters in a document are correctly encoded, the |
Allowed location:
|
Jump to the beginning of the loop. Only used inside |
Allowed location:
|
Set a cookie. |
Allowed location:
|
Template decoration mechanism. For |
Allowed location:
|
Specify what happens if a condition doesn't evaluate to true. Must be used with |
Allowed location:
|
Create conditional template code. |
Allowed location:
|
Specify a subcondition for an |
Allowed location:
|
Includes the contents of one template inside another. As a best practice, add includes that affect the whole page to the top of the template. |
Allowed location:
|
Creates a loop. See also |
Allowed location:
|
Declares custom tags. In SiteGenesis, all |
Allowed location:
|
Jump forward within a loop. Only used inside |
|
Collects page impressions or views from the storefront. Must pass an object of type Must wrap any object you want to record active data for. |
Allowed locations:
|
Injects |
Allowed location:
|
Format and encode output strings. |
Allowed location:
|
Redirect to a target URL. |
Allowed location:
|
Remove user-defined variables. |
Allowed location:
|
The insert content to be decorated. If a template is going to be remotely included, the |
Allowed locations:
|
Create a script within a template. |
Allowed location:
|
Enhancements to the HTML |
Allowed location:
|
Set user-defined variables. |
Allowed location:
|
Define slots for content display. |
Allowed location:
|
Define a status code. |
See also:
Parent topic: