Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Resolution note repeated twice in activity stream of incident form - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Resolution note repeated twice in activity stream of incident form
KB0744256

Resolution note repeated twice in activity stream of incident form


2013 Views Last updated : Aug 24, 2022 public Copy Permalink
KB Summary by Now Assist

Issue

Symptoms

When the incident is resolved, user prompted to enter "Resolution Notes". This entered "Resolution Notes" was appearing twice on the activity stream of the incident form as shown in the below screenshot,

Release

Any supported release.

Cause

There was an after update Business Rule which was set up on the Incident table and it had current.update() statement, due to this, when the incident form is saved after entering resolution code, system fired the second update with same values.

Thus the "Resolution Notes" was updated 2 times and it was eventually these 2 updates were audited.

Hence, the activity stream was showing the "Resolution Notes" twice as there are 2 audits for it. 

Resolution

  • In general, it is highly not recommendable to use current.update in the business rule. Also, the after update business rule is usually used to update other relevant records, not the current record.
  • Please review the after update Business Rule which has current.update() statement and modify it.
  • If modifying business rule is not an easy option, then you can consider updating the script to include the setworkflow(false) statement so that the audit would not be triggered with the second update. 

Additional Information

How business Rules work

Never use current.update on Business Rule


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.