- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-10-2015 08:26 AM
So I'm working on what I thought might be a simple feature: Require a user to add Change Tasks before a Change Request can be submitted for approval (via a Request For Approval UI Action).
I have Change Tasks as an embedded list on my Change Request form and my users love it. So I'm wondering if I could key the UI Action visibility or at least have a client script check onSubmit (of the change request) if data has been populated in that embedded related list. Everything I see on the GlideList2 wiki page seems to be altering the properties of the embedded related list, and not actually interacting with its data.
Am I barking up the wrong tree here?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-10-2015 11:39 AM
Ok, with the insights Travis Toulson and Cory Seering gave me, I cracked the case.
function onSubmit() {
var list = GlideList2.getByName('change_request.change_task.change_request'),
rows = list.table.getElementsBySelector('tr.list_row'),
sys_id;
// - 1 to exclude the insert row which is the last in the list of rows retrieved above
if (rows.length - 1 == 0){
alert("No Change Tasks");
} else {
alert(rows.length + " up in here.");
}
}
Now all that's left to do is integrate this into my Request Approval button and I'm off to the races. Which leaves one more order of business for Travis and Chris:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-10-2015 11:54 AM
Glad you got it working!