Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0049195Retail ModulesDiscounts and Promotionspublic2022-05-03 14:472022-06-10 09:05
Reporterrfacon 
Assigned Toradhakrishnan 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned Tomarvintm
OBNetwork customer
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0049195: Availability subtab records can be deleted
DescriptionAvailability subtab records can be deleted
Steps To Reproduce1. Configure a discount in the Backend, for example:
- Discount/Promotion Type: Price adjustment
- Active = Y
- Define the discount for a product

2. Availability subtab : add a new record by indicating a day

3. Delete the record created at step 2 by selecting it and clicking on the bin icon (or by doing a right click + delete)

Result : even if the record is deleted in the BO, it remains active in the POS masterdatas.

To avoid this issue, we shouldn't be able to delete records of the availibility subtab, but only to put them as inactive in case they are not used
Proposed Solution
Additional Information
TagsNOR
Relationships
related to defect 0049194 closed radhakrishnan Discount availability should be validated with POS time instead of server time 
related to feature request 0048383pi closed jetxarri Allow to activate promotions on 2 distinct time slots within the same day 
related to defect 0049204 closed ranjith_qualiantech_com Modifying the Availibility subtab doesn't update the discount audit section 
related to defect 0049517 closed radhakrishnan API call - Availability of a promotion is calculated on universal time by the API 
related to defect 0049518 closed radhakrishnan API call - A promotion with an availability set on the last hours of a day is also applied on the last hours of the day before 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2022-05-03 14:47rfaconNew Issue
2022-05-03 14:47rfaconAssigned To => Retail
2022-05-03 14:47rfaconTriggers an Emergency Pack => No
2022-05-04 10:28rafarodaTag Attached: NOR
2022-05-04 10:28rafarodaRelationship addedrelated to 0049204
2022-05-04 10:28rafarodaRelationship addedrelated to 0049194
2022-05-04 10:29rafarodaRelationship addedrelated to 0048383
2022-05-04 10:30rafarodaTypebackport => defect
2022-06-07 21:44rafarodaIssue Monitored: rafaroda
2022-06-08 16:09radhakrishnanAssigned ToRetail => radhakrishnan
2022-06-09 15:20radhakrishnanStatusnew => scheduled
2022-06-09 23:44rafarodaRelationship addedrelated to 0049517
2022-06-09 23:44rafarodaRelationship addedrelated to 0049518
2022-06-10 09:05marvintmReview Assigned To => marvintm
2022-06-10 09:05marvintmNote Added: 0138238
2022-06-10 09:05marvintmStatusscheduled => closed
2022-06-10 09:05marvintmResolutionopen => no change required

Notes
(0138238)
marvintm   
2022-06-10 09:05   
Disallowing deletions in this tab would be inconsistent with the rest of the masterdata tables, where we do allow deletions, so we think this is not the right approach. It would be very confusing to not allow deletions here, and allow them in the rest of the discounts filters for example.