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

Is it possible to modify the List Control of a Related List and apply that change to all extended tables of CMDB_CI?

Paul VanOver
Kilo Contributor

Hello all, I am brand new in the SNow community, so please be gentle.   We are on the Helsinki platform.

Here is the situation. We have numerous tables extended from cmdb_ci, such as cmdb_ci_windows_server, cmdb_ci_linux_server, etc. etc. I think this is pretty much common in any instance of SNow. All of these have multiple records in them.

If you open any of these items and view them, at the bottom of the form are the related lists. Every single table extending from cmdb_ci appears to have a related list, called Affected by Task. I have been asked to lock this down for all of these extended tables, as well as change the Label the user sees.

I have figured out that all of these related lists are in the sys_ui_related_list_entry table. I know one way to lock down these related lists is to configure them using the List Control options. I went into sys_ui_list_control expecting to find a list control for each of these and could not. Therefore I assume there is some default mechanism being used to control.

I know I can create an entry in sys_ui_list_control for every related last in every table extending from cmdb_ci and accomplish what I want, however, this just doesn't sound like the right approach.   It seems like I should be able to create one entry for cmdb_ci which applies to that table and all tables which extend it. This would also handle any new future items discovered by Discovery and added to the cmdb.

Does anyone know if this is possible? Thank you very much for your help!

Paul

Additional information (since I posted this)

I have figured out that I can duplicate the global New or Edit... ui actions and change the table to task_ci (affected tasks) and then set the condition to false, this prevents the New and Edit button from ever showing on that related list. that is one option, still sounds odd to me.

I also figured out there are Omit Edit Condition and Omit New Condition scripts available on List Control, but those weren't being displayed by default. This seems like a much better approach to me.

This still doesn't address the need to apply this change at the base table level. Ideally, I could create a script that says, "Hey, If I am a related list, if I am the task_ci affected task list, and my parent base table is cmdb_ci, then I want to globally change my Label to say "yada yada" and I want to remove the New and Edit button.

6 REPLIES 6

Thank you for trying to help, but that doesn't quite do it either. That might control the New and Edit on child tables of task_ci, but I am referring to the related lists which appear at the bottom of each of the child tables of cmdb_ci. I think Pradeep is correct in that I am going to have to go to each table and create an entry in the List Control table if I want to change that label.


Paul VanOver
Kilo Contributor

I think, after much research, and someone please tell me if you think I am wrong, here are my options:



To Remove the New and Edit button:


        Option 1) I will need to configure an ACL to remove them for task_ci.


        Option 2) I can modify the Global New and Edit buttons so they do not appear on this one related list.



To setup the columns which display, it appears I can go straight to task_ci.list and use List Layout to arrange them how I want and that does trickle down to the related list on each form.



To modify that label "Affected by Task" it appears I have no choice but to create a List Control for each related list, on a form by form basis. I suppose I could use a script and insert all these rows in a matter of seconds.