How to add a button to every record on list layout ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-25-2019 04:01 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-25-2019 04:06 AM
Hi,
So you want 10 buttons for 10 records on list layout. That would be difficult to achieve.
But what you can have is list ui action and would be shown when you right click on that record
Mark Correct if this solves your issue and also mark Helpful if you find my response worthy based on the impact.
Thanks
Ankur
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-25-2019 04:23 AM
Hi Ankur
I have attached a screenshot displaying a list layout with a button on every record. I think we can also achieve if someone has achieved it but i'm trying to figure out how.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-25-2019 04:28 AM
Hi,
So what you want is to show a button? what should happen when that is clicked?
Mark Correct if this solves your issue and also mark Helpful if you find my response worthy based on the impact.
Thanks
Ankur
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-27-2019 04:46 AM
There was a similar question asked here:
https://community.servicenow.com/community?id=community_question&sys_id=fa5607e1db1cdbc01dcaf3231f9619ca
The key is that there is a field type called UI List Action that is not visible by default. And, as an admin, I was unable to make it visible. That required the maint role. I tried adding the maint role to the admin role in our instance, and was unable to do so... It seems like the maint role highly locked down and not something that should be given to individual users. As a result, I'm not sure what you are trying to do would be supported --or at least is not a recommended practice -- based on the security set around locking down this functionality that clearly exists in some form.