it has been awhile and I am really tied up, so I would have to do what I
am going to explain to you.
the artifact, in webtools, is a good to see what interacts with an entity.
from that you can deduce the use.
also a code search for the entity for what the artifact may miss, since
Scott says the artifact does not cover everything.
[email protected] sent the following on 8/10/2010 11:51 AM:
Hi BJ,
Thank for your quick reply.
I understand that in OFBIZ we can use an "Appl" table to implement the
n:m relationship technically.
What I don't understand is the business level design of these two
relations: What's the purpose to associate a product feature category or
group to a product category? I haven't find anywhere can use these
relationships.
Thanks,
Miles
On Tue, 2010-08-10 at 11:10 -0700, BJ Freeman wrote:
*Appl is usually to have many to many relationships
miles sent the following on 8/10/2010 11:01 AM:
Hi,
I'm relative new to OFBIZ and has worked on it for several months. I've
understand the product feature applying to product to setup virtual/variant
products.
But what's the purpose of ProductFeatureCategoryAppl and
ProductFeatureCatGrpAppl design? I can associate a product feature category
or product feature group to product categories. But I can't find any effect
on doing this, either in documentation or by hand-on experiment. I may
missed something. Can any one explain the purpose of such operations?
Thanks,
Miles.
