Maybe a newbee question, but does anybody know which variable contains the Requestors RealName ?
{$Ticket->Requestors->EmailsAsString()} gives the email address
{$Transaction->CreatorObj->RealName()} is not what I want because that one doesn’t work after a
ticket is resolved.
Thanks,
Len Kranendonk - www.primaat.com
Len Kranendonk wrote:
Maybe a newbee question, but does anybody know which variable contains
the Requestors RealName ?
{$Ticket->Requestors->EmailsAsString()} gives the email address
Note the plural in the above, giving potentially many e-mail addresses
in a single string. That’s because a ticket can have more than one
requestor (though only one owner, which is why OwnerObj had the method
you found).
Since it doesn’t really make sense to have a string containing many
names, there isn’t a function to do this; you have to grab the name of
each requestor individually.
To see how this works, have a look at the nice diagram that Bruce drew.
Go to the list archive:
http://lists.fsck.com/cgi-bin/htsearch
and search for “human female”; currently it’s the only mail on the list
containing that term. (Though of course once I’ve sent this mail, that
– plus any follow-ups – will also be in the archive containing that
string.)
Smylers
GBdirect
and search for “human female”; currently it’s the only mail on the list
containing that term. (Though of course once I’ve sent this mail, that
– plus any follow-ups – will also be in the archive containing that
string.)
And I still don’t have an adequate behavioural schema for
God->Image->Man->Female , or Evolution->HomoSapien->Female . sigh
->Man->Male->Nationality( ‘US’ ) is mostly wrapped up, but
->Man->Male->Nationality( ‘NL’ ) is proving interesting at times.
Bruce Campbell RIPE
Systems/Network Engineer NCC
www.ripe.net - PGP562C8B1B Operations/Security