Designing email notice templates

Last update 2021-01-03

New user account emails are configured separately, based on the PDXpert Server service environment. For more information, see the PDXpert service configuration setting in this Install Guide.

This is an advanced topic for PDXpert 14.0 and later. You must have administrator permissions to add and delete email templates. If you want to replace email content, you should know basic features of the HTML language.

Although you can use a plain text editor like Windows Notepad or Notepad++, there's also a wide variety of free and paid HTML editors available. (Word processors like Microsoft Word are not as useful.) The HTML examples (below) can be used as a starting point for pasting into an editor. Search the web for html editor

PDXpert PLM software sends event-driven email notices to users. This application note shows how to add HTML static content and CSS styles; it doesn't change the email system behavior.

Introduction: How email templates work

PDXpert can send email notices when certain events occur. For example, when a new user account is made, the person can get an email that shows the PDXpert client application download, as well as log-in information. Other notices are sent by the PDXpert server to users who must act on a change form, or who is an observer to the change workflow action. And, there are emails related to tasks assigned by one user to another user.

PDXpert uses a standard set of email templates. Emails always have a plain-text Subject line and HTML-formatted Content. In most cases, you can replace PDXpert's standard templates with your own templates. Replace the standard email template with a new template on the Tools menu ➔ Email Management window.

HTML and non-HTML formats§

There are four possible subject+content options using:

A new the plain-text subject line, and PDXpert's standard content.
Plain-text subject lines for different workflow paths, and using PDXpert's standard content.
Custom HTML with a common plain-text subject line (contained in an HTML <title>), with custom HTML-formatted content (in the <body>).
Custom HTML subject lines for different workflow paths: unformatted subject line (<title>) with HTML-formatted content (<body>).

Only change workflow notices can have path-based subject lines; task notices don't have paths.

Plain text: If you do not use a custom HTML body, then you can specify only a custom email subject; the standard email content is used. Subject text is merged with any workflow or task parameter values, and any excess length is deleted, before your email is sent.

HTML text: A custom HTML body begins with <!DOCTYPE or <html. The complete HTML is not validated; PDXpert expects that you validated the HTML before adding it to the system. The current parameter values are merged with (1) the HTML <title> element, and (2) your HTML <body> ... </body> element. The result is sent as the email.

The following Email Management window shows some example templates:

A change actor's HTML-formatted template, with path-based subjects.
A change observer's notice, where only the email subject is changed; the body uses the system's standard format.
An HTML-formatted notice sent to a person who's been assigned a task.
An empty template, which uses both the standard email subject and email body when the assigned task is completed.

Plain text subject template §

If you want to change only the email subject, then enter the new subject as plain text:

You have a new task!

HTML template §

A basic HTML email template looks like this:

<!DOCTYPE html><html lang="en">

<title>Actor email subject (one line of valid HTML, no CSS styles)</title>

</head>

<body>

Actor email body as valid HTML.

The body can contain multiple lines, and can use styles.

</body>

</html>

Subject lines are always a single line of unformatted text: no colors, or bold, italic or underline styles.

Subject line details §

The template textbox can contain only the email subject as plain text, or an HTML document's <title> element can contain the subject line.

PDXpert removes all newline characters, tabs and doubled spaces. Most parameters can be used in the subject. Some parameters may include a lot of text and are not practical: after merging parameter values into your template, PDXpert sends only the first 140 characters in the subject line.

PDXpert's standard email subject line is used when:

the template textbox is empty,
the HTML document doesn't begin with <!DOCTYPE or <html, or
the HTML document doesn't have a <title>, or
the HTML document <title> element is empty.

Custom subject line §

The subject line can be a simple text string, such as A change has been processed. This text is used for every email, regardless of the change workflow path.

However, we can insert more details about the current change form. The subject line is used for every change workflow path, so simple information is best; for example, the change type, the number, and its new lifecycle:

Change form {ChangeTypeShort} {ChangeNumber} is now {ChangeNewLifecycle}

The parameters {ChangeTypeShort} {ChangeNumber} and {ChangeNewLifecycle} are selected from the set of available change workflow parameters. There's a separate set of assigned task notice parameters.

Path-based subject line for change workflow §

You can specify a unique subject line for every path on the change workflow diagram. If the subject line begins with the characters |Pn=, then the rest of the line is used as the subject for workflow Path n. You can define as many path-based subjects as you want; any paths you don't define use the standard subject line. For example, change forms moving along workflow Path 3 can show a subject line as:

|P3={ChangeEditor} routed {ChangeTypeShort} {ChangeNumber} for approval [{ChangePath}]

Content details §

PDXpert's standard email content is used when:

the template textbox is empty, or
the HTML document begins with <!DOCTYPE or <html, and doesn't end with </html>, or
the HTML document doesn't have a <body>

Design hints §

Writing HTML for email is not the same as designing a web page – web browsers are better than email clients. Email software may ignore shared styles in the <head> or in elements like <table> or <div>. In the examples below, you may see that each element repeats the same paragraph style. Test your HTML using common email clients (Outlook, Thunderbird, Hiri, etc.), as well as corporate applications like CRM and ERP.
Don't use embedded or linked images, such as a company logo. Images and links are often blocked by antivirus, and may prevent delivery of emails outside of your company network. Similarly, limit use of URLs such as company website.
All date paramenters end in ...Date}, such as {TaskDueDate}), and show a sortable date without the time (for example, 2021-03-21). Before formatting, date parameters are converted from UTC to the PDXpert server's local time and selected culture. You can add an optional date format string using @, such as {TaskDueDate@d MMM yyyy} (without double-quote) or {TaskDueDate@"d MMM yyyy"} (with double-quote). The format string must conform to a standard or custom .NET date format. Emails that go to other countries should use a culture-independent format that all users understand. It's best to use a format that doesn't include the time.
An HTML template with an empty <title></title> element sends an email using the standard subject line with your custom HTML content.
An HTML template with an empty <body></body> element sends an email with only a subject line and no content.
In the examples, the subject line often contains the {ChangePath} numeric value. This is useful for database queries or transforms that track the workflow history.
Quoted attribute values may use single quotes: lang='en' instead of lang="en". Some email clients may not support single quotes.
PDXpert 15.0 adds identifier attributes to selected HTML elements in standard templates.§

You can add similar id="" values for parsing your own HTML code. For example:

<!DOCTYPE html>

...

{action to be taken} {review detail}

<hr>

{change description}

...

</html>

When the change workflow is Routed, reviewers may receive slightly different {action to be taken} text:
- Must act group: Your group must review this change.
- Can act group: Your group can review this change for a short time only.
The {review detail} may contain HTML like

Approved by {reviewing group} reviewer {reviewing person} Comments: {person's comment}

Use the id="" values in a SQL query to parse email content in the Email table's Body column.

SELECT

...

SUBSTRING([GroupStart], 0, CHARINDEX('<', [GroupStart], 0)) AS [ReviewGroup]

...

FROM

(

SELECT

 ...

 ,CASE

 WHEN CHARINDEX('id="group"', [Body], 0) = 0 THEN ''

 ELSE REPLACE([Body], SUBSTRING ([Body], 0, CHARINDEX('id="group"', [Body], 0) + LEN('id="group"') + 1), '')

 END AS [GroupStart]

 ,...

)

...

Template descriptions §

Change workflow actor & observer §

Standard subject §

Change form {ChangeTypeShort} {ChangeNumber} is now {ChangeNewLifecycle} (moved from {ChangeOldLifecycle})

Standard body: Actor §

This email is sent to users who are expected to act: the analyst, reviewing groups' members, etc. Messages in your release may be different.

Your action on this change is needed.

{ChangeReviewSummary}

{ChangePrimaryDiscussion}

You received this email from PDXpert® software based on your assigned role and this change's workflow. Contact your PDXpert administrator to unsubscribe.

Standard body: Observer §

This email is sent to interested persons who do not actively participate in making, processing or reviewing the change form. Messages in your release may be different.

You're an observer of this change. See how this change affects you.

{ChangeReviewSummary}

{ChangePrimaryDiscussion}

You received this email from PDXpert® software based on your assigned role and this change's workflow. Contact your PDXpert administrator to unsubscribe.

Change workflow parameters §

The following parameters can be used in the HTML template, and will be replaced by the actual change form values.

{ChangeAnalyst}

The person name of change form's assigned Analyst.

{ChangeClassification}

The change form's displayed Change classification selection.

{ChangeEditor}

The name of the person who acted on the change form, causing it to move along the current path, from the old lifecycle state to the new lifecycle state.

{ChangeEffect}

The change form acts on its affected items as either an Executing or Advisory change form. The change form template's Release/cancel iterations when change is released checkbox sets this value.

{ChangeNewLifecycle}

The ending lifecycle state of the change form's current path. For example, if the change form is moving along path 03, then the {ChangeNewLifecycle} is replaced with Routed.

{ChangeNumber}

The change form's assigned Number value.

{ChangeOldLifecycle}

The beginning lifecycle state of the change form's current path. For example, if the change form is moving along path 03, then the {ChangeOldLifecycle} is replaced with Originated.

{ChangeOriginator}

The person name of change form's assigned Originator (Trustee).

{ChangeOriginDate}

The change form's Originated date. See note 1.

{ChangeOwner}

The full Owner name for the change form owner, which is always the home organization. For example, Acme Manufacturing Company.

{ChangeOwnerShort}

The display name for the change form's owner (always the home organization). For example, Acme.

{ChangePath}

The current numeric (1, 2, …, 25) transition path, matching the paths shown on the Change Forms collection member's Workflow page.

Although the help topic's workflow diagram shows all paths with two numeric characters, you can also use normal numbers 1 to 9 for the path identifier. That is, either |P01= or |P1= is accepted.

{ChangePrimaryDiscussion}

The complete text contained in the primary discussion (often labeled as Change description.) Although this parameter can be used in the email Subject, it's not recommended because the entire subject line is limited to 140 characters.

{ChangePriority}

The change form's displayed Priority selection.

{ChangeProblemSource}

The change form's displayed Problem source selection.

{ChangeReason}

The change form's displayed Change reason selection.

{ChangeReviewComment}

The reviewing person's comment that's included with the response. See note 2.

{ChangeReviewDate}

The date of the review. See notes 1 & 2.

{ChangeReviewGroup}

The reviewing group's name. See note 2.

{ChangeReviewParticipation}

The reviewing group's participate: Must act or Can act. See note 2.

{ChangeReviewResponse}

The reviewing person's selected response, such as Approve change. See note 2.

{ChangeReviewSummary}

The reviewing group name, reviewer, response and comment. See note 2.

{ChangeSecondaryDiscussion}

The complete text contained in the secondary discussion (often used for background or supporting details) Although this parameter can be used in the email Subject, it's not recommended because the entire subject is limited to 140 characters.

{ChangeType}

The change form's change Type name, as defined in the collection member.

{ChangeTypeShort}

The change form's change Type abbreviation, as defined in the collection member.

Notes

The date can be formatted using a .NET format specifier string, like {ChangeOriginDate@d MMM yyyy}.
This parameter is available only for "incomplete review" emails sent on Paths 8 to 13, and Path 16; it's blank for all other paths.

Change workflow examples §

Custom subject with standard body: Observer §

Observing {ChangeTypeShort} {ChangeNumber}, now at {ChangeNewLifecycle}

Workflow notice summary: Actor §

Use this template, and then move a change to a new workflow lifecycle state, to see the parameter values.

HTML

<!DOCTYPE html><html lang="en"><head><meta charset="utf-8">

<title>EmailNoticeChangeActor for Path {ChangePath}</title>

</head>

<body>

EmailNoticeChangeActor key

{Name}: Current value

ChangeAnalyst: {ChangeAnalyst}

ChangeClassification: {ChangeClassification}

ChangeEditor: {ChangeEditor}

ChangeEffect: {ChangeEffect}

ChangeNewLifecycle: {ChangeNewLifecycle}

ChangeNumber: {ChangeNumber}

ChangeOldLifecycle: {ChangeOldLifecycle}

ChangeOriginator: {ChangeOriginator}

ChangeOriginDate: {ChangeOriginDate}

ChangeOwner: {ChangeOwner}

ChangeOwnerShort: {ChangeOwnerShort}

ChangePath: {ChangePath}

ChangePrimaryDiscussion: {ChangePrimaryDiscussion}

ChangePriority: {ChangePriority}

ChangeProblemSource: {ChangeProblemSource}

ChangeReason: {ChangeReason}

ChangeReviewComment: {ChangeReviewComment}

ChangeReviewDate: {ChangeReviewDate}

ChangeReviewGroup: {ChangeReviewGroup}

ChangeReviewParticipation: {ChangeReviewParticipation}

ChangeReviewResponse: {ChangeReviewResponse}

ChangeReviewSummary: {ChangeReviewSummary}

ChangeSecondaryDiscussion: {ChangeSecondaryDiscussion}

ChangeType: {ChangeType}

ChangeTypeShort: {ChangeTypeShort}

</body>

</html>

Path-based subject line with custom body: Actor §

The body contains the change description:

ACT NOW

{ChangePrimaryDiscussion}

Information in this email is proprietary.

HTML with path-based <title> for the subject line

<!DOCTYPE html><html lang="en"><head><meta charset="utf-8">

<title>

|P1={ChangeTypeShort} {ChangeNumber} assigned to {ChangeOriginator} [{ChangePath}]

|P2={ChangeTypeShort} {ChangeNumber} submitted for analysis [{ChangePath}]

|P3={ChangeTypeShort} {ChangeNumber} routed for approval [{ChangePath}]

|P4={ChangeTypeShort} {ChangeNumber} analyzed and returned for update [{ChangePath}]

|P5={ChangeTypeShort} {ChangeNumber} analyzed and routed for approval [{ChangePath}]

|P6={ChangeTypeShort} {ChangeNumber} is Canceled [{ChangePath}]

|P7={ChangeTypeShort} {ChangeNumber} returned for update while routed [{ChangePath}]

|P8={ChangeTypeShort} {ChangeNumber} disapproved and returned for update [{ChangePath}]

|P9={ChangeTypeShort} {ChangeNumber} is Rejected after it was disapproved [{ChangePath}]

|P10={ChangeTypeShort} {ChangeNumber} stopped after it was disapproved [{ChangePath}]

|P11={ChangeTypeShort} {ChangeNumber} is Canceled after it was disapproved [{ChangePath}]

|P12={ChangeTypeShort} {ChangeNumber} approved and routed to the next group(s) [{ChangePath}]

|P13={ChangeTypeShort} {ChangeNumber} accepted and must be released [{ChangePath}]

|P14={ChangeTypeShort} {ChangeNumber} is Released after all reviewers approved [{ChangePath}]

|P15={ChangeTypeShort} {ChangeNumber} is Canceled after it was routed [{ChangePath}]

|P16={ChangeTypeShort} {ChangeNumber} held [{ChangePath}]

|P17={ChangeTypeShort} {ChangeNumber} returned for update after it was held [{ChangePath}]

|P18={ChangeTypeShort} {ChangeNumber} routed for approval after it was held [{ChangePath}]

|P19={ChangeTypeShort} {ChangeNumber} is Canceled after it was held [{ChangePath}]

|P20={ChangeTypeShort} {ChangeNumber} returned for update after it was disapproved [{ChangePath}]

|P21={ChangeTypeShort} {ChangeNumber} is Rejected after it was disapproved [{ChangePath}]

|P22={ChangeTypeShort} {ChangeNumber} is Canceled after it was disapproved [{ChangePath}]

|P23={ChangeTypeShort} {ChangeNumber} returned for update after it was accepted [{ChangePath}]

|P24={ChangeTypeShort} {ChangeNumber} is Released after it was accepted [{ChangePath}]

|P25={ChangeTypeShort} {ChangeNumber} is Completed [{ChangePath}]

</title>

</head>

<body>

ACT NOW

{ChangePrimaryDiscussion}

Information in this email is proprietary.

</body>

</html>

Task assigned & completed §

Standard subject: Task assigned §

Task due {TaskDueDate} for {TaskItemOwnerShort} {TaskItemType} {TaskItemNumber}

Standard subject: Task completed §

Task {TaskStatus} for {TaskItemOwnerShort} {TaskItemType} {TaskItemNumber}

Standard body: Task assigned §

This email is sent to the person who is assigned a task.

{TaskItemFullInfo}

Priority: {TaskPriority}

Assigned by: {TaskAssignedByPerson}

Assigned on: {TaskAssignedDate}

Due on: {TaskDueDate}

Task description: {TaskDescription}

Standard body: Task completed §

This email is sent to the person who assigned the task. The task's status may be set to Completed, Deferred, or Canceled.

{TaskItemFullInfo}

Priority: {TaskPriority}

Assigned to: {TaskAssignedToPerson}

Assigned on: {TaskAssignedDate}

Due on: {TaskDueDate}

Status: {TaskStatus}

Status on: {TaskStatusDate}

Task description: {TaskDescription}

Parameters §

The following parameters can be used in the HTML template, and will be replaced by the actual task values.

{TaskAssignedByPerson}: Name of the person shown in the task's Assigned by field.
{TaskAssignedDate}: Date shown in the task's Assigned on field. See note 1.
{TaskAssignedToPerson}: Name of the person shown in the task's Assigned to field.
{TaskDescription}: The complete content of the Task description field.
{TaskDescriptionShort}: The shortened content of the Task description field. See note 2.
{TaskDueDate}: Date shown in the task's Due on field. See note 1.
{TaskItemClass}: The item's class name: Part, Document or Change.
{TaskItemDescription}: A simplified version of the task's part, document or change form description. See note 2.
{TaskItemNumber}: The part, document or change form Number of the item that contains the assigned task.
{TaskItemOwner}: The full Owner organization name of the item that contains the assigned task. For example, Acme Manufacturing Company.
{TaskItemOwnerShort}: The display name for the organization that owns the item that contains the assigned task. For example, Acme.
{TaskItemRevision}: The part or document pending revision identifier. (Empty for change forms.)
{TaskItemSummary}: The part, document or change form item summary: owner display name; item type abbreviation; item number; pending revision (if any); and the item's simplified description. See note 2.
{TaskItemType}: The full Type name of the item that contains the assigned task. For example, Assembly.
{TaskItemTypeShort}: The abbreviation (display name) for the item type of the item that contains the assigned task. For example, Assy.
{TaskPriority}: The selected value shown in the task's Priority field.
{TaskSendingPerson}: The name of the person who acted on the task, causing it to send the email notice. This could be the person who assigned the task, who responded to the assignment, or an analyst or trustee.
{TaskStatus}: The selected value shown in the task's Status field.
{TaskStatusDate}: Date shown in the task's Status on field. See note 1.

Notes

The date can be formatted using a .NET format specifier string, like {TaskAssignedDate@m}.
This parameter is up to 140 characters, after extra spaces and line breaks are removed.

Task assignment examples §

Standard body with standard subject §

Don't put any text into in the template's textbox.

Standard body with custom subject §

{TaskPriority} priority task for {TaskItemClass} {TaskItemNumber}

Assigned task summary §

Add this template, and then assign a task to another person, to see the parameter values in the task email.

<!DOCTYPE html><html lang="en"><head><meta charset="utf-8">

<title>Assigned task email subject (one line of valid HTML & no CSS styles)</title>

</head>

<body>

Assigned Task

{Name}: Current value

TaskAssignedByPerson: {TaskAssignedByPerson}

TaskAssignedDate: {TaskAssignedDate@d MMM yyyy}

TaskAssignedToPerson: {TaskAssignedToPerson}

TaskDescription: {TaskDescription}

TaskDescriptionShort: {TaskDescriptionShort}

TaskDueDate: {TaskDueDate@d MMM yyyy}

TaskItemClass: {TaskItemClass}

TaskItemDescription: {TaskItemDescription}

TaskItemNumber: {TaskItemNumber}

TaskItemOwner: {TaskItemOwner}

TaskItemOwnerShort: {TaskItemOwnerShort}

TaskItemRevision: {TaskItemRevision}

TaskItemSummary: {TaskItemSummary}

TaskItemType: {TaskItemType}

TaskItemTypeShort: {TaskItemTypeShort}

TaskPriority: {TaskPriority}

TaskSendingPerson: {TaskSendingPerson}

TaskStatus: {TaskStatus}

TaskStatusDate: {TaskStatusDate@d MMM yyyy}

</body>

</html>

New user account created §

The standard email template cannot be completely replaced, and is not shown in the Email Management tool. Set the values using the PDXpert service configuration file. For more information, see the PDXpert service configuration setting in this Install Guide.

The new user account email is sent when the administrator adds a new user account. The user account must refer to a person that already has an email account.

This email notice's subject cannot be changed. The email body can be adjusted to set the service name (HostName); the service base port number (ServiceTcpPort) that affects downloading the client; or the preferred network location of the installer download (ClientInstallerPath).

Other parameters, such as {user password}, are automatically set by the system and cannot be changed.

Standard subject §

PDXpert client setup & user account log-in

Standard body §

If the PDXpert PLM client is not installed, download this file to install the software:

http://{HostName}:{ServiceTcpPort}/client/setup

To use PDXpert software:

Run the PDXpert PLM application.
Enter your account name: {user name}
Enter your account password: {user password}
Enter the server name (or IP address): {HostName}
Click the OK button.

Manage your password by selecting the Passwords... command from the Tools menu.

If you need help, contact {administrator name} or press the F1 key on your keyboard to open the PDXpert PLM help file.

This application note was relevant to the PDXpert software release that was current at time of publication. Product changes since that time may affect its utility. We'd be happy to assist you in assessing the applicability of this note to your situation.

Designing email notice templates

Introduction: How email templates work

HTML and non-HTML formats§

Plain text subject template §

HTML template §

Subject line details §

Custom subject line §

Path-based subject line for change workflow §

Content details §

Design hints §

Template descriptions §

Change workflow actor & observer §

Standard subject §

Standard body: Actor §

Standard body: Observer §

Change workflow parameters §

Change workflow examples §

Custom subject with standard body: Observer §

Workflow notice summary: Actor §

HTML

Path-based subject line with custom body: Actor §

HTML with path-based <title> for the subject line

Task assigned & completed §

Standard subject: Task assigned §

Standard subject: Task completed §

Standard body: Task assigned §

Standard body: Task completed §

Parameters §

Task assignment examples §

Standard body with standard subject §

Standard body with custom subject §

Assigned task summary §

New user account created §

Standard subject §

Standard body §

Working within PDXpert

Working with other software applications

Product Info

Support Info

Company Info

Offer

Zero $ Subscription Zero license cost when moving all users into PDXpert from other solutions for the duration of your existing contract terms*

Offer

Zero $ Subscription Zero license cost when moving all users into PDXpert from other solutions for the duration of your existing contract terms*

Offer

Zero $ Subscription Zero license cost when moving all users into PDXpert from other solutions for the duration of your existing contract terms*

Offer

Zero $ Subscription Zero license cost when moving all users into PDXpert from other solutions for the duration of your existing contract terms*

Designing email notice templates

Introduction: How email templates work

HTML and non-HTML formats§

Plain text subject template §

HTML template §

Subject line details §

Custom subject line §

Path-based subject line for change workflow §

Content details §

Design hints §

Template descriptions §

Change workflow actor & observer §

Standard subject §

Standard body: Actor §

Standard body: Observer §

Change workflow parameters §

Change workflow examples §

Custom subject with standard body: Observer §

Workflow notice summary: Actor §

HTML

Path-based subject line with custom body: Actor §

HTML with path-based <title> for the subject line

Task assigned & completed §

Standard subject: Task assigned §

Standard subject: Task completed §

Standard body: Task assigned §

Standard body: Task completed §

Parameters §

Task assignment examples §

Standard body with standard subject §

Standard body with custom subject §

Assigned task summary §

New user account created §

Standard subject §

Standard body §

Working within PDXpert

Working with other software applications

Product Info

Support Info

Company Info

Book a Demo

Get a Quote