Openbravo Issue Tracking System - Retail Modules | ||||||||||||
View Issue Details | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | |||||||
0055319 | Retail Modules | Web POS | public | 2024-04-12 12:01 | 2024-04-26 08:19 | |||||||
Reporter | jonae | |||||||||||
Assigned To | kousalya_r | |||||||||||
Priority | normal | Severity | minor | Reproducibility | have not tried | |||||||
Status | closed | Resolution | fixed | |||||||||
Platform | OS | 5 | OS Version | |||||||||
Product Version | ||||||||||||
Target Version | RR24Q2 | Fixed in Version | ||||||||||
Merge Request Status | approved | |||||||||||
Review Assigned To | ||||||||||||
OBNetwork customer | No | |||||||||||
Support ticket | ||||||||||||
Regression level | ||||||||||||
Regression date | ||||||||||||
Regression introduced in release | ||||||||||||
Regression introduced by commit | ||||||||||||
Triggers an Emergency Pack | No | |||||||||||
Summary | 0055319: Customer name and taxID are updatable in the customer collection data in PT | |||||||||||
Description | Within the PT localization, there is a validation for which some of the customer data cannot be updated as it must be key: If the customer file contains taxID, this taxID cannot be updated if for this customer any sale has been fiscalized. Which means, the taxID is the key data for this customer. If the customer file DOES NOT contain taxID, the customer name cannot be updated if for this customer any sale has been fiscalized. Currently, in the customer data collection popup, both the customer name and taxID can be updated. For Portugal this could be problematic. if will be possible for the seller to enter any data do not taken from the customer assigned to the sale, for those cases when such particular data is not available, for instance the address or the Tax ID of the customer. it will not be possible for the seller to change the “Name” and the “Tax ID” retrieved from the customer assigned to the sale, unless: there is a validation error of the PT Tax ID provided, so the correct one can be introduced by the seller (as we can not 100% trust the validity of the PT Tax ID provided) there is a valid “PT Tax ID” assigned to the customer, as that is the only use case where the name of a customer can be changed. | |||||||||||
Steps To Reproduce | - In a new ticket - Choose an existant customer - Pay it - The name and taxid are editable | |||||||||||
Proposed Solution | ||||||||||||
Additional Information | ||||||||||||
Tags | No tags attached. | |||||||||||
Relationships |
| |||||||||||
Attached Files | ||||||||||||
Issue History | ||||||||||||
Date Modified | Username | Field | Change | |||||||||
2024-04-25 13:43 | jonae | Type | defect => backport | |||||||||
2024-04-25 13:43 | jonae | Target Version | => RR24Q2 | |||||||||
2024-04-26 08:19 | hgbot | Resolution | open => fixed | |||||||||
2024-04-26 08:19 | hgbot | Status | scheduled => closed | |||||||||
2024-04-26 08:19 | hgbot | Note Added: 0163781 |
Notes | |||||
|
|||||
|
|