capeterson/visualforce-field-history

Force.com Visualforce component for showing field history on custom objects.

visualforce-field-history's Issues

No support for standard objects

A string replacement of __c for __History is done internally, which doesn't work properly for standard objects. If you need standard object support comment on this issue and I'll get around to fixing that.

Add special logic to show opportunities

Contacts are linked to opportunities by contact role objects, which don't have a label and aren't displayed.

We should add a special case so when these objects are seen a history event is added to the list,

Duplicate items if chatter and field history both tracked a change

If chatter tracking is enabled on the same field that field history is enabled on two entries will be shown in the timeline, one from chatter and one from field history tracking.

Created event is not shown

The "Created" event in the history table is not shown in this component.

Excessive SOQL use

The way SOQL queries are run - by iterating over the child objects and running a query for each - is very inefficient against governor limits, in particular the total number of SOQL queries.

The child object query functionality should be changed to run multiple subqueries for child objects rather than totally separate SOQL queries. This should cut the amount of resources and DB load down dramatically on complex objects with a large number of relationships.

Display should be (optionally) paginated

To make things more efficient we should really use standard set controllers to page the results, or use DateTime offsets in our queries. This should drop the viewstate use and increase speed dramatically on larger history lists.

Also while we're at it most of the component controller can probably become transient to speed things up as well.

Add an option to show lookup values as current name

Currently lookup and master detail fields usw the name of the related record at the time the field was edited, directly from the history table.

An option should be added to show record names as they exist at runtime, that is the current namw of the record instead of the name of the record at the time of the change.

Sent via Hubroid

Include chatter tracked changes

Currently fields tracked in chatter tracked changes aren't included. They should be.