Use technical event date for optimistic locking

[S-Tim]

Scenario

• camunda-bpm-taskpool version: any
• Camunda BPM version: any
• Description of your use case: (detailed description or executable reproducer, e.g. GitHub repo)

When updating data entries for technical reasons (for example enriching the payload with a previously non-existing attribute) we want to keep the last updated date because it is part of our domain and relevant for the users in the UI. We would still like an optimistic locking mechanism, so using a new field with the technical date of the event would be good.

Current Behaviour

Currently the date from the Modification is used for optimistic locking. When the provided date is older than the last updated date on the JPA entity, then the update is ignored.

Wanted Behaviour

Newer events (according to the domain event timestamp) should not be ignored, even if the timestamp in the modification is older.

Possible Workarounds

Database or modification timestamp modification