Variables sharing the same name as Encrypted Text field causes Encryption Context to be evaluated, returning message "Invalid attempt. Encrypted data could not be saved" - Known Error

Variables sharing the same name as Encrypted Text field causes Encryption Context to be evaluated, returning message "Invalid attempt. Encrypted data could not be saved" Description Build information: Build name: London Build date: 02-14-2019_1004 Build tag: glide-london-06-27-2018__patch6-02-06-2019

Issue Description: In a record producer, when creating variables that share the same as an Encrypted Text field types on the corresponding table, this causes the Encryption Context to be evaluated, resulting in the message "Error MessageInvalid attempt. Encrypted data could not be saved Info MessageRecord not found"

Even if the 'User encryption' option is flagged off, the encryption context is still called due to the same variable and field name

- This issue does not occur in Kingston.

Steps to Reproduce

- Activate 'Encryption Support' plugin

1. Navigate to System Security > Field Encryption > Encryption Contexts https:// .service-now.com/sys_encryption_context_list.do

2. Create a new Encryption Context with 'Type' set to "AES 128-bit"

3. Create a new field on the Incident form: Name = Encryption Text Field Database column name = u_encryption_text_field Type = Encrypted Text

5. Create a new Record Producer pointing to the Incident table 6. Create a new variable: Question = Encryption Text Field Name = u_encryption_text_field

7. Log in locally as "Joe Employee" into the instance 8. Open the newly created Record Producer and attempt to submit

Expected behavior - The Record Producer is submitted

Actual behavior - The Record Producer does not submit and displays the following message:

*Error Message Invalid attempt. Encrypted data could not be saved *Info Message Record not found

Workaround To receive notifications when more information is available, subscribe to this Known Error article by clicking the Subscribe button at the top right of the article. If you are able to upgrade, review the Fixed In field to determine whether any versions have a permanent fix.