Using the Data field of the Transactions table

RT Developers
1

Jesse and all,

I would like to implement a feature in Asset Tracker that
would record an explanation when changing a field value,
mainly a custom field (Set) but possibly other types of
transactions.

It looks like the Data field might do the trick, although
255 characters may sometimes be limiting. It seems the Data
field is currently used only for these types of transactions:

-EmailRecord
-Correspond
-Comment
-CommentEmailRecord

This seems to be using for message threading. Is that correct?

Is there another, more flexible way you would suggest to do
what I want?

If I decide to go the Data route, is there any issue that I
should be aware of?

Any thoughts would be appreciated.

-Todd

2

Jesse and all,

I would like to implement a feature in Asset Tracker that
would record an explanation when changing a field value,
mainly a custom field (Set) but possibly other types of
transactions.

It looks like the Data field might do the trick, although
255 characters may sometimes be limiting. It seems the Data
field is currently used only for these types of transactions:

The data is a transaction-type specific field for stuffing things. Go
for it.

-EmailRecord
-Correspond
-Comment
-CommentEmailRecord

This seems to be using for message threading. Is that correct?

Not that I know of.

3

Jesse and all,

I would like to implement a feature in Asset Tracker that
would record an explanation when changing a field value,
mainly a custom field (Set) but possibly other types of
transactions.

It looks like the Data field might do the trick, although
255 characters may sometimes be limiting. It seems the Data
field is currently used only for these types of transactions:

The data is a transaction-type specific field for stuffing things. Go
for it.

Cool.

-EmailRecord
-Correspond
-Comment
-CommentEmailRecord

This seems to be using for message threading. Is that correct?

Not that I know of.

The Data for these transactions looks like message IDs, so
I assumed threading.

Is there another, more flexible way you would suggest to do
what I want?

What do you think of recording the message as a text/plain
attachment to the transaction, so that > 255 characters
can be accomdated?

Thanks, as always.

-Todd

4

What do you think of recording the message as a text/plain
attachment to the transaction, so that > 255 characters
can be accomdated?

If you do that, I’d recommend an application-specific mime type.

5

What do you think of recording the message as a text/plain
attachment to the transaction, so that > 255 characters
can be accomdated?

If you do that, I’d recommend an application-specific mime type.

Looking at all the distinct ContentType values in the Attachments
table, it seems that RT doesn’t currently use any of it’s own
mime types, that I can see anyway.

Could you explain what the advantage of having an application
specific mime type is?

Also how would a web browser know how to display my mime type?

Any pointers to practical explanations of the topic would be great.

Thanks.

-Todd

6

What do you think of recording the message as a text/plain
attachment to the transaction, so that > 255 characters
can be accomdated?

If you do that, I’d recommend an application-specific mime type.

Looking at all the distinct ContentType values in the Attachments
table, it seems that RT doesn’t currently use any of it’s own
mime types, that I can see anyway.

Could you explain what the advantage of having an application
specific mime type is?

Letting your code know that any time it sees that mime type, it has the
right to do as it pleases with it.

Also how would a web browser know how to display my mime type?

Er, no. You have your application display your mime-type.