Each Template can be assigned a recipient email address. When a Design based on that Template is ordered by a user, the designated recipient for that item receives an email to let them know the Design has been ordered. In this way, although an order may contain many items, only those relevant to the designated recipient will be included in the notification to them.
If the user orders more than one Design with the same designated recipient email address, the items are batched together into a single email to prevent spam. If a Design is subject to approval, the notifications are postponed until the item is approved and ready to produce. Even if an order has several Designs with the same designated recipient, the recipient will receive multiple email batches if some of the items in the order are subject to approvals. Each Template can be allocated multiple recipients, with each recipient being treated individually for the purposes of receiving email batches.
The notifications are capable of including download links to the final output artwork. if these are included in the notification, the email notifications to the designated recipient are delayed until the artwork has been rendered.
The Templates configured to display the Download Now link on their Form-Filling page are not processed. The notification is not sent when the link is clicked and the template downloaded.
Links to the final output artwork can be included in the notifications. The output folder needs to be web-accessible, that is, the correct user-permissions must be set, and it also must be located inside of an existing website’s virtual directory.
For each ordered design, the result is represented by one or more output files. The email body template can contain placeholders for these output files, for instance the <DocumentPropertyExtra:LinksToOutputFilesHtml> tag. There can also be a nested loop in the inside of the Document Loop:
<DocumentLoop>
<OutputFileLoop>
<a href=’<OutputFile:Url>’><OutputFile:Name></a> (<OutputFile:Size>)<br />
</OutputFileLoop>
\&#xNAN;</DocumentLoop>\
If any Output File tags are included in the configuration, the Product Notifications wait until the output is generated for the relevant file before sending the email notification.
The drop-down lists above the email body contain placeholders for Properties and Fields.
\&#xNAN;Properties are fixed and will always appear in the list, for instance:
\&#xNAN;<OrderProperty:DateTimePlaced>
\&#xNAN;<UserProperty:LogonName>
\&#xNAN;User Fields are defined in Users > Profile Fields > User Fields,
\&#xNAN;Order Fields are defined in Purchasing > Checkout > Payment Step.
Any new user or order fields created will appear in these lists of available fields in the configuration. Changing the name of a field or deleting it will not be detected by the notification configuration and these fields will cease to work in the notifications, as the placeholder’s referenced field will no longer exist.
If placeholders don’t contain any value when the email contents are generated, the resulting email text shows the word NULL for the missing value. The Deployment Administrator who configures the notifications is also responsible for ensuring the notification text contains meaningful values.
\