FSM Notification Addressing and Attachments
Field Service Management (FSM) uses email definitions to select senders, recipients, and attachments. For report preview and prerequisites, see FSM Service Reports and Notifications.
The native report action uses configured addressing. It does not open a recipient-selection dialog. The standard service-report definitions use the following sources.
|
Report |
Sender |
Primary Recipient Source |
|---|---|---|
|
Case |
Employee assigned to the case. |
The case email address. |
|
CRM task |
Task assignee. |
The linked case email address. When there is no linked case, the customer's primary contact email, falling back to the customer email. |
|
Project task |
First resource returned from the project task assignments. |
The linked project's primary contact email address. |
For a CRM task with a linked case, a blank case email does not activate the customer fallback. The standard case and project task definitions have no equivalent customer-email fallback. The first project task assignment returned is not necessarily a designated lead resource.
If the configured sender resolves to no value, the send function uses the current execution user. This fallback does not select a designated business sender or supply a missing recipient.
Configuration can select different recipients and include carbon-copy or blind-copy recipients, generated reports, and existing File Cabinet attachments. Standard service-report notifications attach one PDF. Other notifications can have no attachments. Opening a PDF successfully does not establish that the full email, its addressing, and all attachments can be sent.