Understanding Product Store attributes

[Bob Morley]

I have done a little hunting for this in the docs - I apologize if I have missed this somewhere - but I appear to be spending a lot of time trying to figure out which each option that can be set on a ProductStore "does".  Some of them are obvious, but things like "Set Owner Upon Issuance" is not entirely clear until I do some analysis and see how the service(s) make use of it.

Question #1 - Is there documentation out there that I am missing?

Question #2 - If there is not; can someone tell me an effective way to determine how something like where "title" is used?  Simple searching across the code base returns too many hits ... I am trying to answer the standard question most customers would ask when determining what value to put in the field (that is where will it be displayed?).

[David E. Jones-2]

On Jul 7, 2009, at 8:21 PM, Bob Morley wrote:

>
> I have done a little hunting for this in the docs - I apologize if I  
> have
> missed this somewhere - but I appear to be spending a lot of time  
> trying to
> figure out which each option that can be set on a ProductStore  
> "does".  Some
> of them are obvious, but things like "Set Owner Upon Issuance" is not
> entirely clear until I do some analysis and see how the service(s)  
> make use
> of it.
>
> Question #1 - Is there documentation out there that I am missing?

The only "documentation" I'm aware of is in the field descriptions  
that are in the ProductStore entity definition. Most of the newer  
fields do have some content about them.

You can see these in the entitymodel.xml file or in the WebTools  
Entity Reference.

> Question #2 - If there is not; can someone tell me an effective way to
> determine how something like where "title" is used?  Simple  
> searching across
> the code base returns too many hits ... I am trying to answer the  
> standard
> question most customers would ask when determining what value to put  
> in the
> field (that is where will it be displayed?).

Yeah, searching around for specific fields can be a pain. For many of  
the ProductStore configuration fields they aren't referred to in very  
many places, but some of them are a bit crazy.

Either way, it's not the ideal form of documentation and it would be  
great to have descriptions for all of the fields.

-David

[Ruth Hoffman-2]

Hi Bob, David:
I'm in the process of writing a book about OFBiz ecommerce & the Catalog
Manager. Some of what you are looking for is in a draft copy of what I'm
putting together. If you'd like a copy of this draft, I'd be happy to
send it to you. Please contact me at: [hidden email]

Regards,
Ruth Hoffman
David E Jones wrote:

>
> On Jul 7, 2009, at 8:21 PM, Bob Morley wrote:
>
>>
>> I have done a little hunting for this in the docs - I apologize if I
>> have
>> missed this somewhere - but I appear to be spending a lot of time
>> trying to
>> figure out which each option that can be set on a ProductStore
>> "does".  Some
>> of them are obvious, but things like "Set Owner Upon Issuance" is not
>> entirely clear until I do some analysis and see how the service(s)
>> make use
>> of it.
>>
>> Question #1 - Is there documentation out there that I am missing?
>
> The only "documentation" I'm aware of is in the field descriptions
> that are in the ProductStore entity definition. Most of the newer
> fields do have some content about them.
>
> You can see these in the entitymodel.xml file or in the WebTools
> Entity Reference.
>
>> Question #2 - If there is not; can someone tell me an effective way to
>> determine how something like where "title" is used?  Simple searching
>> across
>> the code base returns too many hits ... I am trying to answer the
>> standard
>> question most customers would ask when determining what value to put
>> in the
>> field (that is where will it be displayed?).
>
> Yeah, searching around for specific fields can be a pain. For many of
> the ProductStore configuration fields they aren't referred to in very
> many places, but some of them are a bit crazy.
>
> Either way, it's not the ideal form of documentation and it would be
> great to have descriptions for all of the fields.
>
> -David
>
>