0027390: When deleting a value from a subset, the system does not delete (or deactivate) the value product is not removed or deactivated

Notes
(0079408) AtulOpenbravo (developer) 2015-08-18 13:38	Test Plan - Create product characteristics (mark it as variant). - Create two values for it in Value Tab. - Nagivate to Subset Tab and Create a new record. - Add two records in Subset values Tab by selecting earlier two values. - Create new product, mark it as Generic and add the above create characteristic and subset to it in Characteristics Tab. - Check in Configuration Tab, two values are added. - Now again go back to Product Characteristic window and add a new value in it. - Go in Subset value Tab and add a new record with above value. - Check in Product Window : Characteristic Tab : Configuration Tab: A record with new value is added to the product with Active = No. - Activate the above record. - Remove the above value from subset value tab of Product Characteristics window. - Check that record the deleted value is also removed from Product Window : Characteristic Tab : Configuration Tab.

(0079677) vmromanos (manager) 2015-08-25 10:04	Rejected after double checking with GDA. The current behavior is the right one. By default, when you enter a new Subset Value, the system automatically creates a Product Characteristic Configuration with active=N because the generic products already created don't need to have that new value. Only in the case you want to use it, the user must manually activate it in the required products. After that, if you delete (or deactivate) the subset value, the value won't be available for the new generic product to be created. However, you still want to use it in the products where you have manually activated it (that's why you have manually activated it, otherwise the record will continue to be deactivated). The proposed solution implies a change in the functional design that it's not required for the Product. That looks more like a customization or a misunderstanding in the way this functionality works. If you really need to have this functionality as a customization, please ping us and we will provide some code you can easily implement in a custom module through an EntityPersistenceEventObserver

Issue History
Date Modified	Username	Field	Change
2014-08-20 14:29	jonalegriaesarte	New Issue
2014-08-20 14:29	jonalegriaesarte	Assigned To	=> AtulOpenbravo
2014-08-20 14:29	jonalegriaesarte	Modules	=> Core
2014-08-20 14:29	jonalegriaesarte	Resolution time	=> 1411423200
2014-08-20 14:29	jonalegriaesarte	Triggers an Emergency Pack	=> No
2014-09-29 10:50	eduardo_Argal	Target Version	3.0PR14Q4 => 3.0PR15Q1
2014-12-22 17:59	Sandrahuguet	Target Version	3.0PR15Q1 => 3.0PR15Q2
2015-03-30 18:21	eduardo_Argal	Target Version	3.0PR15Q2 => 3.0PR15Q3
2015-04-14 12:48	Triage Finance	Assigned To	AtulOpenbravo => Triage Finance
2015-06-08 17:54	vmromanos	Target Version	3.0PR15Q3 =>
2015-08-04 12:27	egoitz	Resolution time	1411423200 => 1442700000
2015-08-04 12:27	egoitz	Issue Monitored: egoitz
2015-08-18 09:15	AtulOpenbravo	Assigned To	Triage Finance => AtulOpenbravo
2015-08-18 11:45	AtulOpenbravo	Status	new => scheduled
2015-08-18 13:38	AtulOpenbravo	Note Added: 0079408
2015-08-25 10:04	vmromanos	Review Assigned To	=> vmromanos
2015-08-25 10:04	vmromanos	Note Added: 0079677
2015-08-25 10:04	vmromanos	Status	scheduled => closed
2015-08-25 10:04	vmromanos	Resolution	open => invalid

Relationships [ Relation Graph ] [ Dependency Graph ]