as long as you can control the sales person to put in only notes that don't effect the time or materials, I think this is fine. However my experience is that down the road the intent gets lost and notes the may effect the time and materials of a product run are introduced. so coming up with a structure that lets them put in variables that can be then interpretated by the code and change the Production run and costing would be a better approach.
yes it is a quicker setup to use notes but in the Dollars area to the user it is a non traceable expense. Jacopo Cappellato sent the following on 8/15/2008 11:00 AM: > I agree with you that storing them using the WorkEffortNote is the best > way. > > Jacopo > > On Aug 15, 2008, at 10:51 AM, Bilgin Ibryam wrote: > >> Hi fellows, >> >> I want add possibility for entering comments (production >> instructions/comments) for selected configurable product items when >> ordering from Order manager. >> In ProductConfigConfig entity (where the configurations are stored) >> there is already a description field, which I suppose is for this >> purpose. >> >> As this comments will be for the production run but not the order, I >> want to transfer these comments to production run tasks, but not sure >> where to put them. >> It is possible to have a comment for every selected option, so I think >> to go one of 2 ways: >> >> 1) create note for every comment and assign them to production run >> WorkEffort using WorkEffortNote entity. (I think to choose this option) >> or >> 2) extend WorkEffortGoodStandard entity with a description field and add >> the comments there. >> >> Anyone with better proposal or seeing a something wrong in this >> scenario? >> >> Thanks in advance. >> Bilgin Ibryam >> >
