We are looking at ways for one of our robots to handle encrypted e-mails using either the Outlook connector or a C# script, and wondered if anyone has experience with this? The volume of encrypted e-mails we’re receiving has been increasing, so this is becoming more and more of a requirement as security naturally tightens.
Currently, the automation will throw an exception when trying to interact with an encrypted e-mail in any way. We have not yet found a way to move the e-mail to another folder. It remains in place, so any attempts to retry the process keep hitting the same issue. If we could just move the e-mail, rather than create a Try-Catch to safely ignore the exception and continue, we can at least provide a better solution to the end users. Even better if there’s a way to actually read the e-mail (at least subject line) and save it as an *.msg file, as well as move it around.
Is there something available OOTB that I’ve missed maybe, or any ideas on how we could achieve this? Thanks
can you try this to resolve the exceptions when handling encrypted emails, you should implement a C# script component that utilizes the Microsoft Outlook Object Model to interact with the MailItem directly. This script can successfully access metadata like the Subject and execute the Move method to transfer the email to a designated subfolder, even when the encrypted body content is inaccessible. You must ensure that the robot’s execution machine has the necessary S/MIME certificates installed so the Windows session can recognize and handle the encrypted items correctly. By programmatically moving these emails, you prevent the automation from failing repeatedly and allow for organized manual processing by human users. This specific approach bypasses the limitations of the standard Pega Outlook connector and provides a robust way to manage secure communications without crashing the robot. Let me know if this won’t work, thanks
Thank you for replying. Unfortunately, this won’t quite fit our scenario/use case, and there are times when things slip through the net. I’m hoping to find some way to at least handle the e-mail - if not as a ‘_mailitem’ object, then as a generic ‘object’ somehow