FSM Notification Email Definition Reference
This reference describes the standard notification email definitions, their properties, and their message associations.
This topic includes the following sections:
Case Service Report Email
The following table describes the standard behavior of notification.caseEmail.servicereport.
|
Setting |
Standard Behavior |
|---|---|
|
Author |
Employee assigned to the case. |
|
Recipients |
Email address on the case. |
|
Email template |
|
|
Email-body data |
Case record under |
|
Message association |
Case and its contact, where supplied. |
|
Attachment |
Case service report PDF. |
CRM Task Service Report Email
The following table describes the standard behavior of notification.taskEmail.servicereport.
|
Setting |
Standard Behavior |
|---|---|
|
Author |
Task assignee. |
|
Recipients |
Email address on the linked case. If the task has no linked case, the customer search uses the primary contact's email address, falling back to the customer's email address. |
|
Email template |
|
|
Email-body data |
Task record under |
|
Message association |
Linked case and the contact found on that case, where supplied. |
|
Attachment |
CRM Task service report PDF. |
The customer recipient search is used only when there is no linked case. An empty case email address doesn't itself cause the customer search to be used.
Project Task Service Report Email
The following table describes the standard behavior of notification.projectTaskEmail.servicereport.
|
Setting |
Standard Behavior |
|---|---|
|
Author |
First resource returned by the project task assignment search. |
|
Recipients |
Primary contact's email address on the linked project. |
|
Email template |
|
|
Email-body data |
Project task under |
|
Message association |
Linked project. |
|
Attachment |
Project task service report PDF. |
The first project task resource returned is not necessarily a designated lead resource.
FSM Mobile Login Email
The following table describes the standard behavior of notification.employeeEmail.mobilelogin.
|
Setting |
Standard Behavior |
|---|---|
|
Author |
The standard definition supplies no explicit author. The sending process uses the current execution user's ID. |
|
Recipients |
Employee's email address. |
|
Email template |
|
|
Email-body data |
Employee under |
|
Message association |
Employee. |
|
Attachments |
None supplied in the standard definition. |
This template reference is relative to the FSM script folder in the File Cabinet. For a custom template stored elsewhere, use its full File Cabinet path.
Email Definition Properties
The following table describes properties for each named email, such as notification.taskEmail.servicereport.
Template tags can supply values within email definitions. Their resolved values must have the type and structure accepted by the property. For information about syntax and evaluation details, see FSM Expressions and Template Tags. The notification service renders these definitions, which differ from FSM Mobile element expressions.
|
Property |
Resolved Value |
Standard Value or Fallback |
Effect |
|---|---|---|---|
|
|
Employee internal ID. |
Record-specific standard definition. If the resolved author is not supplied or evaluates as false, the send function uses the current execution user's ID. |
Sets the sender. |
|
|
Recipient address or collection accepted by NetSuite email sending. |
Record-specific standard definition. The renderer's empty-array fallback supplies no recipients. |
Sets the primary recipients. |
|
|
Email address or collection of addresses. |
Not supplied in the standard definitions. |
Sets carbon-copy recipients. |
|
|
Email address or collection of addresses. |
Not supplied in the standard definitions. |
Sets blind-copy recipients. |
|
|
Email address string. |
Not supplied in the standard definitions. |
Sets the reply-to address. |
|
|
String. |
If omitted or empty, the rendered email body's |
Sets the message subject. |
|
|
Object containing |
Record-specific standard definition. |
Defines the HTML message body. |
|
|
Collection of files or report definitions that resolves to an attachment array. |
Service report PDF for the three service email definitions. No attachment for the FSM Mobile login email. |
Attaches files to the message. |
|
|
Object containing message-association properties. |
Record-specific standard definition. |
Associates the sent message with NetSuite records. |
|
|
Boolean value. |
|
Requests bounceback notifications to the sender. |
|
|
Boolean value. |
|
When |
internal: true controls Message visibility. It doesn't prevent email delivery to an external recipient.
A notification needs a valid sender, at least one valid recipient, and permissions for the execution role to send. The author fallback doesn't select a designated business sender.
Associating Messages with Records
records associates the sent message with NetSuite records. It doesn't load template data, choose recipients, or attach record files to the email. The table describes the properties for associating messages with records.
|
Property |
Value |
Purpose |
|---|---|---|
|
|
Internal ID. |
Associates the message with a transaction or opportunity. |
|
|
Internal ID. |
Associates the message with a case or campaign. |
|
|
Internal ID. |
Associates the message with an entity, such as a contact, customer, project, or employee. |
|
|
Custom record type identifier. |
Identifies the custom record type. Use with |
|
|
Custom record internal ID. |
Identifies the custom record instance. Use with |
Don't assume that setting activity to a CRM task or project task ID provides a task message association. The standard task email associates its message with the linked case and contact. The standard project task email associates its message with the project.
If an association is not required, omit it when creating an email definition. For an inherited association, remove the relevant property using the configuration merge rules.