[
https://issues.apache.org/jira/browse/OFBIZ-10959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16827756#comment-16827756 ]
Mathieu Lirzin commented on OFBIZ-10959:
----------------------------------------
Hello Pawan,
The "include-internal" name has no obvious semantics attached to it, so some documentation explaining what it meant by "internal" and what is the effect of setting the attribute to {{true}} would help alot. Documentation should ideally be added in the {{xsd}} at the minimum.
Regarding the code you wrote, in the following snippet you can remove:
{code:java}
if ((modelField.getIsAutoCreatedInternal() && !autoFieldsEntity.includeInternal)) {
{code}
Thanks.
> Enable entity timestamp fields
> ------------------------------
>
> Key: OFBIZ-10959
> URL:
https://issues.apache.org/jira/browse/OFBIZ-10959> Project: OFBiz
> Issue Type: Improvement
> Components: framework/webtools
> Affects Versions: Trunk
> Reporter: Pawan Verma
> Assignee: Suraj Khurana
> Priority: Minor
> Attachments: OFBIZ-10959.patch, OFBIZ-10959.patch
>
>
> MarkMail link for the discussion: [
https://markmail.org/thread/x7paa3ulljns6awh]
>
> While working on a Production environment, I have found that for some reason entity timestamp fields are disabled at Search Results screen in Trunk and the previous release branch. It is available at View Value screen. It was enabled in Release 16.11.
>
> These fields are helpful for developers to get the idea about when the row in the entity is created/updated. Extremely helpful while working on the Production environment.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Locked
