More about Email Account data instances |
Outgoing email that is formatted for display in an
email client program (such as Microsoft Outlook) may contain HTML
markup, and is produced by correspondence rules with an
EMAIL
correspondence type. Outgoing email that contains
only text can be produced by correspondence rules with a
PHONETEXT
correspondence type, and can be sent to a
SMS-capable phone as a text message.
To test your system's ability to send email:
Work-
class in your application.If your Process Commander server can access a keystore with an appropriate certificate, your application can send digitally signed email using the standard activity @baseclass.SendEmailNotification. See More about Correspondence rules.
If your Process Commander application has email capabilities enabled, your application can initiate and process email- based conversations. When an email is sent from Process Commander, a key is generated and attached to the email. When the reply is received, the message is attached to the work object and then a copy of the message is forwarded to the appropriate party. This functionality is initiated using the standard Work-.SendEmailCorr local action, and requires an Email Server instance, Service Package data instance, Email Listener data instance, and a Service Email rule. (For an example of the service rule, review the standard rule EmailDefault.Work-.ProcessEmails.)
For more information, see the Pega Developer Network article PRKB-25593 How to support email 'conversations.. GRP-461
If your application is required to send encrypted email, encrypted emails can be sent by using the @baseclass.SendEmailNotifcation activity and selecting the EncryptMessage parameter. For an example, see Pega Developer Network article PRKB-26087 How to send encrypted email messages.
See Pega Developer Network article PRKB-25085 About Email and linked articles for examples and additional documentation.