AgileApps Support Wiki Pre Release

Difference between revisions of "History object"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
Line 32: Line 32:
|}
|}
(If multiple audited  fields were modified during a record update, there is one history entry per field.)
(If multiple audited  fields were modified during a record update, there is one history entry per field.)
|-
| Related To || related_to || <tt>{object_id}:{record_id}</tt>


|- <!-- SPACER ROW -->
|- <!-- SPACER ROW -->
| colspan="3" bgcolor="lightblue" style="height:6px" |
| colspan="3" bgcolor="lightblue" style="height:6px" |
|-
|-
| x || y || z
| || ||
|-
|  ||  ||
|-
|  ||  ||
|-
|  ||  ||
|-
|  ||  ||
|-
|  ||  ||  


|}
|}
===Standard Fields===
{{:Standard Field Parameters}}

Revision as of 23:45, 11 November 2014

The History object keeps track of activities related to a record. In the UI, history is shown below the record details.

Fields

Label Field name Notes
Category category Identifies the type of activity.
For example:
  • 2 - Updated this case*
  • 4 - Closed this case
  • 11 - Completed this task
  • 25 - Changed field value* (only applies to Audited Fields
  • 29 - Added a note.
  • 61 - Sent mail
*Category 25 is used when a case field is modified. Category 2 does not appear to be used.

For a complete list, see GearIcon.png > Customization > Global Picklists > History Category'

Description description

Varies, depending on the activity category.
For category 25 (audited field modified), the structure is:
{#structure-identifier^field-label^old-value^new-value^00005}

Example:

{#field_audit.recordname_modified_old_to_new
^#fieldlabel.c3a93f70aa004de6aeb5f9073eb1f759.subject
^Original case title
^Revised case title
^000005}

(If multiple audited fields were modified during a record update, there is one history entry per field.)

Related To related_to {object_id}:{record_id}

Standard Fields

Standard Field Parameters