Web client refresh fails for chained wizards
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo Web (MOVED TO GITHUB) |
New
|
Undecided
|
Unassigned |
Bug Description
openerp-web revno: 3729
openobject-server revno: 4808
openobject-addons revno: 8615
Browser: Chrome Version 22.0.1229.94
This seems to be a bug introduced into the web client in V7.0.
Here's the situation:
1. A wizard is launched from a button on a form. If this wizard modifies the active record for the model of the form then the web client automatically refreshes the form when the wizard exits. (Which makes sense). However...
2. If the first wizard chains to a second wizard which also modifies the active record then the web client does NOT refresh when the second wizard exits. The user must manually refresh the form to see any changes made by the second wizard.
In the 6.1 web client the form would automatically refresh after the second wizard exited.
I've attached a sample module to demonstrate this behaviour.
It adds two buttons to the Sale Order form beneath the 'Customer Reference' field. Both buttons launch a simple wizard (the same one) that captures a new value for the Customer Reference. One button launches the wizard via an action, the other via a method on sale.order but both exhibit the problem.
The wizard writes the entered value to the sale order Customer Reference and has a button to then chain to a second wizard that also captures a Customer Reference value which it writes back to the sale order.
The sale order form is automatically refreshed when the first wizard terminates but not when the second one does. Any Customer Reference value entered on the second wizard is only displayed after the user manually refreshes the sale order form.