Enabling Column Level Encryption (CLE) - Different sys_ids on instances following activation

[spike]

Can anyone help me with the enabling the Column Level Encryption plugin?

I've enabled the plugin on our Dev instance and configured it. Everything appears to be OK.

We've then enabled it in UAT and gone to move the update set with the config changes and the update set has failed. The table "sys_platform_encryption_configuration" is flagged as not existing. This is added as part of the CLE plugin but in UAT has a different sys_id.

Is this something anyone has come across before? How do we enable CLE and move the configuration from one instance to another?

Many thanks!

[SK Chand Basha]

Hi @spike 

If you capture CLE in the update set you will get cross-scope errors it's hard to move. 

Directly do the implementation in production on some fields and check it.

Refer this video :- https://youtu.be/4b9S9KwzL2g?si=rQYauo31yTP_q-eH

Mark this Helpful !!. If this Helps you to understand . This will help both the community and me.

[spike]

Thanks for the reply. That video doesn't really answer the question. I've set it up already and I know how to do that. My point is about moving stuff via update sets. 

You've said that's not possible are you able to refer me to any ServiceNow documentation about that?

Thanks.

[SK Chand Basha]

Hi @spike  we have also Implement CLE in Customer instances first tried with captured in Update sets after moved to test getting Cross errors. So we directly implement on Prod instance. 

[spike]

This is the conclusion I'm coming to. Not heard back from ServiceNow confirming it yet though.