Thanks all the quick responses and Anil for sharing the link it is very helpful, As i have to change most of the forms/screens to limit the fields, i will create a custom component in hot-deploy by extending the corresponding Ofbiz OOTB component and will keep my customization here.
Regards On Fri, Jun 20, 2014 at 11:00 AM, Jacques Le Roux < [email protected]> wrote: > This is good, you can even go further. > Most of the OFBiz parts can be overridden in a hot-deploy component. > This prevents you to have even to maintain patches... > > When you always try to apply this idea you really understand the genius > behind OFBiz... > > Jacques > > Le 20/06/2014 16:31, Anil Patel a écrit : > > Hi, >> As a general practice we don’t modify source files that comes with Apache >> OFBiz. In case we need to, the changes are maintained in patch file. >> >> Here is document on wiki that talks about customization in OFBiz. >> >> https://cwiki.apache.org/confluence/display/OFBIZ/Addressing+Custom+ >> Requirements+In+OFBiz >> >> In my experience, this is the right way to do it. >> >> Thanks and Regards >> Anil Patel >> COO >> Hotwax Media Inc >> http://www.hotwaxmedia.com/ >> ApacheCon US 2014 Silver Sponsor >> http://na.apachecon.com/sponsor/our-sponsors >> >> On Jun 20, 2014, at 10:18 AM, Integrin <[email protected]> wrote: >> >> Hi Ofbiz Users, >>> >>> I'm working on customizing ofbiz as a ERP solution and the requirement >>> comes to having less number fields in most of the screens than what comes >>> out of the box, this requires changes in .ftl files and Forms xml, in the >>> past i have been commenting out the fields that are not required or use >>> access privilege to limit the fields that are being displayed; however >>> this >>> requires merging all these changes when i will be upgrading to the new >>> version; please can you advise what is the best way to handle this, Any >>> pointers appreciated >>> >>> Regards >>> >> >> >> > -- >
