About Email Account data instances |
|
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.
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.
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, in the Finance-LoanSystem-HomeLoan class group, the Account Name is HomeLoan and the Account Type is Notify.
Use the Records Explorer to list email account data instances on your system.
You can also access email accounts on the Outbound tab of the Email landing page by selecting Designer Studio > Integration > Email > Outbound Email.
The Data-EmailAccount class holds email account data instances. They are part of the Integration Resources category.
When you create an email account data instance and save it, the system automatically associates it with a ruleset of the application rule for the current application. This association assists with application packaging. You can update the associated ruleset using the field in the upper right corner of the form. See Identifying parts of rule and data forms.
If there is no ruleset associated with the data instance (for example, for existing instances not previously associated with a ruleset), the Associated Ruleset displays [none].