Is there any Documentaion for Ticket CMD?

[nhoot]

I saw that there is a "Ticket CMD" box in the generic agent, is there any documentation for this feature?
What I would like to do is have the generic agent send out an email for the task after making some changes to it.

NOTE: Not the reminder email, but an actual response email such as you get when you initially create the ticket. This way we can use the generic agent to run custom modules & manipulate tickets based on the response to the initial email and then send it out again.

[jojo]

it will run a script/programm on the OTRS Server and giving TicketID and Ticket# as values...

[crythias]

don't forget Notification (Event)...

[nhoot]

OK! thats Useful to know!, Doesnt solve my current problem, but will definitley come in handy!
Crythias, What is notification(event)?
and is there a way to just fire off the ticket in its current state as an E-Mail? I think I saw in another thread where someone mentioned that this could be done with follow-up responses, but there description in the admin manual is breif in that regard.

EDIT:
OK Found notifications but I am assuming that since they come from the notification master, that replys to these notifications will not appear in the OTRS ticket. So that doesnt quite work either.

[crythias]

... replys to these notifications will not appear in the OTRS ticket. So that doesnt quite work either.

Depends on the notification master's email address.

[nhoot]

Hmm intresting.. Do the notifications also have the X-OTRS Header information?

[crythias]

It probably doesn't matter much because the ticket# is in the subject.

[nhoot]

Absolutely Right!
Very close to what we need now!
Just missing one thing now, when I do a notify, is there a way to include the entire ticket in the body of the message?
Also need a way to add attatchments to the notifications, I assume there is a way to do this?

To provide some context, we are trying to setup a system whereby the agents and customers will work entirely Via Email (each ticket will involve multiple agents), and I am almost done prototyping it. All thats missing at this point is a way to modify the notification to include the entire ticket Preferably in lieu of the OTRS link at the bottom of the email), that way I can just use generic Agent to manipulate the tickets, and the notification it sends out will also send each person who begins working on it the complete history of the ticket, Then their reply to the ticket will include a text flag that the generic agent can use to determine the tickets status and pass it off to the next person/queue/escalation/etc.