Implement selling Handyman Sevices.

[Honey Goyal]

Hi,

I want to implement Handyman Services in ofbiz. My requirement is to get customer request for a Handyman. After that we will create Order and generate Bill for work done by a Handyman. For that purpose i have decide to use Products having productTypeId="SERVICE".

I want to know more about entities should be for saving customer request and then associate those request with Order.


Thanks,
Honey Goyal

[BJ Freeman-2]

hello,  i suggest you learn how to create the entities in the entity folder of the apps you want to use.by doing this on paper, so to speak, will give you a familiarity and a way to maintain your implementation in the future.that said you may want to go over the party associations as related to products as well
 


     On Wednesday, September 2, 2015 8:13 AM, Honey Goyal <[hidden email]> wrote:
   

 Hi,

I want to implement Handyman Services in ofbiz. My requirement is to get
customer request for a Handyman. After that we will create Order and
generate bill for work done by a Handyman. For that purpose i have decide to
use Products having productTypeId="SERVICE".

I want to know more about entities should be for customer request and then
associate those request with order.


Thanks,
Honey Goyal



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

[Honey Goyal]

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.

 

[Ashish Vijaywargiya-4]

Please go with CustRequest route. Requirement is specific to shortage in
goods and later on creating Purchase Order and then receiving the same in
the system.

--
Kind Regards
Ashish Vijaywargiya
HotWax Systems - est. 1997

On Thu, Sep 3, 2015 at 11:48 AM, Honey Goyal <[hidden email]> wrote:

> 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.
>

[BJ Freeman-2]

Before I jump in, what version are you using?
 


     On Wednesday, September 2, 2015 11:24 PM, Honey Goyal <[hidden email]> wrote:
   

 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.


   

[BJ Freeman-2]

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 <[hidden email]> wrote:
   

 Before I jump in, what version are you using?
 


    On Wednesday, September 2, 2015 11:24 PM, Honey Goyal <[hidden email]> wrote:
 

 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.


 

[Honey Goyal]

Yes, even i thought the same. I explored a bit, Requirement table is used when Product Stock reaches to ProductFacility.minimumStock.

[Honey Goyal]

I am using release13.07. yeah i will assign EMPLOYEE role to each Handyman.

[BJ Freeman-2]

employee is usually meant for those working for the product store, and/or business defined in accounting.what you have would be two types if customers, unless you plan to hire the handymen, and pay their wages, as employees.
 


     On Friday, September 4, 2015 7:09 AM, Honey Goyal <[hidden email]> wrote:
   

 I am using release13.07. yeah i will assign EMPLOYEE role to each Handyman.



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