[
https://issues.apache.org/jira/browse/OFBIZ-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15373667#comment-15373667 ]
Michael Brohl commented on OFBIZ-7781:
--------------------------------------
Thanks for your lengthy lecture about how to come to implementation decisions. You seem to imply that "we" meant only the contributors, which is not the case with my posting.
That said, I wonder if we really have strong *user* requirements for overall tracking fields and if yes, how many. Not sure if we have an "academic" discussion here.
The original issue was about user tracking of status changes and you brought up the idea of user tracking for all entities. It seemed to me that this requirement came out of the discussion and not from OFBiz adopters.
So, do we have a relevant user base who wants this feature?
> Have a configurable solution with respect to the default fields of all entities
> -------------------------------------------------------------------------------
>
> Key: OFBIZ-7781
> URL:
https://issues.apache.org/jira/browse/OFBIZ-7781> Project: OFBiz
> Issue Type: Improvement
> Components: datamodel
> Affects Versions: Trunk
> Reporter: Pierre Smits
>
> This issue follows up on comments posted in the OFBIZ-7622 sub-task.
> Currently the fields to be added to all entities are defined in ModelEntity.java. This is a limited list consisting of:
> * public static final String STAMP_FIELD = "lastUpdatedStamp";
> * public static final String STAMP_TX_FIELD = "lastUpdatedTxStamp";
> * public static final String CREATE_STAMP_FIELD = "createdStamp";
> * public static final String CREATE_STAMP_TX_FIELD = "createdTxStamp";
> After the implemented code change of the sub task mentioned above, a new discussion evolved through postings of comments on the subject of how to get more flexibility in.
> This issue is a starting point and potentially a place holder for sub subtasks to get to a more flexible solution.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
