NOTICE: Breaking Change to "Email - POP3/SMTP/IMAP" VBO.

ewilson — Thu, 23 Apr 2026 16:28:35 GMT

A new version of the Email - POP3/SMTP/IMAP VBO (v10.5.0) has been released which includes a breaking change.

During validation testing, with the upcoming release of WorkHQ, it was determined the name of the VBO would need to be revised as the forward slash characters (/) included in the current name are not permitted in WorkHQ. If you attempt to import the VBO, as is, you will receive a failure.

The VBO has been renamed to Email - POP3 SMTP IMAP. The forward slashes have been replaced by white space. Only the VBO name was changed. The object ID remains the same.

This means any processes you migrate to WorkHQ, that use this VBO, will throw errors until they are revised to reference the new VBO name.

There are a couple options for updating existing processes to reflect the new VBO name:

1) Manual Update - Manually update any existing processes to reflect the new VBO name. If you have only one or two processes that only make a small number of action calls to the VBO, this is probably the easiest approach. Simply open the impacted process in Process Studio. When you do, you will receive a pop-up telling you changes to the process can't be saved because a referenced VBO is missing. This is due to the new VBO overwriting the existing VBO.

Once opened, go to each object stage where the Email VBO is referenced and change the name to Email - POP3 SMTP IMAP. You'll be able to select it from the drop down. The specific action name will remain the same, but you may find that the property values have been reset to empty. That means you will need to reset those properties using the variables you have defined in your process.

2) Find-and-Replace, File Based - You can export impacted process either as individual .bpprocess files or you can combine them into a single .bprelease file. You can then open the file(s) in a text editor, such as Notepad, and perform a global search and replace of Email - POP3/SMTP/IMAP for Email - POP3 SMTP IMAP. Alternatively, if you are using an AI tool like Claude Code, you could also use it to make the change.

Once that is complete, simply import the updated file(s) back into Blue Prism overwriting the existing processes. NOTE: Make sure to keep a backup copy of the file(s) before making any changes.

3) Find-and-Replace, SQL Based - This is the more complex and potentially risky solution. Before attempting this approach, you must ensure you have a current backup of your Blue Prism database.

Blue Prism process and object definitions are stored as XML in the database table dbo.BPAProcess. Depending on your version of Blue Prism, there are two columns that could hold the process definitions. They are processxml and compressedxml.

The compressedxml column holds, as the name implies, a compressed version of the actual raw XML data contained in the processxml column. When Blue Prism loads a process into memory, it will check for the presence of data in the compressedxml column. If the column value is non-null, Blue Prism will use the value of that column as the representation of the process. If that column does not exist (older version of Blue Prism) or the value of the column if null, Blue Prism will use the value of the processxml column. Furthermore, when you edit a process in Process Studio and save your updates, Blue Prism will write the revised XML to the processxml column and generate a new value for the compressedxml column.

With the above in mind, the following SQL queries are examples of how you could update impacted processes directly in the database.

List Impacted Processes

SELECT [processid], [ProcessType], [name], [compressedxml], [processxml] FROM [dbo].[BPAProcess] WHERE [ProcessType] = 'P' AND [processxml] LIKE '%Email - POP3/SMTP%'

Clear 'compressedxml' Column if Needed

UPDATE [dbo].[BPAProcess] SET [compressedxml] = NULL WHERE [ProcessType] = 'P' AND [processxml] LIKE '%Email - POP3/SMTP%'

Update 'processxml' Column for Impacted Processes

' Update the processxml column for any process that references the VBO. UPDATE [dbo].[BPAProcess] SET [processxml] = REPLACE([processxml], 'Email - POP3/SMTP/IMAP', 'Email - POP3 SMTP IMAP') WHERE [ProcessType] = 'P' AND [processxml] LIKE '%Email - POP3/SMTP/IMAP%'

Let us know if you have any questions.

Cheers,
Eric

Re: NOTICE: Breaking Change to "Email - POP3/SMTP/IMAP" VBO.

ewilson — Thu, 23 Apr 2026 17:54:20 GMT

Forgot to include the link to latest VBO (v10.5.0). It can be found here: https://digitalexchange.blueprism.com/cardDetails?id=115178

Cheers,
Eric

topic NOTICE: Breaking Change to "Email - POP3/SMTP/IMAP" VBO. in Digital Exchange

NOTICE: Breaking Change to "Email - POP3/SMTP/IMAP" VBO.

Re: NOTICE: Breaking Change to "Email - POP3/SMTP/IMAP" VBO.