Hi All
I'm hoping for some input on the best way to implement custom screens/forms for different product types. I'm thinking I can either: 1. Use ProductAttributes to define what screens should be used for various products 2. Create child ProductTypes and present screens based on that. If I go this way I'm thinking I would need to change all the code that uses ProductTypes for processing so that they call something like: if (ProductServices.isParentProductType(productType, "FINISHED_GOOD")) { Then process as a finished good Any thoughts or other options? Thanks Scott |
Do you mean custom screens in the catalog manger, or in ecommerce? If you're looking for it in ecommerce there is already a feature built- in to allow you to override the default screen (which is "productdetail"). See the EditProduct->Content tab for more info. -David On Oct 17, 2006, at 7:39 AM, Scott Gray wrote: > Hi All > > I'm hoping for some input on the best way to implement custom > screens/forms for different product types. I'm thinking I can either: > 1. Use ProductAttributes to define what screens should be used for > various products > 2. Create child ProductTypes and present screens based on that. If > I go this way I'm thinking I would need to change all the code that > uses ProductTypes for processing so that they call something like: > if (ProductServices.isParentProductType(productType, > "FINISHED_GOOD")) { Then process as a finished good > > Any thoughts or other options? > > Thanks > Scott |
Sorry, I meant the catalog manager
Thanks Scott David E Jones wrote: > > Do you mean custom screens in the catalog manger, or in ecommerce? If > you're looking for it in ecommerce there is already a feature built-in > to allow you to override the default screen (which is > "productdetail"). See the EditProduct->Content tab for more info. > > -David > > > On Oct 17, 2006, at 7:39 AM, Scott Gray wrote: > >> Hi All >> >> I'm hoping for some input on the best way to implement custom >> screens/forms for different product types. I'm thinking I can either: >> 1. Use ProductAttributes to define what screens should be used for >> various products >> 2. Create child ProductTypes and present screens based on that. If I >> go this way I'm thinking I would need to change all the code that >> uses ProductTypes for processing so that they call something like: >> if (ProductServices.isParentProductType(productType, >> "FINISHED_GOOD")) { Then process as a finished good >> >> Any thoughts or other options? >> >> Thanks >> Scott > > |
I got this from the General Entity Overview document:
EntityType is used to describe an Entity. A given EntityType can inherit features from a parent EntityType if one is specified in the parentTypeId field of a given EntityType instance. So perhaps I should create a subType of FINISHED_GOOD and use something like the method I mentioned below to retain it's functionality in other areas? Regards Scott On 18/10/06, Scott Gray <[hidden email]> wrote: > > Sorry, I meant the catalog manager > > Thanks > Scott > > David E Jones wrote: > > > > Do you mean custom screens in the catalog manger, or in ecommerce? If > > you're looking for it in ecommerce there is already a feature built-in > > to allow you to override the default screen (which is > > "productdetail"). See the EditProduct->Content tab for more info. > > > > -David > > > > > > On Oct 17, 2006, at 7:39 AM, Scott Gray wrote: > > > >> Hi All > >> > >> I'm hoping for some input on the best way to implement custom > >> screens/forms for different product types. I'm thinking I can either: > >> 1. Use ProductAttributes to define what screens should be used for > >> various products > >> 2. Create child ProductTypes and present screens based on that. If I > >> go this way I'm thinking I would need to change all the code that > >> uses ProductTypes for processing so that they call something like: > >> if (ProductServices.isParentProductType(productType, > >> "FINISHED_GOOD")) { Then process as a finished good > >> > >> Any thoughts or other options? > >> > >> Thanks > >> Scott > > > > > > |
The data model is designed to support this sort of things (was from the beginning, way back in 2001). The problem is that there are very few parts of the code that support this. In fact I think the only service that exists for this is one for PartyType stuff (if I remember right). Anyway, it could certainly be done. To get an idea of the number of touch points just search for "FINISHED_GOOD". All code in OFBiz _should_ refer directly to IDs like this, so it should result in a pretty good list. -David On Oct 20, 2006, at 1:05 PM, Scott Gray wrote: > I got this from the General Entity Overview document: > EntityType is used to describe an Entity. A given EntityType can > inherit > features from a parent EntityType if one is specified in the > parentTypeId > field of a given EntityType instance. > > So perhaps I should create a subType of FINISHED_GOOD and use > something like > the method I mentioned below to retain it's functionality in other > areas? > > Regards > Scott > > On 18/10/06, Scott Gray <[hidden email]> wrote: >> >> Sorry, I meant the catalog manager >> >> Thanks >> Scott >> >> David E Jones wrote: >> > >> > Do you mean custom screens in the catalog manger, or in >> ecommerce? If >> > you're looking for it in ecommerce there is already a feature >> built-in >> > to allow you to override the default screen (which is >> > "productdetail"). See the EditProduct->Content tab for more info. >> > >> > -David >> > >> > >> > On Oct 17, 2006, at 7:39 AM, Scott Gray wrote: >> > >> >> Hi All >> >> >> >> I'm hoping for some input on the best way to implement custom >> >> screens/forms for different product types. I'm thinking I can >> either: >> >> 1. Use ProductAttributes to define what screens should be used for >> >> various products >> >> 2. Create child ProductTypes and present screens based on >> that. If I >> >> go this way I'm thinking I would need to change all the code that >> >> uses ProductTypes for processing so that they call something like: >> >> if (ProductServices.isParentProductType(productType, >> >> "FINISHED_GOOD")) { Then process as a finished good >> >> >> >> Any thoughts or other options? >> >> >> >> Thanks >> >> Scott >> > >> > >> >> |
Free forum by Nabble | Edit this page |