[rt-users] Email Priority.

[Mark Jenks]

That is exactly what I have an when I send an email into the queue with
the priority on, it doesn't set it.    I see it when I show full
headers.

How do you debug a scrip?

-----Original Message-----
From: Christian Loos [mailto:cloos at netcologne.de] 
Sent: Wednesday, August 04, 2010 10:48 AM
To: Mark Jenks
Cc: rt-users at lists.bestpractical.com
Subject: Re: Email Priority.

You have to create a new scrip with:

Description: On Create Set Priority
Condition: On Create
Action: User Defined
Template: Global template: Blank
Stage: TransactionCreate

and my code in 'Custom action cleanupcode'.

-Chris

Am 04.08.2010 17:28, schrieb Mark Jenks:
> Okay, I modified the original "On create notify requestors" and put
that
> code in.  Got nothing.
> Created a new "On create set priority" and it still didn't do
anything.
> 
> -Mark
> 
> -----Original Message-----
> From: Christian Loos [mailto:cloos at netcologne.de] 
> Sent: Wednesday, August 04, 2010 3:54 AM
> To: Mark Jenks
> Cc: rt-users at lists.bestpractical.com
> Subject: Re: Email Priority.
> 
> Create a scrip 'On Create' with the following 'Custom action cleanup
> code':
> 
> my $ticket;
> my $attachment = $self->TransactionObj->Attachments->First;
> return 1 unless $attachment;
> my $prio = $attachment->GetHeader('Priority');
> return 1 unless $prio;
> 
> if ( $prio eq 'Urgent' ) {
>   $ticket->SetPriority(50);
> }
> return 1;
> 
> -chris
> 
> Am 03.08.2010 20:17, schrieb Mark Jenks:
>> Is there a way to set a ticket priority to 50 if the user sets the
> Email
>> from outlook to Urgent?
>>
>>  
>>
>> Inside of the headers of the email exists "Priority: Urgent".
>>
>>  
>>
>> Can that be checked and acted on when a ticket gets created?
>>

CONFIDENTIALITY NOTICE:  The information contained in this email message, including any attachments, may be 
privileged, confidential and otherwise protected from disclosure.  If the reader of this message is not the 
intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this 
message, including any attachments, is strictly prohibited.  If you have received this email message in 
error, please notify the sender by reply email and delete/destroy the email message, including attachments, 
and any copies thereof.  Although we have taken precautions to minimize the risk of transmitting viruses via 
email and attachments thereto, we do not guarantee that either is virus-free, and we accept no liability for 
any damages sustained as a result of any such viruses.