New Glide List type field not becoming visible on Playbook Lane

[Vinay Noel]

I have created a new field on playbook tasks table and this field is added to the form default view and playbook view as well of the playbook task. Also, I have added the field into the UI layout of Form fields section of the playbook activity (User form activity).

But this field is not coming up on the playbook lane.

It is only coming on the playbook task form view in native and also in workspace.

Can anyone help me to identify why this field is not coming up on the Playbook lane(Activity card of the User form activity). Is some extra configuration missed somewhere?

Thanks in advance

#playbook #playbookactivity 

[Vikram Reddy]

Hi @Vinay Noel,

Nine times out of ten with this one it's the field type, not something missing in your setup. A Glide List field (same family as Watch list, internal type glide_list) is one of the field types that just doesn't reliably render through the User form activity's Form fields configuration on the activity card, even though it displays fine on the actual form in both native and workspace. The activity card uses a lighter rendering layer than the real form, and list controls like slushbuckets don't have a clean mapping into that layer, so the field gets silently dropped instead of throwing an error.

Before assuming that though, run through these on the activity config itself:

• Check whether you're listing the field under Form fields or pointing to a Form View, if the view's title and its internal name don't match exactly (extra spaces, different casing), the card ignores it, that's a known trip up
• Confirm the field's technical name is exact, not a dot walked or inherited name
• If this is going through a UI Layout rather than the plain User Form activity, verify the field is actually added to that record's UI Layout and that the layout includes the Update playbook action, otherwise fields stay read only or invisible regardless
• Swap the Glide List field out temporarily for a plain string or reference field on the same activity to isolate whether it's the field type or the config

If that swap test shows the plain field renders fine and only the Glide List one won't, you've confirmed it's a rendering limitation on the card rather than anything you missed. The practical workaround people use in that case is a read only display field, populated via a business rule or UI policy that mirrors the list value as a string, since the activity card just isn't built to run list type controls the way the form is.

Thank you,
Vikram Karety
Octigo Solutions INC