Skip to main content

 –

Configuring Pulse notifications on additional email accounts

Suggest edit Updated on November 29, 2021
Applicable to Hybrid mode applications

Enhance and categorize communication in your organization by creating multiple email accounts to send email notifications about Pulse messages. Consequently, users can quickly understand the context of the message, and as a result, process their work faster.

For example, you can configure an email account, such as HRServices@example.com, to send Pulse emails from the HR Services application, or SalesAutomation@example.com, to send Pulse emails from the Sales Automation application, so that users can quickly identify which application sends the notification.
Before you begin: Create an email account for your application. For more information, see Creating an email account.
  1. Copy the pyPulseNotificationsEmailAccount data transform that belongs to the Pega-Social ruleset, to your application ruleset:
    1. In the navigation pane of Dev Studio, click Records.
    2. Expand the Data Model category, and then click Data Transform.
    3. Click Create.
    4. In the Label field, enter a new name for the rule.
    5. In the Add to ruleset list, select your application ruleset.
    6. Click Create and open.
  2. On the Definition tab, in the Source column for the Param.PulseNotificationsEmailAccount target, enter your email account name, as in the following figure:
    Data transform for additional email accounts
    Sample configuration of data transform for sending Pulse notifications from an
                application-specific email account
  3. Click Save.
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us