Posted: 24 Aug 2017 7:03 EDT Last activity: 16 Oct 2018 12:03 EDT
Email inbound property for identifying High importance mails and map to clipboard
In my current project we are using an email listener to initiate work. The case workers raised the requirement that when emails having importance flag set to high (exclamation mark in Outlook). Currently I have not found any property that would be available OOTB that tells me the importance. I looked up the class’ properties for Embed-Services-InboundEmailInfo.
Does anyone know a solution how to read the importance flag while the email listener picks up new emails and then map it to clipboard? Thanks!
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Out of the box I do not believe we capture that information. However, you should be able to configure your service email rule's Request tab to capture the header that represents importance and save it to a custom property. I believe one of these headers will be what you're looking for, but you will want to do some testing on your end to verify:
Hi NickLoving_GCS , Thanks for your quick response.
We tried out the solution given by creating property named EmailPriority in Embed-Services-InboundEmailInfo and mapping the same in Request header section to one of the three above mentioned headers. We sent a mail from Outlook with high importance and tested the same .But there was no value set for the newly created EmailPriority property in all 3 cases. Are we missing anything here ? Is there anything else we need to do apart from the things we have done. Please help.
Posted: 4 years ago
Posted: 30 Aug 2017 9:52 EDT
Nick Loving (NickLoving_GCS)
Senior Software Solutions Engineer
Not sure if this was resolved since I see no SR created. I suggest that you create a new post for your query. If you do, please make sure to provide all relevant details such as Pega version, details use case, screenshots if any and attempted solutions.