By Cezary Basta
UI Policy – what’s that?
Valid for build tag glide-utah-12-21-2022__patch0-01-18-2023.
As per the documentation:
UI policies dynamically change the behavior of information on a form and control custom process flows for tasks. (…)
Product documentation
You can also use client scripts to perform all of these actions, but for faster load times use UI policies when possible.
Creation
When you want to create a UI Policy, it’s important to remember 2 things – you create UI Policies for tables and these tables have to be the in current scope. So you can’t create cross-scope object.
First things to pick are a table (obviously) and a short description. There’s a 255 character limit on this field.
Second and really important thing to define well are the conditions. It’s a set of rules that have to be matched in order to execute the UI Policy. Make sure this set is unique, because you don’t want to have multiple policies at the same time. It is possible and maybe sometimes needed, but you need high control over your table, order of executions and other objects affecting it.
The rest of the form is really well defined on the product documentation page, so I want discuss it here.
Actions
Every UI Policy executes actions. Actions can be simple (set field attributes: RO, visibility, mandatory, clear field value) or scripted (run custom client side javascript).
The easiest use case is to simply select fields and their attributes.
Conclusion
And that’s the basics, nothing fancy as you can see. In the next article I will talk more about possible actions, including scripting.