[ 
https://issues.apache.org/jira/browse/OFBIZ-5985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215962#comment-15215962
 ] 

Swapnil Shah edited comment on OFBIZ-5985 at 3/29/16 1:16 PM:
--------------------------------------------------------------

Thanks [~jacopoc] Asset classes can surely be better managed by leveraging upon 
FixedAssetType.parentTypeId. As far as resource assignment based on asset 
classification is concerned i was not too sure if it needs to be automated by 
system based on common class or can we still leave it up to planners that needs 
to be taken care as part of initial setup process essentially to support the 
cases where planners can choose to associate alternate resource from a 
different class as well. So would have liked to here more views on it.


was (Author: swash78):
Thanks [~jacopoc] Asset classes can surely be better managed by leveraging upon 
FixedAssetType.parentTypeId. As far as resource assignment based on asset 
classification is concerned i am not too sure if it needs to be automated by 
system based on common class or can we still leave it up to planners that needs 
to be taken care as part of initial setup process essentially to support the 
cases where planners can choose to associate alternate resource from a 
different class as well.

> Support routing task standard quantity tracking of fixed assets
> ---------------------------------------------------------------
>
>                 Key: OFBIZ-5985
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-5985
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: workeffort
>    Affects Versions: Trunk
>            Reporter: Christian Carlow
>
>  I need the ability to assign track the standard quantity that can be run by 
> fixed assets for a routing task.  WorkEffortFixedAssetStd contains a 
> fixedAssetTypeId instead of fixedAssetId  I've found no code using the entity 
> other than the one that allows the entity data to be manipulated.  Therefore, 
> to prevent adding another entity to the model, would replacing 
> fixedAssetTypeId with fixedAssetId be a worthy solution?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to