[rt-users] Question on use of Category in a scrip

[Rémi]

I agree that it might be good to have this information in the Wiki. But the
solution I proposed is probably not the better one and could cause some
unwanted load on the system.

Even if we can't access the "CF Category" directly by the RT API, I 'm sure
we can do it with a simple sql query,
I'm a bit confused with the RT DB schema to do it fast, I will work on it
when I have some time.
If somebody can help me doing this, it will be welcome.


2009/6/11 Cassandra Phillips-Sears <cassandra at bestpractical.com>

> It might be good if someone could update the wiki with this code, but I
> don't think I should be the one to do it as I'm not a programmer. ;) I think
> it might be helpful for others trying to answer this question in the future.
> --
> Cassandra Phillips-Sears
> Office Manager
> Best Practical Solutions, LLC
> http://www.bestpractical.com
>
> On Jun 10, 2009, at 11:12 AM 6/10/09, Rémi wrote:
>
> Hi Ken,
>
> here is the code I use to do what you want (quite painful like Jesse says
> ...)
>
> my $CustomFieldObj = RT::CustomField->new($_[0]->CurrentUser);
> $CustomFieldObj->LoadById($field);
> my $CFVs = $CustomFieldObj->Values;
> while ($CFVs and my $value = $CFVs->Next ) {
>        if ($value->Name eq $_[0]->FirstCustomFieldValue($field)){
>                    return $value->Category;
>         }
> }
>
> ($_[0] is a the Ticket object and $field is the CF id)
>
>
> Rémi
>
>
> 2009/6/9 Ken Crocker <kfcrocker at lbl.gov>
>
>>  Jesse,
>>
>>
>>     Painful?? Please explain. I'd love to hear it.
>>
>> Kenn
>> LBNL
>>
>> On 6/9/2009 11:56 AM, Jesse Vincent wrote:
>>
>> On Tue  9.Jun'09 at 11:26:08 -0700, Ken Crocker wrote:
>>
>>
>>  Jesse,
>>
>>     I was thinking that that particular command gave me the Custom Field value
>> only. I don't see where the "category" value for that CF can be determined from
>> that code.
>>
>>
>>  Indeed. I misread your question.  Category is an attribute of the
>> CustomFieldValue, itself.   Getting at it will require some more work
>> and will be a bit painful
>>
>>
>>
>>
>> _______________________________________________
>> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>>
>> Community help: http://wiki.bestpractical.com
>> Commercial support: sales at bestpractical.com
>>
>>
>> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
>> Buy a copy at http://rtbook.bestpractical.com
>>
>
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>
> Community help: http://wiki.bestpractical.com
> Commercial support: sales at bestpractical.com
>
>
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> Buy a copy at http://rtbook.bestpractical.com
>
>
>
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>
> Community help: http://wiki.bestpractical.com
> Commercial support: sales at bestpractical.com
>
>
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> Buy a copy at http://rtbook.bestpractical.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20090615/0d53b7bd/attachment.htm>