ofbiz-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From BJ Freeman <bjfr33...@yahoo.com.INVALID>
Subject Re: Implement selling Handyman Sevices.
Date Thu, 03 Sep 2015 21:25:10 GMT
First, there are less supplicatedsolutions, however I from experience, I choose the more complexsolutions.The
core of this solution, usesAgreementhttp://demo-stable-ofbiz.apache.org/webtools/control/ArtifactInfo?type=entity&uniqueId=Agreement
and PartyRelationshipAndDetail http://demo-stable-ofbiz.apache.org/webtools/control/ArtifactInfo?type=entity&uniqueId=PartyRelationshipAndDetail
as you see the second one has noservices , forms, screens, so this is where you would have
to add.
These would be used when a party ofeither type signs up.You can start with one genericagreements
for each type, something like how they would use the site.Then you can add agreements for
eachtype of handyman, this way there is no misunderstanding 
hope that is enough to get started, orjust leave it out. 

     On Thursday, September 3, 2015 10:51 AM, BJ Freeman <bjfr33man@yahoo.com.INVALID>

 Before I jump in, what version are you using?

    On Wednesday, September 2, 2015 11:24 PM, Honey Goyal <er.honey2012@gmail.com>

 Thankyou BJ. Yes, i know about creating new entities. My concern is to use
existing entity model in ofbiz. I have seen Requirement entity and
CustRequest entity. i think both entities can be used to save Customer
Request for a Handyman. But i am not sure.

In Requirement entity, requirementTypeId can be WORK_REQUIREMENT,
CUSTOMER_REQUIREMENT and OrderRequirementCommitment entity can be used for
Order/CustomerRequest association.

Want a expert advise, should i go for these table or is there any other
tables exist in ofbiz. Or should i create my own tables.


View this message in context: http://ofbiz.135035.n4.nabble.com/Implement-selling-Handyman-Sevices-tp4671815p4671820.html
Sent from the OFBiz - User mailing list archive at Nabble.com.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message