Field Visibility

My previous post was all about how dynamic layouts can be used to tailor the user experience of Engagement Cloud.  There are always business requirements to present information differently in certain cases or to certain user roles. Dynamic layouts are a very flexible system to build such consistent and intuitive layouts.  But when dealing with very small specific variations in requirements, this can sometimes lead to a lot of dynamic layouts.  Sometimes too many, with minor differences, to maintain easily.  This is why in Release 18C, an additional capability to define field visibility on layouts was added.

Field Visibility

Fields themselves have their own definition specifying how they should look and behave on the layouts they are added to.  The exact attributes for each of the fields might differ depending on the field type.  But there are a few specifications they all have in common.  The constraints as you can see them in the example below show whether fields should be required and updatable on any of the dynamic layouts they are placed on.

So visibility of a field used to be driven by the fact whether or not fields are placed on dynamic layouts or not …. until now.

As of release 18C, once a field is placed on a dynamic layout, extra visibility specifications can be added.   The required and updatable specifications as defined on the field level can be adapted for each layout also.  These attributes can be set to 1 of 3 different values:

• Yes: Make a field on a specific layout required, updatable or hidden
• No: Make a field on a specific layout optional, read-only or visible
• Expression: Make a field on a specific layout only under specific conditions required, updatable or hidden

This is a new capability I have been really looking forward to!  I hope you are as excited about this as I am !

Have fun !