soujanyaR
ServiceNow Employee

Problem

When working with a custom table that extends the Task table, you may notice that field value changes (for example, changing the State from Work in Progress to Pending) are reflected correctly on the form but are not displayed in the Activity Stream.

Instead, the Activity Stream continues to display the previous field value, making it appear as though the update was never recorded.

Example: The form shows the State as "Work in progress," while the Activity Stream still displays "Open."

 

Screenshot 2026-07-09 at 4.24.37 PM.png

 

 

 

 

 

 

 

 

 

Root Cause

This behavior occurs because the Audit property is disabled (false) for the custom table's dictionary entry. (Attached image)

The Activity Stream relies on audit history to display field value changes. When auditing is disabled, field updates are not written to the audit tables, so those changes cannot be displayed in the Activity Stream.

 

Screenshot 2026-07-09 at 4.28.19 PM.png

 

 

Solution

 

To enable field change tracking:

  1. Navigate to System Definition > Dictionary.
  2. Open the Dictionary list.
  3. Click the List Layout (gear) icon and add the Audit column for easier visibility.
  4. Search for the dictionary record where:
    • Type = Collection
    • Name = Your custom table
  5. Verify that the Audit field is currently set to False.
  6. Open the record and change "Audit" to "True."
  7. Save the record.

Result

After enabling the Audit property, all subsequent field changes will be audited and displayed in the Activity Stream. (Attached image)

Note: Enabling auditing does not populate historical changes. Only changes made after the Audit property is enabled will appear in the Activity Stream.

Screenshot 2026-07-09 at 4.30.39 PM.png

 

Additional Information

  • This behavior is commonly observed with custom tables that extend the Task table.
  • Enabling auditing allows the platform to record field value changes in the audit history, which is then used by the Activity Stream.
  • Consider the storage implications before enabling auditing on tables with a high volume of updates.

 

 

 

 

Version history
Last update:
3 hours ago
Updated by: