Thanks for your answers.
The use case is that end users are submitting forms as attachments.
This works fine until they want to submit updates to these forms. Some
are submitting a new ticket with the updated form, some are just
adding an attachment (updated form) to an old ticket. Since we are
In order to sync the life cycle of attachments and tickets, we are
exploring the idea of restricting to just one the number of attachment
for a given ticket.
Has anyone done that? Where would be a good starting point?
Thanks,
Thierry Thelliez
2011 Training:
Thierry,
That would be more difficult than you might think. Each email in RT's
ticket history is represented by a transaction with one or more
attachments. For example one email may have an html part and a plain
text part, each of which is actually stored as an attachment.
You probably want to
Thierry,
Todd makes good points about the difficulty of this, but the suggestion
to count based on non-null filenames probably wouldn't work in reality.
Many folks have images, vcards, etc automatically attached to their
outgoing email for branding purposes. Sometimes these images are inline
