[NXP-22751] Improve change token detection for Document.Update operation - Nuxeo Issue Tracker

XML

Word

Printable

Details

Type: Improvement
Status: Resolved
Priority: Minor
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 9.3
Component/s: Automation

Release Notes Description:

Hide

The Document.Update operation has been updated so that it is possible to use the change token mechanism and ignore system modifications, that were taken into account with previous releases.

Show
The Document.Update operation has been updated so that it is possible to use the change token mechanism and ignore system modifications, that were taken into account with previous releases.
Epic Link:
Dirty Updates
Tags:
- dev-2017-sprints-h2-93
- nxFG
Sprint:
nxFG 9.3.1
Story Points:
3

Description

Document.Update takes an optional changeToken but the checks don't take into account recent changes by ~~NXP-22019~~ and are therefore too strict (will report a conflict even if there was just a background update to the document).

It should use the new CoreSession.CHANGE_TOKEN checks.

Attachments

Issue Links

depends on

NXP-22019 Improve internal change token for optimistic locking

Resolved

Activity

People

Assignee:

Florent Guillaume

Reporter:

Florent Guillaume

Participants:

Florent Guillaume, Jenkins

Votes:

0 Vote for this issue

Watchers:

2 Start watching this issue

Dates

Created:

2017-07-11 12:22

Updated:

2018-01-14 12:45

Resolved:

2017-07-12 17:46

Time Tracking

Estimated:

Remaining:

Logged: