[
https://issues.apache.org/jira/browse/OFBIZ-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646040#action_12646040
]
David E. Jones commented on OFBIZ-2018:
---------------------------------------
Would that make the purpose of the field less clear?
What I mean is that if there is a "rate" field and a "rateUomId" it is clear
they go together, but if it was named something else then it would be hard to
tell by the names and would only be clear through documentation or something
(not that there shouldn't be documentation too, but it's nice to see patterns
according to how things are named).
> put currency currencyUomId field in the primary key of the RateType entity
> and add percentage field in the partyRate entity
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: OFBIZ-2018
> URL: https://issues.apache.org/jira/browse/OFBIZ-2018
> Project: OFBiz
> Issue Type: Improvement
> Components: specialpurpose/projectmgr, workeffort
> Affects Versions: SVN trunk
> Environment: any
> Reporter: Hans Bakker
> Assignee: Hans Bakker
> Priority: Minor
> Fix For: SVN trunk
>
>
> Proposed are 2 changes realting to a rate:
> 1. move the currencyUomId field in the primary key of the Ratetype table and
> change the reference to the PartyRate including the rateType and
> currencyUomId. This allows to specify a rateType in different currencies.
> 2. Add a percentage field to the partyRate entity to charge only a percentage
> of the actual time spend on the task. We have many employees in training and
> we want only a percentage of the time to be charged on the invoice.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
