Looking at the roadmap I've gained some hope that the bug was recognized. Unfortunately I haven´t received any official confirmation yet. I assume Aras is just a bit shy. Or they hope that I get impatient enough to patch it by myself (...just to release an official patch one day after...).
Nevertheless, I want to keep the bug list as complete as possible. So here a few new scenarios related to this behavior.
Reproduce Error 4 (Roadtrip to uncanny valley)
1. Start from setup above. We are in the tab with the latest revision
2. Click "Edit" (but do nothing else)!
3. Then just click "Discard"
4. Now just switch back to the tab with the previous revision of the Method
5. We now can see the green flag in the previous revision
6. Click on the green flag to unlock the item
7. Toolbar will get confused and we now get a nice grayed Save and Done button.
8. This bug is mainly an optical glitch. It doesn´t do much harm. I think it´s a nice extension to the above collection.
Reproduce Error 5 (Lock seems to be the root cause)
Here I start from the previous scenario, but have changed the Method ItemType. I extended the keyed_name so it combines the "name" and "generation" property.
1. Start from setup above. We are in the tab with the latest revision
2. Use side-by-side mode for direct comparison of the items
3. Lock the latest revision by clicking the "flag" -> Flag turns green
4. Note that the previous revision will immediately change
This image shows the result: Context item was updated on lock, but the Form still shows the previous content:
I assume claim/unclaim is the root cause. Both events are fired when we try to edit an item.
