How to include field changes in this activity available in form widget?

[ManikandanP7586]

In a Service Portal form, I added the Activity formatter for a specific view, and it correctly shows field changes (audit history) at the form level. However, in a custom widget where the widget-ticket-conversation is used, it only shows "Additional comments" and "Work notes".

How can I include field changes in the widget? Is there any out-of-the-box available that I can pass to the widget to enable this?

[Ankur Bawiskar]

@ManikandanP7586 

OOTB ticket conversations widget doesn't support showing activity log.

it only shows comments and work notes

Ticket conversation widget does not show all activity in Service Portal 

💡 If my response helped, please mark it as correct ✔️ and close the thread 🔒 — this helps future readers find the solution faster! 🙏

[Ankur Bawiskar]

@ManikandanP7586 

Thank you for marking my response as helpful.

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[nityabans27 · Accepted solution]

Hi @ManikandanP7586,

You’ve added the Activity Formatter in a Service Portal form and can see field change history there — but inside the widget-ticket-conversation, only Additional Comments and Work Notes appear.

Here’s why:

• The widget-ticket-conversation is designed to display journal fields only (like comments and work_notes).

• Field change history (audit data) is stored separately in the sys_audit table and isn’t fetched by this widget.

• There’s no OOB parameter or property you can pass to the widget to make it show field changes — this behavior is not configurable out-of-the-box.

✅ Options:

1. Clone the widget (widget-ticket-conversation) and extend its server script to:

   • Query sys_audit for the current record’s changes.

   • Merge that data with the widget’s conversation array for display.

2. Or embed the Activity Formatter directly in your portal form if you want both audit and comments in one place.

In short: field changes require custom extension — no OOB flag or parameter exists to include them in widget-ticket-conversation.

If you find my answer helpful then please accept it as solution and mark it helpful.