Templated event titles
Added by IBM contributorIBM | Edited by Claudia R Elbourn on June 16, 2015
Rate this article 1 starsRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars

IBM Connections allows for the introduction of two kinds of template in the title of a connections. The first is object substitutions, where an appropriate representation of a known object within the event is substituted into the title. The second is title template substitutions. These use the above object substitutions, providing a full title that is appropriately resourced. In both cases above, a submitted event.title is converted into an event.content if and only if no event.content is present within the event. Where an event.content is provided by the POSTer of an event, this value is maintained and returned in any ActivityStream feed that is retrieved.

Object Substitution

A number of substitution values are supported within a submitted event.title. These are specified using the ${} marker.

  • ${Actor} - this is converted into appropriately marked up HTML which displays the Actors name and links to a Business Card corresponding to the Actor
  • ${Object} - if this is a person we display as with the Actor above, otherwise the displayName with a link to the url
  • ${Target} - if this is a person we display as with the Actor above, otherwise the displayName with a link to the url

The event.content is generated from the title, exactly substituting as appropriate.

Title Template Substitution

A number of templates are available which provide the additional facility of localised content, as the particular text appropriate for the locale of the viewing user is used when retrieving the event. These are also specified using the ${} marker.

Available templates (in English)

  • ${add}=${Actor} added ${Object}.
  • ${add.target}=${Actor} added ${Object} to ${Target}.
  • ${create}=${Actor} created ${Object}.
  • ${create.target}=${Actor} created ${Object} in ${Target}.
  • ${post}=${Actor} posted ${Object}.
  • ${post.target}=${Actor} posted ${Object} to ${Target}.
  • ${comment}=${Actor} created a comment.
  • ${comment.target}=${Actor} commented on ${Target}.
  • ${like}=${Actor} liked ${Object}.
  • ${like.target}=${Actor} liked ${Object} in ${Target}.
  • ${update}=${Actor} updated ${Object}.
  • ${update.target}=${Actor} updated ${Object} in ${Target}.
  • ${share}=${Actor} shared ${Object}.
  • ${share.target}=${Actor} shared ${Object} with ${Target}.
  • ${follow}=${Actor} is now following ${Object}.
  • ${stopFollowing}=${Actor} has stopped following ${Object}.
  • ${tag}=${Actor} tagged ${Object} with ${Target}.
  • ${join}=${Actor} is now a member of ${Object}.
  • ${invite}=${Actor} has invited ${Object}.
  • ${invite.target}=${Actor} has invited ${Object} to ${Target}.
  • ${access}=${Actor} has accessed ${Object}.
  • ${access.target}=${Actor} has accessed ${Object} in ${Target}.
  • ${assign}=${Actor} has assigned ${Object} to ${Target}.
  • ${accept}=${Actor} has accepted ${Object}.
  • ${reject}=${Actor} has rejected ${Object}.

Default template

In the absence of a title or content in the submitted event, we attempt to create an event title based on the verb used in the event. If we cannot to this we use the ($Updated) emplate above