Exploring email configurations
Use an email account data instance to record the email accounts that your system uses to send outbound email correspondence generated during flow processing and to receive inbound email. The Pega-ProCom agent uses information in an email account data instance to process outgoing email and for Short Message Service texting.
Email messages are a key part of the business processes that developers build in their Pega Platform applications. You can configure flows to send emails to work parties, including people outside your organization such as customers and vendors. Additionally, incoming email messages can deliver work items such as cases to your business processes. Review the limitations on email accounts to understand how they affect your application. For more information, see Email account limitations.
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 item and the Type set to
Notify. If the activity does not find a match, it uses the email account
named Default instead.
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, in the Finance-LoanSystem-HomeLoan class group, the Account Name is HomeLoan and the Account Type is Notify.
To see a list of email account data instances on your system, in the navigation panel of Dev Studio, click . You can also view your email accounts from App Studio. For more information, see Viewing your email accounts.
The Data-EmailAccount class holds email account data instances. They are part of the Integration Resources category.