Add export/import for credentials and work queue items

[StefanPappalard]

We are forced to use the migration strategy when upgrading Blue Prism because we need the following features.

• The original environment can remain operational during the upgrade (Fallback!)
• Advantage of a clean start (Performance!)
• NO Downtime is required to perform the upgrade (Stability!)

Follow link for more details: High-level upgrade strategies (blueprism.com)

 But there is some potential for optimization with the migration strategy.

• Please add a feature to Blue Prism Automate for exporting and importing credentials.
• The passwords should be encrypted for security reason.
• There need to be the same encryption key in the target environment.
• After the import another encryption key can be generated to re-encrypt all credentials and the old credential key could be deleted.
• Please add a feature to Blue Prism Automate for exporting and importing work queue items.
• When encryption is used the transport of affected information should be encrypted at export.
• The encryption key for the work queue need to be transferrable / reusable in the target system.
• After the transfer of the data the old encryption scheme should be replaceable by a new one.

The main benefits of these features are...

• Safe and secure transfer of credentials and work queue items on migration.
• More flexibility for switching between environments outside of migrations.
• Less effort for building and maintaining workarounds when trying to create an alternative transfer solution.

Thanks in advance 🙂

[AmyTsaousi]

Hi Stefan, 

Thanks for submitting your idea, the team really like it. I’ve updated the status to Under Consideration and you will see updates here as it progresses through the process.

Best Regards,

Amy