Glide List - Control Starts Locked or UnLocked?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-25-2011 05:00 PM
I have some glide lists that I want to start out locked and some unlocked.
I tried what's in this forum:
anyway to force the URL Padlock to unlock then lock automatically?
However, this doesn't seem to work.
Any ideas?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-01-2011 06:05 AM
http://www.servicenowguru.com/scripting/client-scripts-scripting/lock-unlock-glidelist-url-fields-client-scripts/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-01-2011 01:40 PM
You're on a roll! Thanks!!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-06-2017 06:04 AM
There's a dictionary attribute for unlocking a glide list as default.
start_locked=false
(late to the party but this article is Google top result)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-27-2018 12:56 PM
Unfortunately this does not work for Variable Attributes from what I see. ServiceNow added the capability to turn a slushbucket into a a glide list using the glide_list attribute but they weren't consistent by allowing the expand feature. That almost makes the glide list unusable on record producers/catalog request forms because the user has to remember to unlock it which seems silly to me. There are ways around it using client scripts, but when you get that far down the rabbit hole it's not worth it anymore. Uggg.