Skip to navigation Skip to content

CloudDeakin Guides

Replacement Strings

Replacement strings allow you to personalise messages by providing the code to replace information that is specific to a student such as their first and last names. This allows you to send personalised messages to each student in your site without having to enter their personal details numerous times.

Replacement strings can be used:

  • where ever there is a WYSIWYG (What You See Is What You Get). Examples: HTML pages, Assignment folder descriptions, Announcements, widgets, discussion posts, etc.
  • emails sent by Intelligent Agents (within the body and/or the address field)

Note: Replacement strings cannot be used in emails sent via the Classlist.

Common Replacement Strings

Replace StringWhat will be displayedWhere it can be used
{OrgName}The name of the organisation (e.g. Deakin University)
  • Announcements – In the Headline and Content
  • Discussions – In the Subject and Message
  • Topic – When you create a new file
  • Assignments – In Folder custom instructions & Feedback
  • Quizzes – In Description, Introduction, Page Header and Footer
  • Grades – In Comments
  • Checklist – In Name and Description
  • Groups – Descriptions
{OrgUnitCode}The code for the Org Unit (e.g. ABC123_Tri-1_2012)
  • Announcements – In the Headline and Content
  • Discussions – In the Subject and Message
  • Topic – When you create a new file
  • Assignments – In Folder custom instructions & Feedback
  • Quizzes – In Description, Introduction, Page Header and Footer
  • Grades – In Comments
  • Checklist – In Name and Description
  • Groups – Descriptions
{OrgUnitName}The name of the org unit (e.g. ABC123 – Introduction to the Alphabet)
  • Announcements – In the Headline and Content
  • Discussions – In the Subject and Message
  • Topic – When you create a new file
  • Assignments – In Folder custom instructions & Feedback
  • Quizzes – In Description, Introduction, Page Header and Footer
  • Grades – In Comments
  • Checklist – In Name and Description
  • Groups – Descriptions
{FirstName}First Name of the logged in user (e.g. John)
  • Announcements – In the Headline and Content
  • Discussions – In the Subject and Message
  • Assignments – In Folder custom instructions & Feedback
  • Quizzes – In Description, Introduction, Page Header and Footer
  • Grades – In Comments
  • Checklist – In Name and Description
  • Groups – Descriptions
{LastName}Last Name of the logged in user (e.g. Doe)
  • Announcements – In the Headline and Content
  • Discussions – In the Subject and Message
  • Assignments – In Folder custom instructions & Feedback
  • Quizzes – In Description, Introduction, Page Header and Footer
  • Grades – In Comments
  • Checklist – In Name and Description
  • Groups – Descriptions
{OrgUnitStartDate}The start date specified for the org unit (21 Feb, 2012)
  • Intelligent Agents
{OrgUnitEndDate}The end date specified for the org unit (2 June, 2012)
  • Intelligent Agents
{InitiatingUser}The user who performs the action that meets the agent’s criteria
  • Intelligent Agents
{InitiatingUserFirstName}The first name of the initiating user (e.g. John)
  • Intelligent Agents
{InitiatingUserOrgDefinedId}The Org Defined Id of the initiating user (e.g. jdoe)
  • Intelligent Agents
{InitiatingUserLastName}The last name of the initiating user (e.g. Doe)
  • Intelligent Agents
{LoginPath}The address of the login path for the site
  • Intelligent Agents
{LastLoginDeate}The date the initialing user last logged in.
  • Intelligent Agents
{OrgUnitId}The id for the unit.
  • Intelligent Agents
{LastCourseAccessDate}The date the initialising user last accessed the unit.
  • Intelligent Agents
back to top