Openbravo Issue Tracking System - Openbravo ERP |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0029049 | Openbravo ERP | A. Platform | public | 2015-02-24 16:47 | 2022-02-01 08:05 |
|
| Reporter | plujan | |
| Assigned To | Triage Platform Base | |
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | acknowledged | Resolution | open | |
| Platform | | OS | 5 | OS Version | |
| Product Version | pi | |
| Target Version | | Fixed in Version | | |
| Merge Request Status | |
| Review Assigned To | |
| OBNetwork customer | |
| Web browser | |
| Modules | Core |
| Support ticket | |
| Regression level | |
| Regression date | |
| Regression introduced in release | |
| Regression introduced by commit | |
| Triggers an Emergency Pack | No |
|
| Summary | 0029049: It is possible to trigger an autosave in the background tab objects when Add Payment modal pop up is open |
| Description | The Financial Account > Transaction tab has an Add Payment pop up, if I click the plus icon to open the Add Payment selector, that open pop up does not block the underlying screen objects. Incorrect functional flows are allowed because of this (an autosave in the background tab can be triggered).
Note that in the greyed area it is possible to interact with the objects, generating unexpected behaviours.
|
| Steps To Reproduce | 1. Login as Openbravo user
2. Open Financial Account window
3. Select Cuenta de Banco and move to Transaction tab
4. Create a new record and select BP Withdrawal as Type
5. Click the plus icon on the Payment field to open the Add Payment selector
6. Click anywhere outside the modal popup. An autosave will be triggered and this action will also create an "org.openbravo.base.exception.OBException: @APRM_INVALID_TRANSACTION@" message in application log.
|
| Proposed Solution | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | | related to | defect | 0029048 | | closed | Sandrahuguet | It is possible to interact with background objects when Add Payment pop up is open | | related to | defect | 0029050 | | acknowledged | Triage Platform Base | Behaviour of selector and parameter window modal popups is not homogeneous |
|
| Attached Files |  FIN_AddPaymentErrorMessage.png (81,195) 2015-02-24 16:47
https://issues.openbravo.com/file_download.php?file_id=7823&type=bug
|
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2015-02-24 16:47 | plujan | New Issue | |
| 2015-02-24 16:47 | plujan | Assigned To | => Sandrahuguet |
| 2015-02-24 16:47 | plujan | Modules | => Core |
| 2015-02-24 16:47 | plujan | Triggers an Emergency Pack | => No |
| 2015-02-24 16:47 | plujan | Issue generated from | 0029048 |
| 2015-02-24 16:47 | plujan | Relationship added | related to 0029048 |
| 2015-02-24 16:47 | plujan | File Added: FIN_AddPaymentErrorMessage.png | |
| 2015-02-24 16:52 | plujan | Assigned To | Sandrahuguet => AugustoMauch |
| 2015-02-24 17:22 | AugustoMauch | Note Added: 0074864 | |
| 2015-02-24 19:20 | dbaz | Note Added: 0074883 | |
| 2015-02-25 10:03 | AugustoMauch | Relationship added | related to 0029050 |
| 2015-02-26 08:24 | alostale | Relationship added | related to 0029035 |
| 2015-02-26 08:24 | alostale | Relationship deleted | related to 0029035 |
| 2015-02-26 08:59 | alostale | Note Added: 0074950 | |
| 2015-02-26 08:59 | alostale | Status | new => closed |
| 2015-02-26 08:59 | alostale | Resolution | open => no change required |
| 2015-02-26 09:52 | AugustoMauch | Note Added: 0074952 | |
| 2015-02-26 09:52 | AugustoMauch | Status | closed => new |
| 2015-02-26 09:52 | AugustoMauch | Resolution | no change required => open |
| 2015-02-26 09:53 | AugustoMauch | Summary | It is possible to interact with background objects when Add Payment pop up is open => It is possible to trigger an autosave in the background tab objects when Add Payment modal pop up is open |
| 2015-02-26 09:55 | AugustoMauch | Description Updated | bug_revision_view_page.php?rev_id=7764#r7764 |
| 2015-02-26 09:55 | AugustoMauch | Steps to Reproduce Updated | bug_revision_view_page.php?rev_id=7766#r7766 |
| 2015-03-06 10:35 | alostale | Priority | normal => urgent |
| 2015-03-06 10:35 | alostale | Status | new => acknowledged |
| 2015-03-17 14:37 | alostale | Assigned To | AugustoMauch => platform |
| 2015-11-11 11:37 | alostale | Priority | urgent => normal |
| 2022-02-01 08:05 | alostale | Assigned To | platform => Triage Platform Base |
|
Notes |
|
|
|
|
I think the save button is not clickable, but if the user clicks anywhere outside the popup the header tab will be selected, and that will trigger an autosave event. |
|
|
|
(0074883)
|
|
dbaz
|
|
2015-02-24 19:20
|
|
I think also that is the behavior that Augusto points.
Ideally a modal popup should 'freeze' the current opened window/tab, allowing the user navigate to other tabs (top side operation) or clicking in the grey zone without firing the autosave.
The behavior of the selectors, ideally too, should be the same of the processes modal popup (issue 29050) |
|
|
|
|
|
closing this issue as defect as it's reported as design defect in 0029050 |
|
|
|
|
|