Project:
| View Revisions: Issue #48472 | [ Back to Issue ] | ||
| Summary | 0048472: Problem using the circle task in order to confirm a task | ||
| Revision | 2022-01-25 18:32 by idiez | ||
| Steps To Reproduce | If the user confirms the tasks quickly using the "ball" associated with the task instead of via the orange "Confirm" button on the FE AWO. It works correctly if the "Confirm" button is used, although this is not the most common operation when the device is a PDA in which only one of the two parts of the screen is shown https://drive.google.com/file/d/1a0GOW_ovE_QwmT0snEwoh6fp4MmvtUEz/view?usp=sharing [^] [^] Issue can be reproduced in livebuilds also https://drive.google.com/file/d/11rHsYm9OuB5V5Ko0kdEELiZJtPmFhYTd/view?usp=sharing [^] |
||
| Revision | 2022-01-25 18:30 by idiez | ||
| Steps To Reproduce | If the user confirms the tasks quickly using the "ball" associated with the task instead of via the orange "Confirm" button on the FE AWO. It works correctly if the "Confirm" button is used, although this is not the most common operation when the device is a PDA in which only one of the two parts of the screen is shown https://drive.google.com/file/d/1a0GOW_ovE_QwmT0snEwoh6fp4MmvtUEz/view?usp=sharing [^] [^] Issue happens in livebuilds also https://drive.google.com/file/d/11rHsYm9OuB5V5Ko0kdEELiZJtPmFhYTd/view?usp=sharing [^] |
||
| Revision | 2022-01-25 18:01 by idiez | ||
| Steps To Reproduce | The steps to reproduce are the same as in the related issue If the user confirms the tasks quickly using the "ball" associated with the task instead of via the orange "Confirm" button on the FE AWO. It works correctly if the "Confirm" button is used, although this is not the most common operation when the device is a PDA in which only one of the two parts of the screen is shown https://drive.google.com/file/d/1a0GOW_ovE_QwmT0snEwoh6fp4MmvtUEz/view?usp=sharing [^] [^] Issue happens in livebuilds also https://drive.google.com/file/d/11rHsYm9OuB5V5Ko0kdEELiZJtPmFhYTd/view?usp=sharing [^] |
||
| Revision | 2022-01-25 08:39 by ranjith_qualiantech_com | ||
| Steps To Reproduce | 1) Set the preference "Limit of tasks to be loaded by mobile application" to a high enough value, for example 300 tasks as seen in the image 2) Assign a high number of pending tasks to confirm any type (picking, receipt, move, etc.), for example 200 to a user 3) Access the FE AWO with that user and confirm the first one. Observe that the "Loading" bar appears for several minutes (2-5 ') -> KO! After this time, two things can happen: that the browser is "frozen" or that it ends with the correctly confirmed task 4) Confirm the next user task -> OK. The task is normally confirmed in less than 1 sec. 5) The behavior in 3) is reproducible every time the user refreshes their task list or a task is added to their queue If the user confirms the tasks quickly using the "ball" associated with the task instead of via the orange "Confirm" button on the FE AWO. It works correctly if the "Confirm" button is used, although this is not the most common operation when the device is a PDA in which only one of the two parts of the screen is shown https://drive.google.com/file/d/1a0GOW_ovE_QwmT0snEwoh6fp4MmvtUEz/view?usp=sharing [^] [^] Issue happens in livebuilds also https://drive.google.com/file/d/11rHsYm9OuB5V5Ko0kdEELiZJtPmFhYTd/view?usp=sharing [^] |
||
| Revision | 2022-01-24 14:09 by ranjith_qualiantech_com | ||
| Steps To Reproduce | 1) Set the preference "Limit of tasks to be loaded by mobile application" to a high enough value, for example 300 tasks as seen in the image 2) Assign a high number of pending tasks to confirm any type (picking, receipt, move, etc.), for example 200 to a user 3) Access the FE AWO with that user and confirm the first one. Observe that the "Loading" bar appears for several minutes (2-5 ') -> KO! After this time, two things can happen: that the browser is "frozen" or that it ends with the correctly confirmed task 4) Confirm the next user task -> OK. The task is normally confirmed in less than 1 sec. 5) The behavior in 3) is reproducible every time the user refreshes their task list or a task is added to their queue If the user confirms the tasks quickly using the "ball" associated with the task instead of via the orange "Confirm" button on the FE AWO. It works correctly if the "Confirm" button is used, although this is not the most common operation when the device is a PDA in which only one of the two parts of the screen is shown https://drive.google.com/file/d/1a0GOW_ovE_QwmT0snEwoh6fp4MmvtUEz/view?usp=sharing [^] [^] |
||
| Revision | 2022-01-24 13:20 by idiez | ||
| Description | he client is using: Environment: 21Q2.2 Advanced Warehouse Operations 1.5.212000 : If the user confirms the tasks quickly using the "ball" associated with the task as seen in the video linked (instead of using the orange "Confirm" button on the FE AWO); tasks already confirmed appear (are refreshed) again in the user front-end. |
||
| Revision | 2022-01-24 13:17 by idiez | ||
| Description | he client is using: Environment: 21Q2.2 Advanced Warehouse Operations 1.5.212000 At various points in the warehouse, work is carried out with a high volume of tasks. It is not possible to reduce the value of the preference because then when scanning a product of a task assigned to the user that is not loaded it would not be located in the FE. Right now they have had to spend the day confirming tasks from the BE since from the FE it is inoperable It is difficult to work with a large flow of tasks The problem may have arisen with the possible regression that could be introduced in https://issues.openbravo.com/view.php?id=0041775 [^] [^] since in the previous version of the client (19Q3), this behavior did not occur, yet having 200 or 300 tasks loaded in the FE. Comparing the code of the 2 versions of the client environments (21Q2 vs. 19Q3) we believe that the problem could be in the code of obawo-tasks-view.js, specifically in the part indicated in the image |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |