Substitution Tokens

The following list describes substitution tokens that you can use to incorporate data from the runtime errors into the email. For example, you can use tokens to return information about the object on which the error occurred, identify the user who caused the error, and/or indicate what type of action caused the error to occur.

This token...	Inserts the following information into the parameter value at execution time...
${error.id}	The unique identifier of the error.
${error.message}	A short message text describing the error.
${error.action}	An action that a user can perform to resolve the error.
${error.explanation}	A description of the error.
${error.stacktrace}	The stack trace of the error.
${entity.name}	The object's name (in the user's locale).
${entity.description}	The object's description.
${entity.owner}	The name of the user who owns the object on which the error occurred.
${entity.organization}	The organization to which the object on which the error occurred belongs.
${entity.state}	The state of the object on which the error occurred.
${entity.type}	The type of object on which the error occurred.
${entity.XML}	XML of the object on which the error occurred.
${entity.URL}	The URL for the object on which the error occurred.
${entity.version}	The object's user-assigned version identifier.
${system.repository.url}	The fully qualified URL for the CentraSite registry/repository (http://localhost:53307/CentraSite/CentraSite).
${system.user.name}	The name of the user who caused the error.
${user.locale}	The locale of the user who caused the error.
${diagnostic.all.properties}	Renders all custom properties provided during diagnostics.