AgentITSMConfigItemBulk does not work with Dynamic Fields

[ybeckmann21]

When adding additional Dynamic Fields to the AgentITSMConfigItemBulk, the fields get displayed in the Bulk Action but they are not working. Changes made are not saved in the CI.
Selecting a Value in the Manufacturer Field also produces a network error.

Tested on ITSMConfigurationManagement 11.0.9

[stefanhaerter]

I investigated the problem and can confirm. So far, I identified several TODOs:

• Add FormID handling to Kernel::Modules::AgentITSMConfigItemBulk::new()
• Add sysconfig Loader::Module::AgentITSMConfigItemBulk###003-ITSMConfigItem, likely needs to contain the same CSS and JS as Loader::Module::AgentITSMConfigItemEdit###003-ITSMConfigItem
• Add subaction AJAXUpdate to Kernel::Modules::AgentITSMConfigItemBulk

The first two things are low hanging fruits, the third is not as trivial, I'd asume.

[k1ch3r]

I just changed these two lines in AgentITSMConfigItemBulk on my local dev system and it looks like a working fix to me:

# old (line 182)
        next DYNAMICFIELD unless $Self->{Config}->{ $DynamicFieldConfig->{Name} };
# new
        next DYNAMICFIELD unless $Self->{Config}->{DynamicField}->{ $DynamicFieldConfig->{Name} };

# old (line 538)
                    AJAXUpdatable      => 0,
# new
                    AJAXUpdate         => 0,

I can pull request my version with these changes if it helps.

[svenoe]

Hi Jonas,

thanks; I can imagine that some standard fields will work with this, but for more special ones, say reference fields, lenses, etc., definitely the "AJAXUpdate" will be necessary. At the same time things which usually come with this (i.e. ACLs) are not all too well defined when working on a bulk of objects, instead of one. Secondly compared to standard fields which are mandatory for the object (e.g. a queue in a ticket), we have a problem with leaving dynamic fields in bulk empty, because it could either mean "leave the current value", as it is in TicketBulk, or "empty the current value". Both things are not unsolvable (that is, we have to define the wanted functionality), but it should be a concious decisions; for TicketBulk those two points are likely the reason why DFs have never been in TicketBulk, also.

Currently this is on hold on our side.