
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-06-2019 07:54 AM
Hello,
We had to do a tweak in the OOTB Script Include. To do this we've duplicated(by keeping the same name) the OOTB script include and modified it to satisfy our need then deactivated the OOTB Script Include. I've few question around duplicating the OOTB Script Include and possible issues.
1. Is it safe to duplicate it? We did this to avoid the skip during an upgrade.
2. What happens when OOTB SI gets an update? Like a SI new call being added somewhere in the system for OOTB SI How can I overcome this?
Thanks for your time.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-06-2019 10:33 AM
Hi,
1. Is it safe to duplicate it? We did this to avoid the skip during an upgrade.
Yes it is safe if you make sure you do the following:
- Keep OOTB settings, conditions, etc.
- Whenever you need to extend OOTB settings, duplicate your script include and duplicate the entry where you would like to use such ACLs, etc. Whenever an upgrade happens, your functionality will not be affected.
- I advice you to keep OOTB settings enabled and extend the functionality on a new script keeping the original settings.
PS. I would suggest having a prefix on the ScriptIncludeName like RickScriptIncludeName.
2. What happens when OOTB SI gets an update? Like a SI new call being added somewhere in the system for OOTB SI How can I overcome this?
Nothing if you follow previous bullets. Your functionality could be affected during an upgrade but applying this quite of practices reduces (80%) chances of being affected.
Thank you,
Raf

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-06-2019 08:00 AM
Hello Rick,
As of I know you can create another script include and extend the OOB script include here.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-06-2019 08:25 AM
Thanks for the reply Bhagya.Can you please post if have any reference or example for that.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-06-2019 08:03 AM
1. Is it safe to duplicate it? We did this to avoid the skip during an upgrade.
--> As best practice, you should not customize OOB objects to avoid any issues in future upgrades.
2. What happens when OOTB SI gets an update? Like a SI new call being added somewhere in the system for OOTB SI How can I overcome this?
--> OOTB SI will be updated to latest release version if this isn't customized.In your case, since you deactivated OOB SI, this OOB SI will be skipped during future upgrade.
Regards,
Sachin

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-06-2019 08:11 AM
Thanks for the reply Sachin. I just wanted to make few things clear. We are not customizing the OOTB SI, we will just deactivate, duplicate it by keeping Replace on Upgrade true. My main concern is what will happen if the OOTB gets some new code change since it is deactivated.