GenericAgent jobs don't Run after Saved

[peters]

Hi,

in 3.3.9, after editing custom Generic Agent job and pressing "Save", the job doesn't run, throw any error, nor match any ticket. Job is configured to match 1 ticket based on TicketNR (it's not running scheduled or based on events).

If the ticket is run from the list of jobs via the "Run this task", then it's executed and matches the filtered ticket.


Following error is found in apache error_log, right after opening job editing page (Subaction=Update). Same error is generated even if adding new job, or editing any created job.

Code: Select all

[Mon Sep 29 13:02:16 2014] -e: Version string '-1, set by base.pm' contains invalid data; ignoring: '-1, set by base.pm' at /opt/otrs//Kernel/System/Log.pm line 203.
ERROR: OTRS-CGI-10 Perl: 5.10.1 OS: linux Time: Mon Sep 29 13:02:16 2014

 Message: Need Data!

 RemoteAddress: 192.168.10.14
 RequestURI: /otrs/index.pl?Action=AdminGenericAgent;Subaction=Update;Profile=_Change1_Title

 Traceback (1066):
   Module: Kernel::Output::HTML::Layout::BuildSelection (OTRS 3.3.9) Line: 2267
   Module: Kernel::System::DynamicField::Driver::BaseSelect::SearchFieldRender (OTRS 3.3.9) Line: 514
   Module: Kernel::System::DynamicField::Backend::SearchFieldRender (OTRS 3.3.9) Line: 1231
   Module: Kernel::Modules::AdminGenericAgent::_MaskUpdate (OTRS 3.3.9) Line: 907
   Module: Kernel::Modules::AdminGenericAgent::Run (OTRS 3.3.9) Line: 320
   Module: Kernel::System::Web::InterfaceAgent::Run (OTRS 3.3.9) Line: 871
   Module: ModPerl::ROOT::ModPerl::Registry::opt_otrs_bin_cgi_2dbin_index_2epl::handler (unknown version) Line: 41
   Module: (eval) (v1.99) Line: 204
   Module: ModPerl::RegistryCooker::run (v1.99) Line: 204
   Module: ModPerl::RegistryCooker::default_handler (v1.99) Line: 170
   Module: ModPerl::Registry::handler (v1.99) Line: 31

Can I somehow increase logging to see what is causing the error message?

Thanks,
Peter

[reneeb]

This is caused by a dynamic field. Please check your dynamic fields of type "Select" or "Multiselect" and check if every dynamic field has key/value pairs configured...

[peters]

For the custom dynamic fields, all of them are of type "Dropdown". I checked them, and all have key-value pair. Some of them have the "default value" set to "-". Can this be the cause?

[peters]

The default "ITSMDecisionResult" didn't have any key-value pairs defined. After adding some, the error message "Message: Need Data!" vanished.

Anyway, after the job is saved, the window Run with matched tickets is not opened. Is this new behavior in 3.3?