BJ Freeman wrote: > > some thoughts > if you provide a way to change a process you must make sure it can not > be changed once it is used for Resource planning without feeding back > the change to the Resource planning component. > > cloning from a template or cloning to create a template is acceptable. > Cloning of data that is in two places creates a sync situation. > This trickles down to the BI component. >
Yep this is a real good point; we need to avoid data redundancy at all times in the operational database. I must confess that I am not very familiar with the resource planning in Ofbiz at all. What I have now in our project is a routing template that you can only assign specific resources to it the form of WorkEffortPartyAssignment. These relations (between WorkEffort and Party) were always cloned from the routing template (I made no change there). The implication is that the WorkEffort's resource could change during some parts of the ProductionRun lifecycle. In my mind this was during the "non-finished" states -- Created, Documents Printed, Running -- but not during Completed, Closed, Cancelled. How does the Ofbiz resource planning component fit in here? What I have now puts the onus on either the template task creator to assign the specific resources up front or on the user that is creating the Production Run (or printing docs / starting) to assign specific resources to the tasks before things get rolling. -- View this message in context: http://n4.nabble.com/Copying-WorkEffortCostCalc-as-part-of-a-ProductionRun-tp2016212p2016907.html Sent from the OFBiz - User mailing list archive at Nabble.com.
