Attachments

Yeah, I have a number of webforms that use attachments. They all send
e-mail (with file attached) to the rt e-mail gateway, and it
disassembles the attachments and adds them properly to the ticket.On Wed, 2007-03-28 at 15:13 +0100, John Paul Hayes wrote:

Hi All,

I’m currently developing a form which performs some basic ticket
manipulations
eg, set priority, due date etc…
Now the requirement to add attachments has arisen on this form.

I’ve searched the archives for relevant information on this but I
cannot find any.
So hence this post.

Has anybody developed such a form with this functionality before?
If so, would they be kind enought to point me in the right direction.

Thank you in advance,
Jp


The rt-users Archives

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Here’s a code snippet of a function I wrote to abstract sending e-mail
with attachments. If you read the perldoc for Mail::Sender, it talks
about attaching multiple files, etc.

sub Send_Email{
use Mail::Sender;
my ($to, $from, $subject, $message, $attach) = @_;
my $sender = new Mail::Sender{
smtp => ‘127.0.0.1’,
from => $from
};
unless($sender) { die “Send_email said $sender: $Mail::Sender::Error
\n”; }

my $mf=$sender-> MailFile({
	to => $to,
	subject => $subject,
	msg => $message,
	file => $attach
		   }); 
		   
unless($mf) { die "Send_email mailfile said $mf: $Mail::Sender::Error

\n"; }

}On Wed, 2007-03-28 at 10:22 -0400, Matthew Keller wrote:

Yeah, I have a number of webforms that use attachments. They all send
e-mail (with file attached) to the rt e-mail gateway, and it
disassembles the attachments and adds them properly to the ticket.

On Wed, 2007-03-28 at 15:13 +0100, John Paul Hayes wrote:

Hi All,

I’m currently developing a form which performs some basic ticket
manipulations
eg, set priority, due date etc…
Now the requirement to add attachments has arisen on this form.

I’ve searched the archives for relevant information on this but I
cannot find any.
So hence this post.

Has anybody developed such a form with this functionality before?
If so, would they be kind enought to point me in the right direction.

Thank you in advance,
Jp


The rt-users Archives

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com


The rt-users Archives

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

We have a workflow where when a ticket is created, a dependent approval
ticket is also created. This dependent is the “Review” stage for the
originating ticket before it hits the real “Approvals” stage and is
processed.

One of our users needs to be able to approve a “Review” by email (without
ever looking at RT due to network restrictions). This means he would need to
receive correspondence containing the originating ticket data, then respond
to that using keywords to approve. We have achieved this behaviour but
cannot call the originating ticket attachments.

If a file is attached to the original ticket when created, we need to also
attach it to the “Review” ticket and then mail it out with the “Review”
correspondence.

Here is our “Review” ticket create template which also emails the nominated
reviewer.

===Create-Ticket: Review Approval
RT-Attach-Message: yes
Depended-On-By: TOP
Queue: ReviewApproval
Owner: {$Tickets{TOP}->FirstCustomFieldValue(‘Nominate Reviewer’);}
Requestors: {$Tickets{TOP}->RequestorAddresses}
Type: approval
Due: {time + 86400}
Content-Type: text/html
Content:
(CONTENT REMOVED)
ENDOFCONTENT

The following attempts haven’t worked for us but outline what we are trying
to achieve;

Attachment: {$Tickets{TOP}->Attachments}

Attachment: {$Tickets{TOP}->Attachments->First}

View this message in context: http://requesttracker.8502.n7.nabble.com/Attachments-tp58394.html