View .EML file in pxFEED
Request for a product enhancement to .pxFeed to handle .eml files. More immedietely an existing solutions or quick workaround to the issue of viewing .eml files in the pxFEED gadget:
Would like to be able to:
- In addition to the existing functionality of having a link in the feed(see below) with which you open the email in .eml format, provide an option to show the content of the email directly inside the feed.
- Alternatively, provide an option to open the email in some HTML format that doesn’t necessitate an email client.
@DamianosD please comment further if I've missed something above.
***Moderator Edit-Vidyaranjan: Updated SR details***
Pegasystems Inc.
US
Hi @willt2,
I have submitted this enhancement on your behalf and updated your post with the FDBK-ID. You can view this in our internal enhancement system.
Thank you!
Pegasystems Inc.
US
Thank you Marissa, we are also interested to hear from any others who may have dealt with this situation and what they used as a workaround solution.
Pegasystems Inc.
US
Sounds great!
Pegasystems Inc.
IN
Based on the information given, it looks like the above use case is related to email interaction case.
Is it required to show the text styling from email content as well in the pxFeed gadget? If it is not required, then we can simply change the service email rule to use Inline-Prefer text option (available as part of request tab in service email rule). This will show the content directly as part of feed gadget. Attaching the snapshots before and after the change.
Cisco Systems
NL
HI Pavan, If I understand this correctly then updating the rule will show the email content plain text, ie it will loose the formatting of the original message. If that is the case I think that's an acceptable solution, thank you.
Another issue we have with email interactions is that when a case gets created from the email interaction through triage (attached screen 1) then the associated interaction does not (consistently) display the moment we open case (screen 2). Do you have any ideas why we might be seeing this behavior?
thank you
Tony.
Pegasystems Inc.
IN
Hi Tony,
We are not able to see this issue OOTB, it might be happening at framework level. Need more details to find the root cause. Better to raise a Service request (SR) so that some engineer from pega can closely work with you and debug the issue.
Regards, Pavan
Cisco Systems
NL
Thanks Pavan, we will do that.