[
https://issues.apache.org/jira/browse/OFBIZ-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372940#comment-15372940 ]
Michael Brohl commented on OFBIZ-7622:
--------------------------------------
The discussion about making this configurable comes from Pierre's suggestion:
{quote}
Isn't it much better to extend the ModelEntity in ModelEntity.java, with something like 'STAMP_FIELD' and such? And have that applied in GenericDAO.java?
Now it seems we have something implemented for a set of specific cases. But having a 'changeByUserLoginId on every entity makes sense.
{quote}
I then stated:
{quote}
That could be a problem at least in Germany, where it is a very sensitive subject because you could track when employees changed data and could monitor their working behaviour. I did not deeply think about it, just a short notice to think about before we implement such a feature.
{quote}
Maybe we should first decide *if* we want the "changeByUserLoginId" in every entity. If the answer is "yes", we may have to deal with configuration of some sort to switch it off.
> Add "changeByUserLoginId" field for CustRequestStatus
> -----------------------------------------------------
>
> Key: OFBIZ-7622
> URL:
https://issues.apache.org/jira/browse/OFBIZ-7622> Project: OFBiz
> Issue Type: Sub-task
> Components: ALL COMPONENTS
> Affects Versions: Trunk
> Reporter: Nameet Jain
> Assignee: Julien NICOLAS
> Attachments: OFBIZ-7622.patch, OFBIZ-7622.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
