we are looking at the following unexpected behaviour: User A (backoffice): datagrid-based form where depending on status ('ready to ship') of a line they can 'finalize' an order. This will open a dataview where they do some checks and then 'push the button'. User B (Order picking): they see assigned orders, fullfill them and mark the order as 'ready to ship'. When User A is looking at their overview and the notice a "ready to ship order', and open it, instead of seeing the fullfiled order, they get to see the "previous state", as if User B had not acted, which is weird, as the OVERVIEW show the correct, advanced, status. Upon canceling and reopening the order opens to the correct status... This behaviour ONLY shows up when User A is still logged on and on the overview whilst User B does their thing. Should user A be logged off and logon again the flow works as expected. The issue appears both in IE and Chrome.... Am I looking at chacheing issues? Suggestions are welcome
Lex van Rooy
Suggestion is that you look to the moment of the commit. This behaviour can happen with autocommits. So committing on the right time could solve this problem
Martin van Dijk
With the insight provided by both Martin and Ronald my partner methodicly tested. Essentially as far as we can tell, it boils down to this.
On the Order Picking side al works well, as they work through each order individualy and once it is reported finished the commit correctly refreshes their overview.
The backoffice however is working from a "list" which is NOT refreshed, unless they completly leave the overview screen. In order for them to get a correct individual presentation of the order we added a "commit- no action - refresh in client" in the workflow to open the dataview which fixed the problem.