Sends a specified e-mail message to a given recipient or group of recipients. You can define the recipients as users (people with user profiles in the Profile repository) or e-mail addresses.
Scenario editor display name: Send Notification
Examples:
Send notification with path My Web App:/en/email/complaint.jsp to address
mgarcia@example.com
Send notification with path My Web App:/en/email/complaint.jsp to address
mgarcia@example.com with site Budget Pet Supplies
Registers where Site is MyStore > Send notification with path Example
Corps Web App:/en/newMember.jsp to people Amy Stevens with site
Event's SiteNote that the site can be set by the preceding event, as shown in the last example above.
This element is designed for situations in which you want to notify a person or group in response to an earlier event in the scenario. For example, you might want to notify your Sales department if a site visitor displays a page showing pricing information about a new product. By contrast, the Send E-mail action (see below) is designed for situations in which you want to send a message as part of an e-mail campaign to a targeted group of site visitors.
Note that the EmailNotify action is persisted to the database only if the recipient is a user profile. Actions whose recipients are specified as e-mail addresses are not persisted.
Action Registry Tag | Value |
|---|---|
action name |
|
configuration component |
|
action execution policy | collective |
action error response | delete |
The EmailNotify action has the following parameters:
Parameter | Required | Description |
|---|---|---|
| no | The profile IDs of the people to whom this notification is sent. |
| no | The e-mail addresses to which this notification is sent. (Used in cases where there are multiple recipients). |
| no | The e-mail address to which this notification is sent. |
| no | The path of the template to send. Corresponds to the ACC option Users specify the fully qualified path of the e-mail template to send. If the document is outside the Dynamo document root because it is part of a non-DAS J2EE application, they must specify the application context root manually. This parameter reflects the way that users specified document paths in versions of Oracle Commerce Platform products before 6.0.0 and exists mostly for compatibility with those versions. |
| no | The path of the template to send. Corresponds to the ACC option Users specify the path of the e-mail template to send by selecting the template in a document picker dialog box. The path is automatically prepended with either the application context root (if the template is part of a J2EE application) or a flag indicating that the template is located in the Dynamo document root. |
| no | (Multisite environments) The Web site to use as the context for the template. Corresponds to the ACC option |
EmailNotifyConfiguration Component
The following example shows the properties file for the EmailNotifyConfiguration component, which you can use to define various settings for the EmailNotify action.
# Version: $Change: 246405 $$DateTime: 2002/07/10 17:43:59 $ $class = atg.process.action.EmailNotifyConfiguration defaultEmailInfo=/atg/scenario/DefaultTemplateEmailInfo emailSender=/atg/scenario/IndividualEmailSender profileRepository=/atg/userprofiling/ProfileAdapterRepository webAppRegistry=/atg/registry/WebApplicationRegistry # set to true if you want to render an email with the scenario subject's profile # but send the email to someone other than the scenario subject # renderTemplateWithProcessSubject=false
By default, the profile you can associate with an EmailNotify message is the profile of the person to whom it is sent, not the profile of the person passing through the scenario. This behavior means that any profile-related dynamic content that you include in the body of the message will reference the recipient’s profile. However, suppose you want to design a scenario that alerts your customer support department whenever a customer makes an unusually large purchase. You want to send the message to a support rep, but you want to include information from the customer’s profile in the body of the message (her login, order number, and order total, for example). To do this, you can set the renderTemplateWithProcessSubject property of the EmailNotifyConfiguration component to true. This setting uses the profile of the person going through the scenario to resolve any content in the body of the message, but sends the message to the person you specify when you create the EmailNotify action in the scenario editor.
Note that you can maintain two versions of the EmailNotify action, one with the renderTemplateWithProcessSubject property set to true and one with the property set to false.
