[jira] [Commented] (OFBIZ-7781) Have a configurable solution with respect to the default fields of all entities

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (OFBIZ-7781) Have a configurable solution with respect to the default fields of all entities

Nicolas Malin (Jira)

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

Nicolas Malin commented on OFBIZ-7781:
--------------------------------------

+1, the advantage with track user on EntityStatus is the direct benefit to follow activity on sensible process. A good compromise between useful and resource.

Track all entities Oo sorry I can't believe it. A better way would be improve entity-audit-log engine, to enable it when you want at the fly and have a screen to analyse.

> 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)