Openbravo Issue Tracking System - POS2 | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0051378 | POS2 | POS | public | 2023-01-16 14:12 | 2023-01-16 14:55 |
| Reporter | lorenzofidalgo | ||||
| Assigned To | Retail | ||||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | main | ||||
| Target Version | Fixed in Version | ||||
| Merge Request Status | |||||
| Review Assigned To | |||||
| OBNetwork customer | |||||
| Support ticket | |||||
| Regression level | |||||
| Regression date | |||||
| Regression introduced in release | |||||
| Regression introduced by commit | |||||
| Triggers an Emergency Pack | No | ||||
| Summary | 0051378: [23Q1] An informative message is required to warn backoffice user that a new record is overwriting existent Default value | ||||
| Description | It is possible 2 different categories are marked as DEFAULT inside the same Keymap and same Organization when 1 of those categories is recorded as '*' Organization and the other one as, for example, Vall Blanca Store. In case that situation happens, the user must be informed to avoid future problems. | ||||
| Steps To Reproduce | 0-Login POS backoffice. 1-Go to POS Keymap window. 2-Select Main App Keymap record. 3-Go to Version tab and select present "OBPOS2_Store_v1" record. 4-Go to Categories tab and realise Best Seller category has Default value = Yes and its Organization value = '*'. 5-Now, click "Create a new record in form" and enter the following values: -- Organization: * Search Key: TestingXXX Name: TestingXXX Default: Yes -- Try to save that record. An error will be shown. 6-Change the Organization value from * to Vall Blanca Store. Try to save. Now, it will let you save that record. DEFECT: Realise now there are 2 different DEFAULT records saved. In case this situation is acceptable, an informative message warning the backoffice user what default record is going to be predominant must be shown. | ||||
| Proposed Solution | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2023-01-16 14:12 | lorenzofidalgo | New Issue | |||
| 2023-01-16 14:12 | lorenzofidalgo | Assigned To | => Retail | ||
| 2023-01-16 14:12 | lorenzofidalgo | Triggers an Emergency Pack | => No | ||
| 2023-01-16 14:55 | lorenzofidalgo | Summary | [23Q1] An informative message is required to warn backoffice user that a new record is overwritten existent Default value => [23Q1] An informative message is required to warn backoffice user that a new record is overwriting existent Default value | ||
| There are no notes attached to this issue. |