Difference between revisions of "Template Variable Contexts"
From LongJump Support Wiki
imported>Aeric |
imported>Aeric |
||
| Line 1: | Line 1: | ||
Template variables have slightly different syntax in different contexts. The template variable tools gives you the possible variables in the correct syntax for each context: | Template variables have slightly different syntax in different contexts. The template variable tools gives you the possible variables in the correct syntax for each context: | ||
: | :{| | ||
| Print || '''Designer > Data > Objects > {object} > Print Templates > {template}''' | |||
|- | |||
| JavaScript actions || '''Designer > Data > Objects > {object} > Actions > Execute JavaScript''' | |||
|- | |||
: | | Workflow || '''Designer > Data > Objects > {object} > Workflows > {workflow} > Notification Templates''' | ||
|- | |||
| Component || '''Designer > Logic > Components > {component}''' | |||
{{#if: {{ShowIsvInfo}} | | |||
|- | |||
| Service Provider emails || '''Settings > Service Provider Settings > Manage Email Templates''' | |||
}} | |||
|} | |||
And, in the Sales Force Automation application: | And, in the Sales Force Automation application: | ||
:* Email: '''Workspace > All Items > Templates > [New Template]''' | :* Email: '''Workspace > All Items > Templates > [New Template]''' | ||
Revision as of 19:47, 9 January 2012
Template variables have slightly different syntax in different contexts. The template variable tools gives you the possible variables in the correct syntax for each context:
Print Designer > Data > Objects > {object} > Print Templates > {template} JavaScript actions Designer > Data > Objects > {object} > Actions > Execute JavaScript Workflow Designer > Data > Objects > {object} > Workflows > {workflow} > Notification Templates Component Designer > Logic > Components > {component}
And, in the Sales Force Automation application:
- Email: Workspace > All Items > Templates > [New Template]