Hi David, now i am on the content subject, i expect that a contentId will be connected to many more possible main entities so any incoming paper document can be scanned and connected to the related entity.
At the moment it is WorkEffort, party, order, partyResume, product, communication event, customer request, but it could also be connected to invoice, payment, agreement, budget, fixedAsset, productCatalog, productFacility, return, shipment, supplier, supplierProduct, tax entities, timesheet and more. Is it perhaps more flexible to have a more generalized entity such as: contentId, entityName, entityKey so we can connect any content to any entity? what are your thoughts on that? -- http://www.antwebsystems.com : Quality OFBiz support for competitive rates....
