Openbravo Issue Tracking System - POS2 | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0053092 | POS2 | POS | public | 2023-07-27 14:42 | 2024-03-04 11:20 |
| Reporter | justin_patterson | ||||
| Assigned To | Retail | ||||
| Priority | high | Severity | major | Reproducibility | have not tried |
| Status | closed | Resolution | duplicate | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| Merge Request Status | |||||
| 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 | 0053092: RM-6867 BUT_Promo_New Request_Change property Product is candidate for external discount | ||||
| Description | BUT needs to be able to configure the property “Candidate for external promotion” with different values (Y or N) depending on the store. Currently, it’s only possible to set up this field in the Product screen in a unique way for any store that is configured using the External Discount engine. The business need behind this requirement is that Maxxing has no access to the BUT central ERP (Nossica) and to the BUT store ERP (Nossica store). Depending on the price & business parameters set up in BUT Nossica, BUT will be able to update Webpos (through EDL Price) for which combination of store/product need to have this parameter set up with Yes, and for which other combination of different store, but same product, they need to set up the field with No. Based on this need, BUT will be able to send to Maxxing the right business criteria so that Maxxing can apply or not a discount. Impact of this business need The objective of this functional specifications is to analyze and describe all the requirements related to the refactor of moving the field “Candidate for External Promotions” field from the “Product” screen to the Product Price tab, inside the Price List Version / Price List screen or the Assortment screen | ||||
| Steps To Reproduce | . | ||||
| Proposed Solution | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2023-07-27 14:42 | justin_patterson | New Issue | |||
| 2023-07-27 14:42 | justin_patterson | Assigned To | => Retail | ||
| 2023-07-27 14:42 | justin_patterson | OBNetwork customer | => No | ||
| 2023-07-27 14:42 | justin_patterson | Triggers an Emergency Pack | => No | ||
| 2023-07-27 14:51 | justin_patterson | Type | feature request => defect | ||
| 2023-07-27 15:05 | justin_patterson | Note Added: 0152949 | |||
| 2024-03-04 11:20 | jorgewederago | Note Added: 0161597 | |||
| 2024-03-04 11:20 | jorgewederago | Status | new => closed | ||
| 2024-03-04 11:20 | jorgewederago | Resolution | open => duplicate | ||
| Notes | |||||
|
|
|||||
|
|
||||
|
|
|||||
|
|
||||