Difference between revisions of "Template Variables in Workflows"
From LongJump Support Wiki
imported>Aeric |
imported>Aeric |
||
| Line 5: | Line 5: | ||
In addition to the typical field-based template variables, these workflow-based variables are also available: | In addition to the typical field-based template variables, these workflow-based variables are also available: | ||
:*<tt>$workflow.id</tt> | |||
:*<tt>$workflow.name</tt> | :*<tt>$workflow.name</tt> | ||
:*<tt>$workflow.title</tt> | :*<tt>$workflow.title</tt> | ||
:*<tt>$workflow.current_state</tt> | :*<tt>$workflow.current_state</tt> | ||
:*<tt>$workflow.action_taken</tt> | :*<tt>$workflow.action_taken</tt> | ||
Revision as of 22:53, 3 August 2011
Template variables can be used in both subject and body of a template. All the template variables related to the record are shown.
The Template Variables section provides a lookup to variables that will personalize the message.
In addition to the typical field-based template variables, these workflow-based variables are also available:
- $workflow.id
- $workflow.name
- $workflow.title
- $workflow.current_state
- $workflow.action_taken
- $workflow.available_actions_for_current_state
- $workflow.previous_state
- $workflow.user_comments
- $workflow.owner (Owner(s) for current state)
- $workflow.history (History of workflow in a table)
- $workflow.view_details_link (Link to view the record details)