This content has been marked as final. Show 4 replies
This is OSM's behaviour and is working accordingly. Let me explain
1)In Task 1, for one element lets say Element A you have entered value "X"
2)In Task 3, you modified the element A's value to "ABC". Please notice, element A will still have value "X" stored on history but not visible.
3)So, when you submit amendment, Task 3 will have "ABC" and will undo. <Fine, so far so good>
4)In Task 1, Element A was processed with value "X" before, so, that value has to be undone too. Remember we have undone "ABC" before, so as "X" also has to be undone.
Now, if you still want to achieve your mentioned scenario, then instead of changing the value from "X" -> "ABC" direclty as part of order process, you should raise an amendment and do it. Then everything will work as you expect above.
Hi N Singh,
Without introducing amendments, the feature you suggested is not possible. Especially while undoing the task, OSM will fetch the data that was present when exiting/completing that particular task. As you know this is OSM's behavior.
I am left with the suggestion to change the workflow. Anyways, please wait for experts comments.