Purpose
E-mail messages are a key part of
the business processes that developers build in their Process
Commander applications. Flow processing typically sends email
messages to work parties, including people outside your
organization such as customers and vendors. Additionally,
incoming e-mail messages can deliver work objects to your
business processes.
Use the Email Accelerator to create the rules and data
objects needed to manage the following:
- Outgoing email messages generated by flow processing. For
outgoing email, the accelerator generates an email account
data object (Data-EmailAccount). First,
configure the standard email account named
Default
. Then, if different applications are to
use different email accounts, create additional email
accounts using the name of the work pool as the name of the
email account.
- Incoming email messages that deliver work to an
application. For incoming email, the accelerator sets up an
email service. It generates an email server data object, an
email listener data object, and an email service rule. The
data mapping settings in the service rule map the data from
incoming messages to standard email properties that your work
classes inherit from the Work- base class, and
map the response with two standard HTML rules. You can then
edit the data mapping settings as appropriate for your
configuration.
Before you begin
Before you begin, gather the following information.
For outbound e-mail
- The IP address or domain name of the SMTP host.
- The email account (e-mail address and password) that
Process Commander is to use.
- Whether the SMTP host is configured to use Secured Socket
Layer (SSL) .
- The name of the work pool (class group) for which you are
creating the account.
For inbound e-mail
- For the rules that manage the work object creation:
-
- The name of the work class and the flow
- The organization name
- The RuleSet and version to use
- For the email server object and the listener:
-
- The DNS name of the physical e-mail server (an e-mail
server data instance represents a physical e-mail
server)
- The port number for the e-mail server (typically 110
for POP3 and 143 for IMAP)
- The email protocol the server uses: POP3 or IMAP
- The account name and password for the email account
for Process Commander
- Whether the email server requires the listener to use
SSL to retrieve messages
- The name of the mail folder the listener
monitors
- If the email service needs to run as an authenticated
user, the operator ID it is to use
Starting the accelerator
- From the Developer portal home page, select the Integration icon to
access the Integration slice.
- Locate the Accelerators
area.
- Click the Email Accelerator link.
PDN Articles
See Pega Developer Network article PRKB-25085 About Email and linked articles
for examples and additional documentation.
Tools, accelerators, and wizards