Updated by system@snc: what to do on upgrade?

[Sebastiaan de V]

I'm reviewing the skipped updates from an upgrade from Geneva to Istanbul. The customisations performed   by developers are clear, they need to be reviewed and either kept, reverted or merged. But I also have some customisations that are done by a user called system@snc. Which is not doen by one of the developers, nor does the user (still) exist in the system as   User [sys_user].

The customisations are also done on "system objects" (i.e. read-ony protection policy and/or not supposed to be modified).

What do I do with these updates on an upgrade: revert or keep?

[Chris M3]

You will typically see that when a SN Support personnel have updated a record, typically as a fix for an incident.   I would treat it as any other customization, review the differences and make a determination.

[Sebastiaan de V]

Thanks Chris, I get that for customisations on typical objects like script includes, business rules and client scripts. But what about objects we can't updated (e.g. with a read-only protection policy)?

[Alexiy]

Hi Sebastiaan! 

Have you found the answer for your question? 

[Sebastiaan de V]

Unfortunately not.