The CreatorCon Call for Content is officially open! Get started here.

Visual glitch when applying start_locked=false to table List field

TheInquisitor13
Kilo Sage

When applying the start_locked=false attribute to the List field in my custom table, it is still displaying the fully locked icon above the unlocked slushbucket. How can I correct this?

find_real_file.png

1 ACCEPTED SOLUTION

I found that the glitch occurs when applying the List field to a UI Policy alongside the attribute value. 

 

I applied an onLoad/onChange client script (see below link for reference on code needed) and I  removed the attribute value, start_locked=false, from the field. It works fine now.

 

https://servicenowguru.com/scripting/client-scripts-scripting/lock-unlock-glidelist-url-fields-client-scripts/

View solution in original post

3 REPLIES 3

Murthy Ch
Giga Sage

@TheInquisitor13 

Not really sure, but it works as expected in my PDI.

Thanks,
Murthy

TheInquisitor13
Kilo Sage

No worries, I had to delete the field and re-create it to correct the issue. Was just curious if this was something that has been seen before and if there were any alternative ways of correcting. 

I found that the glitch occurs when applying the List field to a UI Policy alongside the attribute value. 

 

I applied an onLoad/onChange client script (see below link for reference on code needed) and I  removed the attribute value, start_locked=false, from the field. It works fine now.

 

https://servicenowguru.com/scripting/client-scripts-scripting/lock-unlock-glidelist-url-fields-client-scripts/