Skip to main content


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

Integrating Pega Sales Automation with Microsoft Outlook actionable messages

Updated on November 25, 2021

Use the actionable messages to perform quick actions within Outlook, for example to update the due date for a task or complete a task created in Pega Sales Automation.

Pega Sales Automation Implementation Guide Pega Sales Automation Implementation Guide Pega Sales Automation Implementation Guide

With the Outlook actionable messages feature, you can perform the following actions in the Outlook mailbox:

  • Update the due date for a task created in Sales Automation
  • Complete a task created in Sales Automation

Pega’s Outlook actionable messages support the following functionalities:

  • Receiving a reminder email notification for tasks created in Sales Automation
  • Enabling and sending task due notifications

Supported scenarios

Sending actionable messages via email is supported in the following scenarios:

  • The recipient must be an individual, not a group.
  • The recipient must be visible in the message. Do not put the recipient in the BCC field.
  • The recipient must have a mailbox on Outlook.com or Exchange Online in Office 365.

Prerequisites

  • For Actionable messages, you must create an impersonation account on Microsoft Exchange with impersonation privileges for all the users who wish to create tasks in the application. The impersonation account is used for sending email notification reminders for tasks.
  • Register your service with the actionable email developer dashboard. For more info refer to https://docs.microsoft.com/en-us/outlook/actionable-messages/email-dev-dashboard.
Note:
  • To receive email notifications in Outlook, when you create a task in Pega Sales Automation, do not set the Notify reminder to none.
  • There is an SLA configured crmTaskReminder that enables notifications in Outlook. You can use the notifications to update the due date or complete the task in Outlook.

Registering actionable messages service with email developer dashboard

  1. To register your service, create your provider using this link: https://outlook.office.com/connectors/oam/publish.
  2. From the Actionable Email Developer Dashboard copy the Provider Id (originator) value.
  3. In the Sender email address from which actionable emails will originate field, enter your Microsoft Exchange impersonation account.
  4. In the Target URLs field, enter the URL for actionable messages.
  5. In Scope of submission section, select Organization.
  6. Click Save.
Result: This registration request is sent to your organization's administrators with Exchange administrator or Global administrator permissions. The administrator can review and approve your request.

Once the submission is approved or auto-approved or by your administrator, it can take around one hour for the registration to take effect.

Configuring Actionable messages

Configure the Actionable messages to finalize the integration process.

  1. In the User portal, from the Explorer panel, select Administration.
  2. To enable actionable messages, go to Actionable Messages, and select the Enable actionable messages checkbox.
  3. Click Save.
  4. In the navigation pane of Dev Studio, click RecordsIntegration-ResourcesEmail Account , and then click Default.
  5. Replace the default value with your own impersonation account, and then click Save
  6. In the header of Dev Studio, in the search box, search for the ActionableMessagesOriginator Dynamic System Setting, and then replace the originator value with your Provider ID.

Tags

Pega Sales Automation 8.7

Have a question? Get answers now.

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

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

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