Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
ID | ||||||||||||
0051378 | ||||||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
defect | [POS2] POS | minor | always | 2023-01-16 14:12 | 2023-01-16 14:55 | |||||||
Reporter | lorenzofidalgo | View Status | public | |||||||||
Assigned To | Retail | |||||||||||
Priority | normal | Resolution | open | Fixed in Version | ||||||||
Status | new | Fix in branch | Fixed in SCM revision | |||||||||
Projection | none | ETA | none | Target Version | ||||||||
OS | Any | Database | Any | Java version | ||||||||
OS Version | Database version | Ant version | ||||||||||
Product Version | main | SCM revision | ||||||||||
Review Assigned To | ||||||||||||
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. | |||||||||||
Tags | No tags attached. | |||||||||||
Attached Files | ||||||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |
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 |
Copyright © 2000 - 2009 MantisBT Group |