Error "Invalid attempt. Encrypted data could not be saved" shows up with Workflow Scratchpad Encryption plugin after security migration in Vancouver upgrade - Known Error

Error "Invalid attempt. Encrypted data could not be saved" shows up with Workflow Scratchpad Encryption plugin after security migration in Vancouver upgrade Description Workflow Scratchpad Encryption plugin does not work properly after migration in Vancouver upgrade

Steps to Reproduce

In Rome, install plugin 'com.snc.encrypted.scratchpad'. Create a workflow and update scratchpad in the workflow. Create a record and trigger the above workflow. Make sure encryption context is created. Upgrade the instance to Tokyo. Wait until the upgrade is completed. No sys_kmf_crypto_module for the plugin at this moment. Upgrade the instance to Vancouver. Wait until the upgrade is completed. sys_kmf_crypto_module is created after migration. Create a record and trigger the workflow.

Expected Behaviour: The workflow started and worked properly without error. Actual Behaviour: The workflow started with error "Unique Key violation detected by database" after the record was created. The error "Invalid attempt. Encrypted data could not be saved" would show up in the form when the record triggers a workflow. Workaround Set active to false in the following encrypted Field Configurations records and delete them: https:// /sys_platform_encryption_configuration_list.do?sysparm_query=tableSTARTSWITHwf_&sysparm_view=module

Unzip the attached PRB1725402_workaround_configs.zip and import all the xml files. Make sure the following records are imported successfully: sys_kmf_crypto_caller_policy_2febf925c33230109b53cde97640ddec.xml sys_kmf_crypto_module_192a79e1c33230109b53cde97640dd80.xml sys_kmf_module_crypto_spec_c21b7525c33230109b53cde97640dd61.xml sys_platform_encryption_configuration_ab39e7b2c33230109b53cde97640dd2c.xml sys_platform_encryption_configuration_db0927b2c33230109b53cde97640ddb1.xml sys_platform_encryption_configuration_e2d50ae9c33230109b53cde97640dda3.xml sys_user_role_68ea7125c33230109b53cde97640dd70.xml

Rename the encryption context 'Instance Encrypted Workflow Scratchpad'. E.g. add a 'Z' before the name: https:// /sys_encryption_context_list.do?sysparm_query=name%3DInstance%20Encrypted%20Workflow%20Scratchpad&sysparm_view=

4. Now trigger any workflow and the errors should be gone.

Note: For the workflow contexts with Waiting state which started/updated after security migration, and before applying the workaround, the existing workflow context will no longer work.