Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Configuring an email notification channel

Updated on November 22, 2021

In Dev Studio, you can configure an email channel to send notifications to users. Users can reply to email notifications to post messages in a conversation.

  1. Click the Records Explorer and expand the Process category.
  2. Click Notification.
  3. Click the notification for which you want to configure an email channel.
  4. Perform one of the following actions:
    • To customize the email channel, go to 5.
    • To disable email notifications for all users, on the Channels tab, in the Email section, clear the Enable email check box, and then go to 6.
  5. If email notifications are enabled, customize the email channel by performing the following actions:
    1. In the Subject field, keep the default field value or enter the field value that holds your notification message for email notifications. Click the Open icon, to create a new field value or to open the field value that you specified.
    2. Optional: Enter parameters for the field value in the Parameters section.
    3. In the Correspondence field, enter a correspondence template for the email message body. Click the Open icon, to create a new correspondence or to open the correspondence that you specified.
    4. From the Default preference list, enable or disable the email channel for all the users in your application.
      This value is displayed as the default option for the email channel when users see their notification preferences at run time. They can update the preferences as needed.
  6. Click Save.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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