...
But that would mean you need to give access to your internal system to externals and built an additional permission layer – that focuses on externals. That is for once high maintenance and a huge risk factor.
...
| Code Block |
|---|
global-properties:
customFields:
CUSTNR: YourDefaultValue |
Setting the value to YourDefaultValue “YourDefaultValue” is a good way to make sure, the custom field is always applied – even if the original value is empty. Since this is about security, we set a default value that we can expect will not yield any result. We could’ve also set SquareDinosaur“SquareDinosaur”, XXX “XXX” or NoCustomerNumberGiven“NoCustomerNumberGiven”.
Since this field support search terms do not use * as default – it will have the opposite effect.
...
Set the field CUSTNR to “000115”:
...
| Note |
|---|
Even though the custom field is already visible in the user settings, a restart of the backend is still necessary. |
After you saved the settings, the next time the user opens the section the view is already filtered:
...
And you’re done. ✌️ You just solved an issue nobody else could wrap their head around for years.
Synopsis
The Custom Fields are an extremely a powerful tool to build apps with the same structure, but at the same time deliver different content based on who is looking at it. Since the permission are always “content based” you can build them independently of your source application.
...