[
https://issues.apache.org/jira/browse/OFBIZ-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15356286#comment-15356286
]
Nameet Jain edited comment on OFBIZ-7611 at 6/30/16 2:59 AM:
-------------------------------------------------------------
Hi [~utcb],
You are right "enable-audit-log" is also a candidate used for tracking. If we
set "enable-audit-log" on the field to true, it will create a record in entity
"EntityAuditLog" from where we track which entity or field was changed, what
was the previous value, what is the updated value, who changed it, when it was
changed and so on.
What I understand about using "enable-audit-log" setting majorly with entity
fields whose data is very crucial and sensitive. Also,
- Using "enable-audit-log" adds overhead and performance degradation.
- When we want to show status history (same as Order status history shown on
order overview screen) on respective overview screen using "EntityAuditLog" is
an additional work to do.
- By the time when data will grow fetching details from this entity will also
be a heavy job for the system.
I think that's the reason why we have "changeByUserLogin",
"lastModifiedByUserLogin" and such other field on multiple entities, to show
information to the user.
was (Author: nj):
Hi [~utcb],
You are right "enable-audit-log" is also a candidate used for tracking. If we
set "enable-audit-log" on the field to true, it will create a record in entity
"EntityAuditLog" from where we track which entity or field was changed, what
was the previous value, what is the updated value, who changed it, when it was
changed and so on.
What I understand about using this setting majorly with entity fields whose
data is very crucial and sensitive. Also,
- Using "enable-audit-log" adds overhead and performance degradation.
- When we want to show status history (same as Order history shown on
orderview screen) on respective overview screen using "EntityAuditLog" is an
additional work to do.
- By the time when data will grow fetching details from this entity will also
be a heavy job for the system.
I think that's the reason why we have "changeByUserLogin",
"lastModifiedByUserLogin" and such other field on multiple entities to show
information to user.
> Track userlogin for status change
> ---------------------------------
>
> Key: OFBIZ-7611
> URL: https://issues.apache.org/jira/browse/OFBIZ-7611
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL COMPONENTS
> Affects Versions: Trunk
> Reporter: Nameet Jain
> Assignee: Nicolas Malin
>
> Currently in OFBiz, 'changedByUserLoginId' field is missing from status
> entities (like: ShipmentStatus). Using this field we can maintain the history
> for each status change made by user.
> Update all respective service and events to ensure this field gets updated.
> Here is the list of entities with missing this field.
> 1. BudgetStatus
> 2. ContactListCommStatus
> 3. CustRequestStatus
> 4. ExampleStatus
> 5. FinAccountStatus
> 6. InventoryItemStatus
> 7. InvoiceStatus
> 8. PartyStatus
> 9. RequirementStatus
> 10. ShipmentStatus
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
