After you create the PulseNotifications email account that is used to send Pulse notifications, you can configure individual email accounts for each application for which you want to send Pulse notifications.
For example, you can configure an email account, such as [email protected], to send Pulse emails from the HR Services application. You can also configure an email account, such as [email protected] to send Pulse emails from the Sales Automation application, and so on.
Create an email account for your application by clicking.
Save the pyPulseNotificationsEmailAccount data transform, contained in the Pega-Social ruleset, to your application ruleset.
Set the Param.PulseNotificationsEmailAccount to your email account name.
Allow users to reply to email notifications with text or attachments and post the reply as a response to the original message.
- Configuring an email account for Pulse notifications
In Pulse, users can choose to receive email notifications when posts are made on cases that they are following. They also receive emails when other users reference them in posts, like their posts, and so on.
- Enabling users to respond to Pulse email notifications
Users can receive Pulse emails on cases that they are following and for which they choose to receive notifications. Users also receive emails when other users reference them in posts or like their posts. You can allow users to quickly post attachments or text as replies by responding to emails instead of logging in to the application.
- Configuring Pulse email notifications
In Pulse, you can choose to receive emails when another user references you, likes your messages, posts on your profile, posts comments on a conversation in which you are involved, or posts a comment on a case that you are following, provided that your application is configured to send emails.
- Integrating with an email provider
Create an email integration to manage incoming and outgoing email directly in your Pega Platform application. An email integration consists of an email account, email listener, email service rule, and service activity.