Is anyone adding in the ability to turn features o...
# suitescript
c
Is anyone adding in the ability to turn features on/off within their suiteapps? For example, you have to pay $X to get an advanced feature and once paid, can be enabled or even disabled. Just getting some ideas on how people are approaching this.
s
We used to have a custom 'licensing' model for this years ago. Solutions would 'call home' to check licensing before doing the heavy lifting.
💯 1
I don't think it was particularly secure against nefarious users trying to steal.
having the important pieces locked was probably sufficient to deter most.
a
#subscribe
c
I've done the phone home thing in the past but not sure if its frowned upon these days. Would have to setup a restlet for it and just have the app call out as the first thing and bail if no license found.
👀 1
Did you do a check every time functionality was going to be accessed or did you do a time based where it has to phone home every X days to make sure you're still valid?
that call would def add some decent overhead if every operation.
e
I do this. The suitelet calls home and adds additional features based on the license by including additional js files
The license is cached for 24 hours, unless there is a specific param added to the suitelet url to force reload of the license
s
I don't remember how configurable our solution was, but it would be nice to be able to tweak that phone-home setting depending on what the application actually does.
e.g. if it's a process that only runs once a month, no need to check the license every day.
r
360SB has some pretty cool code obfuscation going on. Unrelated? Idk, I don't do SuiteApps
c
yeah I wrote that a long time ago unless they re-did it
s
very little SuiteScript code i've seen is anything I'd care to copy 🙂
😂 3