(Out of curiosity) For the NetSuite partners in th...
# suitescript
l
(Out of curiosity) For the NetSuite partners in this group - do you put a clause in the SOW about the “risks” of using third party libraries when you develop a solution for the customers?
c
I've never seen anything that explicitly calls out third party libraries. You can put whatever you want in a SOW. Does it help w/ the understanding of the work to be done?
l
Reason behind the question is because since these are third-party libraries, they’re out of control, for instance: if the library gets discontinued.
a
are you talking about a code library? Wouldn't you just use the current version and store it in their file cabinet? that way it can't be discontinued, its stored in their account and will keep working how its working today. if you using a hosted library I can see this being a risk, but, its one that's easily avoided. Don't use externally hosted libraries
💯 1
I've never seen such a clause in an SOW, but you can put whatever you like in them, I think stuff like this would just be covered by general disclaimer legalese that goes into all your SOWs, or MSA if you have one of those.
c
I also suggest the library locally
I try to stay way from anything that isn't standard netsuite. I use moment.js and that's it. Something like underscoreJS is pretty popular too but all of these are libraries you download and put in the file cabinet. If you're doing JQuery dark arts and stuff for people for custom views/code, you've already opened yourself up for some issues.
💯 4
l
Well-said @creece