Edit access for Communication Channel journal field on Incident

[dattanarend]

Hi Community,

I have created a journal input field on the Incident table called test Channel (field name: u_test_channel), similar to Work Notes and Additional Comments, and added it to the active view.

We now have a new requirement:

After a MIM Team member posts an entry in the test Channel field, they should be able to edit that entry if something was posted incorrectly — but only while the incident is in Active state.

Constraints:
• Edit access should be restricted to MIM Team members only
• Editing should only be allowed while the incident is Active (not Resolved or Closed)
• Ideally, the edit should happen in-place on the same Incident form
• We prefer NOT to create a custom table if possible

Challenge:
Since sys_journal_field entries are append-only by design, I am trying to figure out the best approach to allow edits without breaking the audit trail or creating a separate table.

Any guidance or real-world experience would be greatly appreciated!

Thanks

[Pavan Srivastav]

Hello,

The main challenge is that sys_journal_field is append-only in ServiceNow, preventing direct edits to maintain audit integrity. Instead of modifying entries, use a “Soft Edit via Correction Entry” pattern: strike through the original and append a corrected entry from an inline UI, preserving the audit trail and meeting business needs natively.

Implementation steps:

1. UI Policy: Display the Edit button only for MIM Team members on active incidents using System UI > UI Policies. The dynamic control is handled in the client script.

2. Client Script: Add an Edit button to each relevant entry, ensuring it appears only for MIM Team and active incidents. Clicking Edit opens a modal for corrections.

3. Correction Modal: The modal lets users enter the corrected text. On save, a GlideAjax call posts a correction entry, marking the original as corrected and logging an audit note in Work Notes.

4. Script Include: The server-side logic checks user roles and incident state, appends the correction and audit note, and ensures security.

5. ACL & Business Rule: Restrict write access to u_test_channel for MIM Team and block direct journal edits on inactive incidents.

Summary: MIM Team members can edit entries in the test channel on active incidents via an inline modal. Corrections are appended, original entries remain, and all actions are fully audited. This is accomplished using native ServiceNow features—no custom tables required.

[Tanushree Maiti]

Hi @dattanarend 

Allowing non-admin users to edit journal fields (like Work Notes or Additional Comments) in ServiceNow typically implies modifying security rules to allow updates to historical data, which is NOT Recommended to  grant broader write access on tasks.