Quick/Bulk Edit in SOW

maciep
Tera Contributor

I've been tasked with disabling the ability to update a Config Item in the SOW based on the name of the CI. So if somebody in the SOW, opens their nav, heads down to the CMDB section and chooses a CI list, then they should not be able to modify any CIs with a matching name.

 

This includes being modified from the normal form, the quick edit form and the bulk edit form. We are currently on Xanadu but Zurich is right around the corner for us. I'm not sure if the approach would need to change between versions but some posts I've found seem to indicate that's the case.

 

I am able to configure the bulk Edit button using the declarative action. However, that's targeting the Global table and the configuration I need could only be set if it targeted a specific table like cmdb_ci. So I don't think I want to change the main Edit declarative action in that way.

 

And even if I could get that to work, the quick edit button is still there. And I haven't found a way to disable it on some records and not others. Plus, it is also a quick preview which may still be desired.

 

So I thought maybe I could disable the "Update" button the quick/bulk edit forms based on a CI Name. But I'm struggling to figure out thow that works. And I think it may work differently between versions. Some advice says the "workspace" is used there, but that doesn't seem to be the case from what I can tell.

 

I've been going in circles between looking at views, declarative actions, ui builder pages and page collections, but I can't seem to find how I'm supposed to accomplish that.

 

If anyone could point me in the right direction or have any tips to try to figure out, it would be appreciated. Thanks!

3 REPLIES 3

RaghavSh
Mega Patron

@maciep Do you want to disable bulk edit from kist view SOW? If yes look for your list in "sys_ux_list" table.

It has the options like disable list edit, you can enable that to disable list edit in workspaces.


Please mark the answer correct/helpful accordingly.


Raghav
MVP 2023
LinkedIn

maciep
Tera Contributor

Thanks, Raghav. I'll take a look at that table.

 

But we don't want to disable it completely. We only want it to be disabled when any of the selected records have a matching name attribute. So it's sort of a record-by-record approach we're hoping to take. I do know that is configurable for declarative actions, but I don't think it's that simple for the Edit one.

 

And we want that same logic applied to the quick edit and normal record views. So essentially, if a CI has matching name, then we don't want anyone to be able to update that CI in the SOW specifically.

TBH, I dont think this would be possible or that easy to implement. I will leave it for other members to comment if they have any ideas.


Please mark the answer correct/helpful accordingly.


Raghav
MVP 2023
LinkedIn