[ 
https://issues.apache.org/jira/browse/OFBIZ-5440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13852966#comment-13852966
 ] 

Christian Carlow commented on OFBIZ-5440:
-----------------------------------------

Or instead, there needs to be a way to uniquely identify bomNodes with 
corresponding submittable quantity, price, and feature selection fields that 
can be passed to getBOMTree so that it can apply variant selection methods when 
building the tree.  Suffixing the submittable fields with the BOM item 
hierarchical index could be one method of unique identification.  So, using 
"_0" at the end of the field could indicate that it is the top node element 
while "_0_0" could be used to indicate the first element of the top node 
element.  If the first element of the top node element is a virtual element for 
which a variant has been selected then it could be indicated using something 
such as "_0_0.0" for he first variant and "_0_0.1" for the second variant.  
This would allow for separate tracking of childrenNodes for each variant.  
Meaning "0_0.0_0" and "0_0.1_0" could be used to associate separate feature 
selections for the first element of each of the variants of the first element 
of the top node.

> Improve BOM functionality to handle virtual BOM variant selection
> -----------------------------------------------------------------
>
>                 Key: OFBIZ-5440
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-5440
>             Project: OFBiz
>          Issue Type: Improvement
>    Affects Versions: SVN trunk
>            Reporter: Christian Carlow
>
> The BOM functionality should be improved to handle virtual product 
> variant/feature selections.  Such functionality would allow for something 
> such as GZ-OUTER-BASKET of selected features to contain 3 GZ-INNER-BASKETs of 
> different selected features
> I think the BOMNode class should contain a List<BOMNode>variantNodes member 
> to be used for virtual nodes in the loadChildren function.  When virtual 
> variants exist, the virtual node childrenNodes can be unset since the nodes 
> will be contained in the variantNodes instead.
> I disovered the need for such functionality while trying to implement 
> OFBIZ-5420 and OFBIZ-5437.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Reply via email to