Preserve data for private system properties?

[Leonard Ambos]

We're looking into using the "Private" option more liberally for system properties, which is intended for instance-specific properties and explicitly prevents the property from being accidentally moved to other instances via update sets.

https://docs.servicenow.com/bundle/tokyo-platform-administration/page/administer/reference-pages/tas...

However, it doesn't look like there's any OOTB protections against these properties from being pulled between instances in clonedowns. Some of them are covered by the "Core Instance Properties" data preserver, which covers a number of properties like glide.email.server, glide.email.smtp.active, glide.smtp.port,  glide.pop3.server, instance_id, instance_name, etc, but a number of private system properties do NOT appear to be covered, such as sn_atf.debug, mid.version, com.glide.plugin.activation_mode.override, etc.

So far we've set up Data Preserves for each private property we've created, but does it make sense to just create a Data Preserver for all system properties where private=true?

[Andy Homar]

Hey @Leonard Ambos  Did you end up trying this?  Makes sense to me and am surprised they aren't preserved OOB if their intention is to be instance-specific.

[Leonard Ambos]

Honestly, private sys_properties haven't come up as much as I worried they would. We jumped from 2 to 6 when I originally posted this, but haven't created any in the last year so we haven't bothered changing our Data Preservers to be more future-proof.