Notification Content
On the Notification Content page, you configure the content that will be included in WorldServer notification messages. These messages are of the following types:
Note: When you click Save after editing the content configuration for a notification type, the content is applied to all new messages of that type. You can edit the message content for multiple types by simply switching types, editing the content, and clicking Save. You can only have one set of message content per type.
You can select the language that a recipient has chosen as her or his preferred display language, and you can select from available parameters for the message subject, header, body parameters, and footer. The default text of the message, and the available parameters from which you can select, depend on which notification type you have selected. The parameters you specify get automatically replaced in the sent message by the data specific to the context of the message. That is, if you specify [issue severity], the message, when sent, will place in this location the actual severity of the issue, for example, High.
You can also simply type in additional or replacement text, and that text will appear in the message.
Settings Common to All Notification Types
The User to contact for assistance and Base URL for WorldServer settings apply to all notification types. That is, you can modify and save the content for different notification types, and they will retain the content changes you've made. But you cannot specify a different user to contact or base URL for each. All notification types share whichever user to contact and base URL was most recently saved.
Note: The Restore Defaults button at the bottom of the page does not apply to the user to contact and base URL settings. If you change these and click Restore Defaults, these two settings will not revert. Restore Defaults applies only to the current configuration, as designated by type menu and language selections. Restoring default settings for English content for Issue Assigned event messages does not restore default settings for any other event types, such as Task Assigned, nor does it affect the Issue Assigned content in other languages, such as Japanese. Content for each language and event type must be restored on an individual basis. There is no convenient option for restoring defaults for all notification content.
The user you select for User to contact for assistance will appear in the delivered message, along with her or his email address.
The Base URL for WorldServer is supplied for you, but is not picked up by the system until you save your settings. You should not need to change this setting. The URL will appear in the delivered message as a link for the recipient to click on for the issue page or project URL.
Caution: the Administrator should ensure that the base URL is not set to http://localhost.... For most cases, this is not a desired base URL and will block users from accessing WorldServer links in notifications.
Configuring Messages for Each Notification Type
After you have selected a notification type and display language, you can modify the content of the message itself by editing the text in each area (Subject, Header, Issue Summary, or Footer) and by selecting and placing (or replacing) parameters.
To place a parameter in the message, select the parameter, then place your cursor at the location in the message you want it to appear and click the arrow. To remove a parameter, simply delete its text (including the brackets) from the message.
Following are explanations of the available parameters that are not self-evident:
Header and Footer Parameters for all notification types:
Parameter
Description
[(contact user email)]
Displays email address of the contact user if it is configured, otherwise does not display.
Note: The footer only provides such information if the corresponding parameters are present in the configuration. They are present by default, but can be removed.
Issues Assigned type:
Parameter
Description
[issue page url]
The WorldServer URL to the issues page.
[issue count]
Number of issues in notifications.
[issue notes]
The latest issue history entry’s notes field.
Task Assigned type:
Parameter
Description
[project task count]
The number of tasks assigned to the recipient in the give project.
[project tasks are]
The number of tasks assigned to the recipient in the given project along with “is” or “are” depending on whether or not the count in singular or plural.
[project task steps]
The list of steps for all assigned tasks in the project.
[project url]
The WorldServer URL to the project page.
Task Due type:
Parameter
Description
[project user type]
Recipient’s project user type. English values are: “task claimant," “task assignee,” “task creator,” and “project creator.”
[project full name]
The task’s project name including locale and ID. For example, Weekly Updates – French (123).
Task Overdue type:
Parameter
Description
[project user type]
Recipient’s project user type. English values are: “task claimant," “task assignee,” “task creator,” and “project creator.”
[project full name]
The task’s project name including locale and ID. For example, Weekly Updates – French (123).
Task Restart type:
Parameter
Description
[project user type]
Recipient’s project user type. English values are: “task claimant," “task assignee,” “task creator,” and “project creator.”
[project full name]
The task’s project name including locale and ID. For example, Weekly Updates – French (123).
Task Still Running type:
Parameter
Description
[project full name]
The task’s project name including locale and ID. For example, Weekly Updates – French (123).
[task workflow engine location]
The identity (hostname, WorldServer instance name, workflow engine number) of the workflow processor that is performing the task's current automatic step.
Parent Topic
WorldServer Administration