Subject: | AddWatcher Unimplemented and others |
Date: | Tue, 4 Sep 2018 13:31:45 +0000 (UTC) |
To: | "bug-RT-Extension-REST2 [...] rt.cpan.org" <bug-RT-Extension-REST2 [...] rt.cpan.org> |
From: | Dimitris Maniadakis <chaniadimitris [...] yahoo.gr> |
Hello,
after using REST2 for a while, now I may ask for some info about the following issues, regarding Assets:
1) I cannot have a successful update of an asset in its Roles (Owner, Contact, HeldBy) with PUT method. The rt.log gives me at that point:
[error]: RT::Asset::AddWatcher Unimplemented in RT::Extension::REST2::Resource::Record::Writable. (/opt/rt4/local/plugins/RT-Extension-REST2/lib/RT/Extension/REST2/Resource/Record/Writable.pm line 167) (/opt/rt4/local/plugins/RT-Extension-REST2/lib/RT/Extension/REST2/Middleware/Log.pm:14)
2) I observe that the update of an asset with PUT method for empty custom fields which remain empty, actually leads to creating history records such as: "yyyy added" or for date cf: "xxxx Not set changed to Not set". These records are undesired since no actual modification has occurred.
3) I realize that I cannot modify the Creator role of an asset using the PUT (or POST) method. I think it only gets the "root (Enoch Root)" which is the account I used for creating the authentication token. How could I modify it?
4) I cannot find a way to change "page" or increase the "per_page" limit at the pagination of any GET results. For example, to GET the first 100 assets I tried without success to post at /REST/2.0/assets the parameter "per_page"=>"100". By the way, is there a GET /assets/allĀ ?
Notes: RT 4.4.3, Ubuntu 16.04.5 LTS, perl v5.22.1
Kind regards,
Dimitris