|
NAMERT::Client::REST::Transaction - transaction object representation. VERSIONversion 0.72 SYNOPSIS my $transactions = $ticket->transactions;
my $count = $transactions->count;
print "There are $count transactions.\n";
my $iterator = $transactions->get_iterator;
while (my $tr = &$iterator) {
print "Id: ", $tr->id, "; Type: ", $tr->type, "\n";
}
DESCRIPTIONA transaction 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 a transaction by itself; instead, you should use transactions() method of RT::Client::REST::Ticket object to get an iterator for all (or some) transactions for that ticket. ATTRIBUTES
METHODSRT::Client::REST::Transaction 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 transactions() method provided by RT::Client::REST::Ticket.
INTERNAL METHODS
SEE ALSORT::Client::REST, RT::Client::REST::Ticket, RT::Client::REST::SearchResult. AUTHORDean Hamstead <dean@fragfest.com.au> COPYRIGHT AND LICENSEThis software is copyright (c) 2023, 2020 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.
|