I won't speak to this specific enhancement as I haven't explored work effort very much.
I think you'll find the least amount of frustration by using the <extend-entity> element in your entitymodel.xml for your enhancements instead of changing the entity definition in the OFBiz entitymodel.xml files. Couple that with the approach in http://ofbizwiki.go-integral.com/Wiki.jsp?page=FAQ21 and you should be able to keep your code separated entirely from the OFBiz codebase. Then if you want to contribute what you've done when it's all working for inclusion in the community project, you can either make the changes necessary and create a patch or simply offer your entire side project and let someone else reincorporate it into the codebase. This will keep you from relying on other people to review and commit your improvements before you can move your custom project forward. --- Jonathon -- Improov <[EMAIL PROTECTED]> wrote: > If the following has already been implemented, > please let me know. > > I need to attach long work instructions (like "knead > dough, dunk face in it briefly, claps hand > and turn 3 times") to Routing Tasks. I'm about to > add a new field to Routing Tasks (entity > WorkEffort with workEffortTypeId of ROU_TASK). The > addition will be to my own code branch in the > worst case, or in OFBiz SVN if my enhancement > suggestion is accepted. > > Can somebody check my understanding of such > additions? > > I understand that adding a new nullable field say > workInstructions of type "very-long" to entity > WorkEffort will not affect other applications, since > use of this field will be purely optional. > Upon restarting OFBiz instances, databases > (currently in use, production or test) will have the > > field added (via "alter table") and set to null, > which will not affect existing applications. Even > if I merge in future updates from OFBiz SVN, I'll > still not face incompatibility issues, as long > as those updates do not use my field > workInstructions. Or do not use in a way that's > incompatible > with the way I use it. > > It of course then follows that I should try to roll > this enhancement, including logics using field > workInstructions, into OFBiz SVN so that we're all > on the same page, and other users don't happen > to create a new field with same name and use that > field as say a "date-time" instead of a "very-long". > > Can somebody check my understanding above, before I > create a JIRA issue to be voted on? Thanks! > > Phew. Do I really have to be that detailed? I'd have > preferred to say "adding new field to > WorkEffort for long work instructions. OK?". Anyway, > I hope the above is clear enough, and > probably helps some newcomers catch on to some OFBiz > concepts too. Or at least assures some > veterans that I "can cross the road on my own, but > need help with the next steps after that"? > > Jonathon >
