About Email
Account data instances
|
|
| New | Outgoing Mail | Incoming Mail | History | More... |
Use an e-mail account data instance to record the e-mail servers and accounts that your system uses to send outbound e-mail correspondence generated during flow processing. The Pega-ProCom agent uses information in an e-mail account data instance to process outgoing e-mail and for Short Message Service texting.
The flow correspondence feature is implemented by a set of
standard activities and rules. The standard activity
Work-.getEmailSenderInfo looks for an e-mail
account with a name that matches the class group of the work
object and the Type set to
Notify. If the activity does not find a match, it
uses the e-mail account named Default instead.
Therefore, always maintain one e-mail account named Default so the activity will always find an account. If different applications need to use different e-mail accounts, use the name of the application’s class group as the name of the e-mail account so the standard activities will find it. For example: HomeLoan.Notify.
This form includes a tab named
Incoming Mail. In versions of
Process Commander prior to 5.3, this tab was used to configure
e-mail accounts that managed incoming e-mail. The Incoming Mail tab remains on the form to
support backward compatibility, but as a best practice in new
development, use email services to manage incoming email.
Use the Rules by Type explorer to list e-mail account data instances on your system.
To create e-mail accounts, use the Email Accelerator. The accelerator creates the rules and data objects to support both outbound e-mail through e-mail account data objects, and inbound e-mail with email service rules. To start the accelerator:
Integration icon to
access the Integration slice.The Data-EmailAccount class holds email account data instances. They are part of the SysAdmin category.
Home