If the CommandByEmail plugin worked for setting Custom Fields, you could
create a custom fields and set it. But I have not been able to set custom
fields by mail!
Has anybody tried
CustomField.{CFName}:
Or
CF.{CFName}:
Or the AddCF versions? And can someone point the difference between
CF.{CFName} and AddCF.{CFName}? There is one instance of someone claiming he
looked at the code and found out how to use them, but he did not say how.
They sure don’t work like the wiki claims they should…
Niki Serakiotou
Client Services Manager
Rice University Division of Information Technology
cell: 713-992-1327
office: 713-348-4887
Address: Mudd 106C, Rice University, 1600 Main Street, Houston, TX 77005
Niki Serakiotou escribi�:
If the CommandByEmail plugin worked for setting Custom Fields, you could
create a custom fields and set it. But I have not been able to set custom
fields by mail!
Has anybody tried
CustomField.{CFName}:
Or
CF.{CFName}:
Or the AddCF versions? And can someone point the difference between
CF.{CFName} and AddCF.{CFName}? There is one instance of someone claiming he
looked at the code and found out how to use them, but he did not say how.
They sure don’t work like the wiki claims they should…
Thanks Niki, but I’m not sure how to make CommandByMail to recognize
them as commands, and even how to handle them later.
I just want to make something easier I believe, like a ‘command alias’:
redirect a custom command like ‘Asunto: something’ → ‘Subject:
something’, maybe through a scrip?
Francisco G�mez Mar�n
Depatamento de Seguridad
Centro Inform�tico Cient�fico de Andaluc�a (CICA)
Avda. Reina Mercedes s/n - 41012 - Sevilla (Spain)
Tfno.: +34 955 056 600 / FAX: +34 955 056 650
Consejer�a de Innovaci�n, Ciencia y Empresa
Junta de Andaluc�a
There is an extension available to do field assignment by email “Extract
Custom Field Value Extension” is the name… Best Practical coded it and
offers support on it…
maybe this is what you are looking for?
Mike Johnson
Datatel Programmer/Analyst
Northern Ontario School of Medicine
955 Oliver Road
Thunder Bay, ON P7B 5E1
Phone: (807) 766-7331
Email: mike.johnson@normed.ca
Technology assistance: email nosmhelpdesk@normed.ca
Technology Emergency Contact (TEC) Mon-Fri, 8am to 5pm excluding stat
holidays:
Off campus toll free 1 (800) 461-8777, option 8, or locally either
(705) 662-7120 or (807) 766-7500
Francisco Gómez Marín fgomez@cica.es 05/01/2010 5:45 am >>>
Niki Serakiotou escribió:
If the CommandByEmail plugin worked for setting Custom Fields, you
could
create a custom fields and set it. But I have not been able to set
custom
fields by mail!
Has anybody tried
CustomField.{CFName}:
Or
CF.{CFName}:
Or the AddCF versions? And can someone point the difference between
CF.{CFName} and AddCF.{CFName}? There is one instance of someone
claiming he
looked at the code and found out how to use them, but he did not say
how.
They sure don’t work like the wiki claims they should…
Thanks Niki, but I’m not sure how to make CommandByMail to recognize
them as commands, and even how to handle them later.
I just want to make something easier I believe, like a ‘command alias’:
redirect a custom command like ‘Asunto: something’ → ‘Subject:
something’, maybe through a scrip?
Francisco Gómez Marín
Depatamento de Seguridad
Centro Informático Científico de Andalucía (CICA)
Avda. Reina Mercedes s/n - 41012 - Sevilla (Spain)
Tfno.: +34 955 056 600 / FAX: +34 955 056 650
Consejería de Innovación, Ciencia y Empresa
Junta de Andalucía
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com
Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
Niki Serakiotou escribi?:
If the CommandByEmail plugin worked for setting Custom Fields, you could
create a custom fields and set it. But I have not been able to set custom
fields by mail!
Has anybody tried
CustomField.{CFName}:
Or
CF.{CFName}:
Or the AddCF versions? And can someone point the difference between
CF.{CFName} and AddCF.{CFName}? There is one instance of someone claiming he
looked at the code and found out how to use them, but he did not say how.
They sure don’t work like the wiki claims they should…
Thanks Niki, but I’m not sure how to make CommandByMail to recognize
them as commands, and even how to handle them later.
I just want to make something easier I believe, like a ‘command alias’:
redirect a custom command like ‘Asunto: something’ → ‘Subject:
something’, maybe through a scrip?
–
Francisco G?mez Mar?n
There is a documentation problem on the wiki page in the description
for Custom field management. It describes the syntax as:
Custom field values
Manage custom field values. Could be used multiple times.
CustomField.{CFName}: <custom field value>
AddCustomField.{CFName}: <custom field value>
DelCustomField.{CFName}: <custom field value>
Short forms:
CF.{CFName}: <custom field value>
AddCF.{CFName}: <custom field value>
DelCF.{CFName}: <custom field value>
But the ‘.’ is used in the perl code and is incorrect for the actual
use which should be:
Custom field values
Manage custom field values. Could be used multiple times.
CustomField{CFName}: <custom field value>
AddCustomField{CFName}: <custom field value>
DelCustomField{CFName}: <custom field value>
Short forms:
CF{CFName}: <custom field value>
AddCF{CFName}: <custom field value>
DelCF{CFName}: <custom field value>
As far as creating your own “commands”, you will need to make a
local version of the TakeAction.pm file that comes with the Extension.
It looks straightforward enough using the original as a guide. It would
be nice if the extension supported several different languages by default
like the RT system itself.
Regards,
Ken
There is a documentation problem on the wiki page in the description
for Custom field management. It describes the syntax as:
There are tests (t/03update.t for example) that use the
CustomField.{CFName} syntax, and a canonicalize command that cleans
CustomField.{CFName} into CustomField{CFName} so they should both
work.
If there is really a bug here, I’d appreciate something in the
rt.cpan.org queue for RT-Extension-CommandByMail, which is the easiest
place to track things.
This reminds me that the 0.08_01 should become 0.08 this week
-kevin
Sorry about that. You are correct. I only looked briefly at the
code and the version without the ‘.’ is the common format, which
I tested. The versions with the ‘.’ also work for me. The docs
are correct as written.
Regards,
KenOn Tue, Jan 05, 2010 at 10:34:42AM -0500, Kevin Falcone wrote:
On Tue, Jan 05, 2010 at 08:04:21AM -0600, Kenneth Marshall wrote:
There is a documentation problem on the wiki page in the description
for Custom field management. It describes the syntax as:
There are tests (t/03update.t for example) that use the
CustomField.{CFName} syntax, and a canonicalize command that cleans
CustomField.{CFName} into CustomField{CFName} so they should both
work.
If there is really a bug here, I’d appreciate something in the
rt.cpan.org queue for RT-Extension-CommandByMail, which is the easiest
place to track things.
This reminds me that the 0.08_01 should become 0.08 this week
-kevin
Custom field values
Manage custom field values. Could be used multiple times.
CustomField.{CFName}: <custom field value>
AddCustomField.{CFName}: <custom field value>
DelCustomField.{CFName}: <custom field value>
Short forms:
CF.{CFName}: <custom field value>
AddCF.{CFName}: <custom field value>
DelCF.{CFName}: <custom field value>
But the ‘.’ is used in the perl code and is incorrect for the actual
use which should be:
Custom field values
Manage custom field values. Could be used multiple times.
CustomField{CFName}: <custom field value>
AddCustomField{CFName}: <custom field value>
DelCustomField{CFName}: <custom field value>
Short forms:
CF{CFName}: <custom field value>
AddCF{CFName}: <custom field value>
DelCF{CFName}: <custom field value>
As far as creating your own “commands”, you will need to make a
local version of the TakeAction.pm file that comes with the Extension.
It looks straightforward enough using the original as a guide. It would
be nice if the extension supported several different languages by default
like the RT system itself.
The rt-users Archives
Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com
Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
Sorry about that. You are correct. I only looked briefly at the
code and the version without the ‘.’ is the common format, which
I tested. The versions with the ‘.’ also work for me. The docs
are correct as written.
Thanks for the confirmation Ken, I was worried that our tests were
insufficient in some way.
-kevin> On Tue, Jan 05, 2010 at 10:34:42AM -0500, Kevin Falcone wrote:
On Tue, Jan 05, 2010 at 08:04:21AM -0600, Kenneth Marshall wrote:
There is a documentation problem on the wiki page in the description
for Custom field management. It describes the syntax as:
There are tests (t/03update.t for example) that use the
CustomField.{CFName} syntax, and a canonicalize command that cleans
CustomField.{CFName} into CustomField{CFName} so they should both
work.
If there is really a bug here, I’d appreciate something in the
rt.cpan.org queue for RT-Extension-CommandByMail, which is the easiest
place to track things.
This reminds me that the 0.08_01 should become 0.08 this week
-kevin
Custom field values
Manage custom field values. Could be used multiple times.
CustomField.{CFName}: <custom field value>
AddCustomField.{CFName}: <custom field value>
DelCustomField.{CFName}: <custom field value>
Short forms:
CF.{CFName}: <custom field value>
AddCF.{CFName}: <custom field value>
DelCF.{CFName}: <custom field value>
But the ‘.’ is used in the perl code and is incorrect for the actual
use which should be:
Custom field values
Manage custom field values. Could be used multiple times.
CustomField{CFName}: <custom field value>
AddCustomField{CFName}: <custom field value>
DelCustomField{CFName}: <custom field value>
Short forms:
CF{CFName}: <custom field value>
AddCF{CFName}: <custom field value>
DelCF{CFName}: <custom field value>
As far as creating your own “commands”, you will need to make a
local version of the TakeAction.pm file that comes with the Extension.
It looks straightforward enough using the original as a guide. It would
be nice if the extension supported several different languages by default
like the RT system itself.
The rt-users Archives
Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com
Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
The rt-users Archives
Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com
Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
As far as creating your own “commands”, you will need to make a
local version of the TakeAction.pm file that comes with the Extension.
It looks straightforward enough using the original as a guide. It would
be nice if the extension supported several different languages by default
like the RT system itself.
Unfortunately, the extension would have a really hard time knowing if
a mail written in latin1 should be parsed with the french, spanish,
portugues or british translations. It would also really complicate
the parsing engine.
It may be easier to follow the previous suggestion of
RT-Extension-ExtractCustomFieldValues to implement something that is
language specific (depending on coding skills and what needs doing)
-kevin