Best Practice to follow while adding code to the out of box script include.

[divyasurada]

Hi,

When security incident is created through ITSM incident through a UI action "Create Security Incident", I want to copy some more fields from ITSM incident to the Security incident.

For this, can I directly add the code to the out of box script include or do I have to create a copy of the script include and then add my code to "CreateFromIncident" function?

Please help me with the best practice that I need to follow here.

Thanks,

Divya

[Omkar Mone · Accepted solution]

Hi Divya,

I donot have any exact documentation but let me tell you, in one of my projects i had to work on change module and change the flow of flow formatter by adding an extra stage as the customer wanted, there i had to make changes in the OTB script include that handles this. I dont think your case would have any affect during the upgrade. But if upgrade haunts you to override the OOTB SI then i would suggest you to create a new once and call it.

Hope this helps.

Omkar Mone

[venkatiyer1]

You can create a copy of the UI action and Script include and prefix it with Custom. make your changes in the custom and use it going forward. Turn off the Out of the box ones and ensure replace with upgrade is true on the sys_update_xml of the original record so that any future changes is captured in the original one for easy comparison. 

[khadija3]

you can use extention points to extend the OOB script include

https://docs.servicenow.com/bundle/newyork-application-development/page/build/applications/concept/e...

https://developer.servicenow.com/blog.do?p=/post/walk-up-experience/

[venkatiyer1]

Is this more of a NY release feature?

[venkatiyer1]

That was helpful to know