Ticket NXP-19435 gives the base framework to have an internal change token. However it must be improved to be more fine-grained and allow concurrent updates if one is "user" and the other is "system" and they don't overlap.
The change token returned to the user-level API DocumentModel.getChangeToken() is now a mix of a system change token (updated at every change) and a user change token (updated at every user change). A "user change" is a change initiated by a user-level operation, which is defined as a document save that passes a previous change token using doc.putContextData(CoreSession.CHANGE_TOKEN, token), or that marks the save as an explicit user change using doc.putContextData(CoreSession.USER_CHANGE, Boolean.TRUE).
- depends on
-
NXP-22641 Salesforce addon: internal server error, java.lang.ClassCastException
- Resolved
-
NXP-22127 Fix spurious ConcurrentUpdateException
- Resolved
-
NXP-19435 Internal change token for optimistic locking
- Resolved
-
NXP-22259 Internal document version/timestamp (system change token)
- Resolved
- is duplicated by
-
NXP-16144 Add a system modification field in all documents
- Resolved
- is related to
-
NXP-22900 Fix ConcurrentUpdateException when Removing Collection Member
- Resolved
- is required by
-
NXP-22254 Add ability to set change token from REST API
- Resolved
-
NXP-22751 Improve change token detection for Document.Update operation
- Resolved