About Email Account data instances
|
|
| New | Outgoing Mail | Incoming Mail | History | More... |
Use an email account data instance to record the email servers and accounts that your system uses to send outbound email correspondence generated during flow processing. The Pega-ProCom agent uses information in an email account data instance to process outgoing email 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 email 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 email account named Default instead.
Therefore, always maintain one email account named Default so the activity will always find an account. If different applications need to use different email accounts, use the name of the application’s class group as the name of the email account so the standard activities will find it. For example: HomeLoan.Notify.
This form includes a tab named Incoming Mail. In versions prior to
V5.3, this tab was used to configure email accounts that managed incoming
email. 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 explorer to list email account data instances on your system.
To create email accounts, use the Email
Landing Page. The Email Landing Page has gadgets to create, edit, and view outbound and inbound email settings. To access the landing page:
the Integration area and then the 
Email landing page.The Data-EmailAccount class holds email account data instances. They are part of the SysAdmin category.
|
Atlas — Initial email account data instances |
SysAdmin category
Help Home