System timestamp should follow Rules
When a field is set to receive a system parameter of timestamp
and
a Rule is created to disable the timestamp field if it is not empty
then
the "disabled" field should not get a new timestamp when the record is updated
Currently, if a field is set to get a timestamp, there is no way to use a Rule to create a condition for this behavior: the field will always get timestamped.
I want to let people update records and timestamp them, but if they update a record twice, I want to hold on to the original timestamp instead of overwriting it.
1
vote
![](https://secure.gravatar.com/avatar/3d2637c797178dbc89e725e750f048b2?size=40&default=https%3A%2F%2Fassets.uvcdn.com%2Fpkg%2Fadmin%2Ficons%2Fuser_70-6bcf9e08938533adb9bac95c3e487cb2a6d4a32f890ca6fdc82e3072e0ea0368.png)