You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I'm aware, REST.pm would require some special handling of the parameters. There's no particular standard here, but Foo[Bar] is quite a common one and would work relatively well(?)
Just needs something that's able to convert DynamicField[Name]=flibble&DynamicField[Empty]=1&DynamicField[Like]=mysearchcontent into an actual DynamicField => {Name => "flibble", "Empty" => 1} hashref.
I imagine the SOAP layer would also need something, but I haven't looked very closely at that
I'm not entirely certain about this, so by all means correct me if I'm wrong (and turn this into a documentation improvement issue!)
The text was updated successfully, but these errors were encountered:
The REST API has no way of handling a "hash" structure of URL parameters
as far as I can tell, this is required for running TicketSearch on DynamicFields due to the operator structure it requires
otobo/Kernel/GenericInterface/Operation/Ticket/TicketSearch.pm
Lines 147 to 160 in 89dd1c7
(incidentally I think the comment here is "out of date" and uses the "old style" of keys?)
otobo/Kernel/GenericInterface/Operation/Ticket/TicketSearch.pm
Lines 541 to 562 in 89dd1c7
otobo/Kernel/GenericInterface/Transport/HTTP/REST.pm
Lines 162 to 172 in 89dd1c7
As far as I'm aware, REST.pm would require some special handling of the parameters. There's no particular standard here, but
Foo[Bar]
is quite a common one and would work relatively well(?)Just needs something that's able to convert
DynamicField[Name]=flibble&DynamicField[Empty]=1&DynamicField[Like]=mysearchcontent
into an actualDynamicField => {Name => "flibble", "Empty" => 1}
hashref.I imagine the SOAP layer would also need something, but I haven't looked very closely at that
I'm not entirely certain about this, so by all means correct me if I'm wrong (and turn this into a documentation improvement issue!)
The text was updated successfully, but these errors were encountered: