How to modify the cmdb_ci filter on forms for some classes

[Fotios Kossyvas]

Hi to all,

for incidents, problems and problem tasks i can select any class of cmdb item in the field Configuration Item in their creation/edit form.

I would like to have it the same way for these classes too:

sc_req_item
sc_task
change_request
change_task

In the list of the Configuration Item field of these classes at the moment there are only these classes:

sc_req_item : nothing
sc_task : servers
change_request: servers
change_task: servers

Could anyone help me implement it?

Thank you in advance

Fotios

[rahulswami]

Hi @Fotios Kossyvas 

This is usually a dictionary override on the cmdb_ci field, not core platform behavior. All these tables (incident, problem, sc_req_item, sc_task, change_request, change_task) extend task, which owns cmdb_ci → cmdb_ci. Each extended table can carry its own override, which is why some are more restricted than others.

To fix:

1. Go to System Definition > Dictionary, filter Table = sc_req_item/sc_task/change_request/change_task and Column name = cmdb_ci.

2. Open each match and check:

• Reference field — should be cmdb_ci. If it's been changed to cmdb_ci_server, that's why only servers show.
• Reference qual — if Simple, remove any sys_class_name=... condition; if Advanced, edit/remove the class filter in the script.

3. Compare against incident's dictionary entry (usually no override) — if the others don't need one either, just delete the override so they inherit the unrestricted base behavior.

If sc_req_item still shows nothing after that, the "Configuration Item" field on that form may actually be a catalog variable on a specific catalog item, not the base task field — check the item's Variables list instead.

Also worth checking Client Scripts / Catalog Client Scripts on these tables for any g_form.addFilter logic on cmdb_ci — a script can restrict the picker even after the dictionary is clean.