Sending automated emails
The Creative Content team wants to generate an email to confirm receipt of each content request through the Content Request case type. The email acts as validation for the requester that the team receives the request.
In the current workflow, this step is prone to errors. There are occasions when Ren's team neglects to send the email and instances when the email is duplicated. There are also inconsistencies in the timing of the email and the information that it contains.
For Ren, automating the requester confirmation email process improves the consistency of the process and saves considerable time and manual effort.
To facilitate the automated email correspondence, Ren considers three simple questions:
- Who is going to receive the email?
- What information will the email contain?
- When, during the case life cycle, will the email be sent?
For Ren, the answers to each of the three questions are:
- The requester receives the email.
- The email contains the request type and case ID.
- The email is sent as the first step in the Processing stage.
With these questions answered, Ren clicks the Processing stage's Send confirmation step to open the contextual properties pane.
Identifying the email recipient
To define the email recipient, Ren fills in the boxes associated with the Send To portion of the contextual properties pane.
Email correspondence can be sent to one of several categories including:
- Email address: An email address can be entered manually.
- Field: An application field such as Requester email can be used to send an email.
- Participants: An email can be sent to one or more of the case’s stakeholders.
Ren defines the email recipient for his application by performing the following steps:
- In the navigation pane of App Studio, click Case types, and then click the Content Request case type.
- On the Processing stage, click the
- In the Step properties pane, in the Send to drop-down list, select Field.
- In the second drop-down list, select Requester email.
Note: This email address is required as part of the Enter request details step.
Next, Ren defines the template for the email notification.
Defining the email template
For Ren, defining the email template begins by entering Content Request Confirmation in the Subject text box. This input is the subject line of the email.
Next, Ren composes his email correspondence template.
Ren incorporates two Pega data fields in his email correspondence template:
- Request Type
- Case ID
These fields reference data from the specific case instance in the email that is generated.
To include these fields in the email template, Ren clicks theicon on the email template menu bar.
In the following figure, click on the + icons to learn more about inserting property fields into the body of an email message:
Ren defines the email template by performing the following steps:
- In the Send confirmation contextual properties pane, in the Subject field, enter Content Request Confirmation.
- Click Compose.
- In the Compose message dialog box, enter the following body text:
Thank you for submitting a request for a <<.RequestType>> to the Creative Content Team.
For your reference your Request ID is: <<.pyID>>
We will notify you by email when your request is complete.
The Creative Content Team
- Click Done.
- Click Save.
The following video details the process Ren uses to automate the Send confirmation step.
As a result of Ren's work, each time a requester submits a new Content Request case, they automatically receive a confirmation email.
Check your knowledge with the following interaction:
In your environment
In your own Pega environment, duplicate the steps Ren uses to generate an automated email. You can recreate the Email Requestor notification that Ren uses or automate an email that is associated with your own process.