When you configure an Email channel interface as a Pega Intelligent Virtual Assistant for Email, you can edit several rules for the channel. Performing this task allows you to add custom logic to the email triage process that is used for the Pega Virtual Assistant for Email.
For example, before the triage stage of an interaction case takes place, you can add an extension point that counts the number of interaction cases for analytics purposes. You can also add an extension point after the triage stage to display an advertisement about related services that might be useful to the user.
You must purchase a separate license before using Pega Intelligent Virtual Assistant for Email in your application.
You can edit the following rules to add custom logic to the Email channel.
Rule type |
Rule name |
Usage |
Activity |
pyParseReplyMail |
A |
Activity |
pyTransferTriageAssignment |
A |
Flow |
pyPreTriage |
A |
Flow |
pyPostTriage |
A |
Flow |
pyTransferAssignment |
A |
Section |
Work-pyRelatedWork |
A section that you can include to show related cases for a specific case. |
Notification |
pyInvolved_PulseDiscussion |
A |
You can also use the following read-only rules directly in the Email channel.
Rule type |
Rule name |
Usage |
Data page |
D_pxGetInteractionCaseDetails |
A |
Data page |
D_pxGetRelatedInteractionCase |
A data page that lists the ID and isKey values of the related interaction cases. This data page is useful while configuring the activity feed if the feed of related interaction cases needs to also be shown. The D_pxPosts data page can be used as the source feed and context parameter should be populated with insKey valuesof interaction case provided by D_pxGetRelatedInteractionCase. |
Flow |
pxMapEntitiesToCase |
A local action that is used in any case created by using email triaging. This flow helps with quickly mapping entities that are extracted during the email triage process to the actual case properties. This local action is only visible if the when rule work-pxCaseHasRelatedInteractionCase is true, for example, the case is created by the email triaging process. When triaging interaction cases, a user can create business cases. During triaging, entities are extracted from user input and saved in a work page. This flow action is rendered on that page and has access to all the entities extracted during the triage process. |