Project:
| View Revisions: Issue #38573 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0038573: The save action of the ticket is being executed more times that should | ||
| Revision | 2018-05-21 15:34 by asiermartirena | ||
| Description | The save action of the order model is being executed locally in Web POS more times that it should, causing performance problems. When updating a line quantity, a save action is done and then the calculateReceipt process is executed, which also finishes with a save action. The second save is the only necessary (and correct) one. When introducing many lines at a time, or when doing several changes in the ticket that launches many calculateReceipt processes, the save action is also executed 2 times, when it should be executed only after the last calculate receipt. Also, when the deleting lines process finishes, a save action is executed in addition to the calculateReceipt action. In this case, the last save action is correct, but the calculateReceipt save action must be avoided. In the other hand, when loading receipts to the Web POS, the order is not being saved locally at the end of the process, which is an error, because if the user presses the F5 having that order, the ticket status is incorrect. |
||
| Revision | 2018-05-21 09:06 by asiermartirena | ||
| Description | The save action of the order model is being executed locally in Web POS more times that it should, causing performance problems. When updating a line quantity a save action is done and after the calculateReceipt process is executed, that also finishes with a save action. The second save is the only necessary (and correct) one. When introducing many lines at a time, or when doing several changes in the ticket that launches many calculateReceipt processes, the save action is also executed 2 times, when it should be executed only after the last calculate receipt. Also, when deleting lines process finishes, a save action is executed in addition to the calculateReceipt action. In this case, the last save action is correct, but the calculateReceipt save action must be avoided. In the other hand, when loading receipts to the Web POS, the order is not being saved locally at the end of the process, which is an error, because if the user presses the F5 having that order, the ticket is incorrect. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |