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.
Dirty form dialog does not appear when using current.setAbortAction(true) in business rule - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Dirty form dialog does not appear when using current.setAbortAction(true) in business rule
KB0594804

Dirty form dialog does not appear when using current.setAbortAction(true) in business rule


2167 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Description

Dirty form dialog box does not appear using current.setAbortAction(true) in business rule, even though glide.ui.dirty_form_support property is set to true.

Steps to Reproduce 

  1. Create a before business rule on the incident table using current.setAbortAction(true) in the script field.
  2. On the business rule:
    • select the Update action
    • set the order to 100
  3. Navigate to the Incident form
  4. Add text to the Comments field.
  5. Add text to the Short Description field.
  6. Click Save.
    On submit an Invalid update error appears. Also, note that the default css property green color for the change fields is no longer there.
  7. Click Reload Form.
    The instance does not display the dirty form dialog box to alert user before discarding the values. The text values previously entered in comments and short description fields have disappeared on load.

After step 6, verify the form value using g_form.getValue('short_description') to display the modified value. The modified value is saved to the UI form. On load, the instance does not prompt the user to save un-saved changes.

Workaround

There is no known workaround for this issue. If you are able to upgrade, review the Fixed In field below to determine the versions that have a permanent fix. You can also subscribe to this known error article (click Subscribe button at the top of the article) to receive notifications when more information is available about this issue.


Related Problem: PRB584991

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.