At the moment i am looking to create a customer service component. The usage of the custRequest entity in this case never will need custRequestItem's
The long description field called 'story' is however only available in the custRequestItem and not on the header. In order to simplify the implementation i would like to have the story field also on the header in order not to have to use a 'dummy' custRequestItem to use the story field. Any objections? -- Ofbiz on twitter: http://twitter.com/apache_ofbiz Myself on twitter: http://twitter.com/hansbak Antwebsystems.com: Quality services for competitive rates.
