About Service
Email rules
|
|
| New | Service | Request | Response | History | More... |
Use email service rules to manage incoming email. An email listener monitors an email inbox on a server identified by an email server data instance. When messages arrive in that inbox, the email listener routes them to an email service rule. Typically the service activity for the email service uses the information in the message to create a work object. If there are any email attachments with the message, the service activity can attach them to the work object. If the message contains Delivery Status Notification information (an undeliverable message, for example), the service activity can route the message to the worklist of someone who investigates such matters.
Email services can process messages that contain plain text, HTML, or XML. If the incoming e-mail messages use SOAP over e-mail, use a SOAP service rule rather than an email service rule to process the message. You still use an email listener, but the listener routes the messages to a SOAP service rather than to an email service.
To create an email service, use the Email Accelerator.
Select Tools > Integration > Email
Accelerator. Alternately, from the Integration slice
(
) under Accelerators,
click the Email Accelerator link.
Use the Integration slice () to list the e-mail service rules in
your application. Use the Rules by Type Explorer to list all
the e-mail service rules available to you.
See Pega Developer Network article 
PRKB-25085 About Email and linked
articles for examples and additional documentation .
E-mail service rules belong to the Integration-Services category. They are instances of the Rule-Service-Email rule type.
|
How to unit test a Service Email rule |
|
Atlas — Standard Service Email rules |
Home