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.
Activated "Change Management - Standard Change Catalog" plugin and custom Change workflows broke - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Activated "Change Management - Standard Change Catalog" plugin and custom Change workflows broke
KB0715930

Activated "Change Management - Standard Change Catalog" plugin and custom Change workflows broke


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

Issue

Symptoms


  • After activating the "Change Management - Standard Change Catalog" plugin (com.snc.change_management.standard_change_catalog), custom Change workflows are no longer working as expected

Release


Jakarta Patch 9c

Cause


When the above plugin was activated, the "Change Management - Core" plugin was also activated, which added three new Change types to the user's system (other than their previously utilized custom types).

Now, there are identically named entries for two of the three Change types (two "Standard" and two "Normal" sys_choice records, all of which are active = true).

Resolution


After a thorough investigation, no issue was found with the design or functionality of the user's custom "Standard Change" workflow.

In fact, a workflow successfully attaches to a Change Request when either the non-current/non-OOB "Standard" Change type or the current OOB "Standard" Change type is used.

The only time an issue arises is when both "Standard" sys_choice Change types are active = true. This is the when the unexpected behavior is experienced.

When one or the other is deactivated, there is no issue. The user just needs to be sure that the desired active = true sys_choice Change type is the same as selected in the relevant Workflow's conditions.


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.