In the past, we have integrated a live chat solution like Olark with our Mendix apps. These provide chat and remote browser viewing/control.
Not until it’s committed.
You could create a temporary (but persistent) helper entity that the customer fills out (with onchange microflows that commit the object) and that the assisting user can also see. Add a microflow button as Save/commit action and in the microflow, validate and then create and commit the database entry you actually want and delete the helper object.
Thank you Martin,
But how to refresh the second user browser after each commit?
Thank you Martin and Mike for your answers, it really helps.
I hope that Mendix will find a way to manage this kind of need.