| RT::Client::REST::Attachment(3pm) | User Contributed Perl Documentation | RT::Client::REST::Attachment(3pm) |
RT::Client::REST::Attachment - attachment object representation.
version 0.56
my $attachments = $ticket->attachments;
my $count = $attachments->count;
print "There are $count attachments.\n";
my $iterator = $attachments->get_iterator;
while (my $att = &$iterator) {
print "Id: ", $att->id, "; Subject: ", $att->subject, "\n";
}
An attachment is a second-class citizen, as it does not exist (at least from the current REST protocol implementation) by itself. At the moment, it is always associated with a ticket (see parent_id attribute). Thus, you will rarely retrieve an attachment by itself; instead, you should use "attachments()" method of RT::Client::REST::Ticket object to get an iterator for all attachments for that ticket.
RT::Client::REST::Attachment is a read-only object, so you cannot "store()" it. Also, because it is a second-class citizen, you cannot "search()" or "count()" it -- use "attachments()" method provided by RT::Client::REST::Ticket.
Currently RT does not allow creating attachments via their API.
See <https://rt-wiki.bestpractical.com/wiki/REST#Ticket_Attachment>
RT::Client::REST::Ticket, RT::Client::REST::SearchResult.
This software is copyright (c) 2018 by Dmitri Tikhonov.
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.
| 2018-12-26 | perl v5.28.1 |