What are the guidelines for modifying OOB scripts?

[nerz]

My current understanding is that if you modify an out of box script, like a task Business Rule, the next system upgrades that touch those business rules will skip them because it detects user modifications to it.

If you duplicate the script and set the original to not active, that still shows a user being the one that last modified the script so will the upgrade still skip it? Does the upgrade actually check the code of the script to see if it matches the upgrades script? Also, what happens if you accidentally modify an OOB script? Is it ok to revert to a previous version and then the upgrade will still upgrade the script?

[Bharat23]

Comment you script. As such you will not face issues with upgrades as difference between the custom and OOB scripts are highlighted and it will be upto you to sync them or revert to OOB so that next upgrade will not skip it. So upgrade process skipping it is not really a problem.

[Goran WitchDoc]

I wrote a post about it what happens with modified OOB and upgrades.

You can read more about it here: Looking into the related list "Versions" and table "Update versions" after an upgrade

//Göran

[Brian Dailey1]

Hi Lee,

My suggestion if you need to customize an OOB script/BR/ACL/etc. is to first inactivate the OOB script/object and save it, and then use the "Insert and Stay" action to create a copy of it that you can customize and leave active in it's place.

That way, you will receive updated versions of the OOB object if they are pushed out by maintenance, but your script will be the active one.   That may be best-practice, I don't know for sure, it's how I handle it.

-Brian

[nerz]

Hi Brian,

So setting the script to Inactive doesn't interrupt the update process on it?