Extracting Custom Fields from Email

RT Users
1

Anyone one have a set of instructions (I’ve looked at and tried the
wiki, read the Harrier book for some background, and tried several
configurations) for setting up RT to process the custom fields out of
an email.

CentOS 5.3 (Linux-Vserver guest)
RT 3.8.4
PostgreSQL 8.3.x (on a remote system)

Installed the package RT::Extension::ExtractCustomFieldValues,

Created a custom field.

Name: Contact
…
Type: Enter one value
Applies to: Tickets (should this be TicketTransactions?)

Created a template: ScanTesting

with this content;

||||

Contact|body|Contact:\s*.*

Created a scrip

Description: TestingCFExtract
Condition: On Create
Action: Extract Custom Field Values
Template: ScanTesting
Stage: TransactionCreate

Any pointers, suggestions, ideas, clarification ofhow this is suppose to
happen?

\||/
Rod

2

Anyone one have a set of instructions (I’ve looked at and tried the
wiki, read the Harrier book for some background, and tried several
configurations) for setting up RT to process the custom fields out
of
an email.

CentOS 5.3 (Linux-Vserver guest)
RT 3.8.4
PostgreSQL 8.3.x (on a remote system)

Installed the package RT::Extension::ExtractCustomFieldValues,

If you have debug logging turned on, the CPAN version of ECFV is
very chatty

Created a custom field.

Name: Contact
…
Type: Enter one value
Applies to: Tickets (should this be TicketTransactions?)

Created a template: ScanTesting

with this content;

||||

Contact|body|Contact:\s*.*

You probably wanted (.*) to capture the value

-kevin

3

Kevin Falcone wrote:

Anyone one have a set of instructions (I’ve looked at and tried the
wiki, read the Harrier book for some background, and tried several
configurations) for setting up RT to process the custom fields out
of
an email.

CentOS 5.3 (Linux-Vserver guest)
RT 3.8.4
PostgreSQL 8.3.x (on a remote system)

Installed the package RT::Extension::ExtractCustomFieldValues,

If you have debug logging turned on, the CPAN version of ECFV is
very chatty

Thanks Kevin.

There might have been a brain-fart on my part involved. I haven’t got
back to it this AM but while dozing off last night I had the thought I
was sending to the wrong queue/email address. No wonder it wasn’t
processing.

Created a custom field.

Name: Contact
…
Type: Enter one value
Applies to: Tickets (should this be TicketTransactions?)

I also realized I am unclear as which to use: Tickets or TicketTransactions.

Created a template: ScanTesting

with this content;

||||

Contact|body|Contact:\s*.*

You probably wanted (.*) to capture the value

Yeah I was thinking I wanted it with one or none spaces. Why? Who knows.

\||/
Rod

4

Roderick A. Anderson wrote:

Anyone one have a set of instructions (I’ve looked at and tried the
wiki, read the Harrier book for some background, and tried several
configurations) for setting up RT to process the custom fields out of
an email.

Turns out it was a mistake on my part. I kept sending to the wrong
queue/email address.

Works now.

\||/
Rod