August 2017
Intermediate to advanced
1330 pages
56h 17m
English
The way that a UI Policy deals with fields that aren't on the form depends on the UI version. In UI11 and below (Eureka and earlier), any condition that uses a field not in the form will evaluate to false. For UI15 and above, the field value will be copied from the database to the client, and the condition will work as expected.
A common way to make it work the same in all versions is to place the required fields in the form and then have a UI Policy that always hides them. However, this compounds the problem: there is now an extra field that needs to be rendered and an extra UI Policy-all to hide some fields that should not show up! Avoid this whenever possible.
Read now
Unlock full access