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.
If your PRPC 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 PRPC application has email capabilities enabled, your application can initiate and process email- based conversations. When an email is sent from PRPC, a key is generated and attached to the email. When the reply is received, the message is attached to the work item 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 Account 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 PDN article How to support email 'conversations'. GRP-461
Beginning in V6.2 SP2, perform approvals or other actions on work items using email-based work processing. Enable this functionality using a standard Notify activity and the correspondence name pzEmailActions, which applies to Work-, belonging to Pega-ProcessEngine RuleSet. The approver receives an email that contains hyperlinks to non-local flow actions. The approver clicks on the appropriate flow action and adds comments as needed, then sends the response. The email is received by an email listener that validates the response using the service activity pyCreateAndManageWorkFromEmail, then delegates processing to the pyProcessEmailRequest agent. A copy of the response is attached to the created work item. For more information see Understanding email-based work processing.
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 PDN article How to send encrypted email messages.
When the system sends outbound email, if the connection to the email server fails, messages are automatically queued for resending later. The number of resend attempts made is defined in the Pega-ProcessEngine.pyEmailMaxResends system setting.
When a customer has a Connector rule for an HTTP-based protocol such as HTTP, SOAP, REST, and sometimes Email, they may point to an SSL-enabled ("https") endpoint. The service that is connected to will provide an SSL certificate in order to identify itself and secure the connection.
PRPC relies on the Application Server in order to "trust" the certificate that another service provided. When PRPC is deployed in tomcat, this usually means that the default java trust store is in use. IBM Websphere has its own trust store, controlled in the Admin Console.
When the certificate provided by a service is not in the trust store, or otherwise not trusted (for instance, it is out of date or issued to a different organization), PRPC cannot complete the connection and an exception such as "Peer not authenticated" results.
It is the responsibility of the customer to ensure that the application server's trust store is set up correctly.
See PDN article About Email and linked articles for examples and additional documentation.
|
Short Message Service, work type |
|
About Agent Schedule data instances About Service Email Service rules About Email Listener data instances |
|
Atlas — Standard activities — Extension points |