RT 3.4 CF API question

RT Developers
1

Jesse and All,

For Enter One Value custom fields, why does RT disable
the old value when a new value is entered, instead of
deleting it?

Thanks.

-Todd

2

Jesse and All,

For Enter One Value custom fields, why does RT disable
the old value when a new value is entered, instead of
deleting it?

Because if you deleted it, then it would vanish from the transaction
history. (Larger values are stored by reference)

3

Jesse and All,

For Enter One Value custom fields, why does RT disable
the old value when a new value is entered, instead of
deleting it?

Because if you deleted it, then it would vanish from the transaction
history. (Larger values are stored by reference)

–
How about deleting one that are not LargeContent? Frequently
updated (small)Content fields make the database grow for no
reason. This is probably not an issue for something short
lived, like a Ticket, but may be for something long lived,
like an Asset.

-Todd

4

How about deleting one that are not LargeContent? Frequently
updated (small)Content fields make the database grow for no
reason. This is probably not an issue for something short
lived, like a Ticket, but may be for something long lived,
like an Asset.

Not really how it works. IIRC, the code is moving or has moved toward
doing all cfs by reference.

5

I would guess that this is for the same reason that tickets aren’t
deleted - tracking past values, etc. for troubleshooting.

DB

Todd Chapman wrote: