When we started working on Documate, protecting our application was one of our main concerns.
This session would’ve saved us some time back then.
Ty Roach not only explains it in his nullEDGE session, but he also demos it in a very concise way.
Key takeaways
Protection levels
There are three protection levels for your files:
- None: visible, editable, exportable.
- Read-only: visible and exportable, but locked for editing.
- Protected: completely hidden. Your code stays secret.
App Repository vs Update sets
Protection Policies only work when you install from the App Repository or Store. No protection if you deploy via Update sets.
When to use them
- Protected mode for core logic you don’t want anybody to see.
- Read-only for API libraries, so that users can learn how to use them without breaking anything.
You need to be a Build Partner to publish to the Store, but any ServiceNow customer can use their App Repository and benefit from these protections.
References
- Ty Roach: LinkedIn | ChecklistPRO
- ServiceNow documentation: Protecting Application Files
- nullEDGE Website
- nullEDGE YouTube channel
- My LinkedIn posts #nullEDGEAdvent (any feedback is welcomed!)
- Intro to my nullEDGE advent calendar adventure
