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.
Custom Processor that includes 'type' as a parameter breaks report pages - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Custom Processor that includes 'type' as a parameter breaks report pages
KB0714797

Custom Processor that includes 'type' as a parameter breaks report pages


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

Description

Build information:
Jakarta Patch 8
glide-kingston-10-17-2017__patch6-05-16-2018

Issue Description:
Custom Processor with 'type' in parameter breaks report pages

Steps to Reproduce

On OOB instance

1. Navigate to System Definition > Processors.
2. Click New.
3. For Name, enter Test.
4. For Type, select script.
5. For Path, enter Test.
6. For Parameters, enter type

7. For Script, enter the following code.
var type = g_request.getParameter("type");
g_processor.writeOutput("text/plain","This will break report page. Type= "+type);

7. Click Submit.

8. goto Reports -> View / Run Clicking 'All' Reports are broken.

Expected behavior
Report pages should show with the new processor with type parameter
Actual behavior
Report page broken with the new processor with type parameter

See the attached screen recording for reference.

Workaround

After carefully considering the severity and frequency of the issue, and risk of attempting a fix, it has been decided to not address this issue in any current or future releases. We do not make this decision lightly, and we apologize for any inconvenience. If you have any questions regarding this problem, contact ServiceNow Customer Support.

 


Related Problem: PRB1293569

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.