Prevent error dialog on custom "new customer ticket" screen

[Monitor02]

Dear all,

I am trying to create a new Ticket link for customers, which fills out the subject and Body automatically.

https://???.de/otrs/customer.pl?Action=CustomerTicketMessage&Subaction=StoreNew&Subject=Test&Body=Test

However, I still want the user to enter a queue manually but because I am not setting a queue in the URL it is throwing an error that at least a queue must be selected.

I have found a solution to a similar problem when creating new phone tickets:
If you add ExpandCustomerName=1; to the URL string it no longer presents the error and lets the user add the CustomerUser themselves.
https://???.de/otrs/ index.pl?Action=AgentTicketPhone&Subaction=StoreNew&Dest=Internal&Subject=Test&ExpandCustomerName=1

I am also not sure which variable I can use for the queue in the "To" field.

Can someone help me with this problem?

Thanks for your time and regards

Thomas

[zzz]

Hello Thomas,

The dest field in the customer frontend is written in this format: 'QueueID||Queuename'.
For example: customer.pl?Action=CustomerTicketMessage&Subaction=StoreNew&Dest=3||Junk

Best regards
Emin

[Monitor02]

Hello Emin,

thanks for the answer, the variabl seems to be correct but
I get an other error message if I ad the Queue like this "...&Dest=665||temp"

An Error Occurred
Invalid Challenge Token!
ERROR: OTRS-CGI-10 Perl: 5.16.3 OS: linux
Traceback (47532):
Module: Kernel::Output::HTML::Layout::ChallengeTokenCheck Line: 911
Module: Kernel::Modules::CustomerTicketMessage::Run Line: 546
Module: Kernel::System::Web::InterfaceCustomer::Run Line: 1221
Module: ModPerl::ROOT::ModPerl::Registry::opt_otrs_bin_cgi_2dbin_customer_2epl::handler Line: 40
Module: (eval) (v1.99) Line: 207
Module: ModPerl::RegistryCooker::run (v1.99) Line: 207
Module: ModPerl::RegistryCooker::default_handler (v1.99) Line: 173
Module: ModPerl::Registry::handler (v1.99) Line: 32

Best regards
Thomas

[zzz]

Yeah, I just had the message aswell after my third URL parameter.
StoreNew&Dest=3||Junk&Subject=Test seems to be ok, but StoreNew&Dest=3||Junk&Subject=Test&Body=test is too much.

I am not sure why tbh, without debugging/taking a deeper look into the code.

Best regards
Emin

[Monitor02]

Yes, I get the "Fatal Error" with more than two attributes...

[Monitor02]

It is not the number of parameters. I currently have three mandatory fields and if I hand them all over, the error occurs. So if I define a dynamic field as the fourth mandatory field, I can pass three parameters (but not four).

But since I don't want to hand over all the mandatory fields anyway, I could live with the problem.
All that remains is the message that an error has occurred. If I confirm this with OK, the System has acted as requested.

Is there a way to prevent this message?

Best regards
Thomas

[Monitor02]

Sometimes it's easy. I left out "&Subaction=StoreNew" and now it works.

Thanks for the support