BugZero | ServiceNow BugID PRB1632945 - In Polaris, Catalog item : "Propose a new Standard...

ServiceNow - Defect ID: PRB1632945

In Polaris, Catalog item : "Propose a new Standard Change Template" variable "sample change requests" has very same text field area

ServiceNow - Defect ID: PRB1632945

In Polaris, Catalog item : "Propose a new Standard Change Template" variable "sample change requests" has very same text field area

Last updated on August 16th, 2024

BugZero Risk Score
5.8 Medium

Overall: 5.8

Severity: 6.4

Community: 3.7

Lifecycle: 8.2

What is the BugZero Risk Score?

ServiceNow Integration

Learn more about where this data comes from

ServiceNow Integration

Learn more

Bug Scrub Advisor

Streamline upgrades with automated vendor bug scrubs

Bug Scrub Advisor

Learn more

BugZero Enterprise

Wish you caught this bug sooner? Get proactive today.

BugZero Enterprise

Learn more

Bug Details

Priority: Sev3
Article Views: 86
Affected Component: Cloud Management

Description

For the variable "More information" the length of the box has small text area in Polaris, which is not similar to UI 16 Steps to Reproduce 1. Hop to any OOB Sandiego, Tokyo instance 2. In UI 16, Open catalog item 'Propose a new Standard Change Template', click on 'Try it" 3. Observe the "Sample Change Requests" variable More information box is huge 4. Make polaris property glide.ui.polaris.experience to 'true' 5. Go to below link https://instancename.service-now.com/now/nav/ui/classic/params/target/com.glideapp.servicecatalog_cat_item_view.do%3Fv%3D1%26sysparm_id%3Dcb2a927f935002003b7a7a75e57ffb4c 6. You can observe for the variable 'sample change request' More information box is less Expected behaviour: In Polaris, The length of the box "More information" should be same as UI 16 Actual behaviour: The length of the box "More information" has small text area in Polaris, which is not similar to UI 16

Workaround

This problem has been fixed. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix

Related Problem

PRB1632945

Change history

2024-08-16 Added: Tokyo Patch 10 Hot Fix 1b, Tokyo Patch 4, Utah Patch 1, Utah Patch 1 Hot Fix 1, Utah Patch 1 Hot Fix 1a, Utah Patch 10b Hot Fix 1, Utah Patch 10b Hot Fix 2, Utah Patch 4, Utah Patch 7a, Utah Patch 9 Hot Fix 1, Vancouver Patch 10, Vancouver Patch 10 Hot Fix 2, Vancouver Patch 2 Hot Fix 1, Vancouver Patch 4, Vancouver Patch 4 Hot Fix 1b, Vancouver Patch 5, Vancouver Patch 6 Hot Fix 2, Vancouver Patch 7 Hot Fix 1, Vancouver Patch 7 Hot Fix 3b, Vancouver Patch 7 Hot Fix 4, Vancouver Patch 8, Vancouver Patch 8 Hot Fix 4, Vancouver Patch 9 Hot Fix 1, Vancouver Patch 9 Hot Fix 2, Vancouver Patch 9 Hot Fix 2a, Washington DC, Washington DC Patch 1, Washington DC Patch 1 Hot Fix 1, Washington DC Patch 1 Hot Fix 2a, Washington DC Patch 1 Hot Fix 3b, Washington DC Patch 2, Washington DC Patch 2 Hot Fix 2, Washington DC Patch 3, Washington DC Patch 3 Hot Fix 1, Washington DC Patch 3 Hot Fix 2, Washington DC Patch 4 Hot Fix 1, Washington DC Patch 4 Hot Fix 1a, Washington DC Patch 4 Hot Fix 2, Washington DC Patch 5, Washington DC Patch 5 Hot Fix 1, Washington DC Patch 5 Hot Fix 2, Washington DC Patch 6, Xanadu

Relevant Products

Click on a version to see all relevant bugs

Fixed versions: No known fixed versions

Relevant Products

Click on a version to see all relevant bugs

Fixed versions: No known fixed versions

Top ServiceNow Defects

9.4Defect ID: PRB1954123
Instance access issues due to Mutual TLS (mTLS) enablement on Zurich instances
8.5Defect ID: PRB1611377
CMDB Baseline creation job causing app node out of memory when a CI has a huge number of records referencing it
8.5Defect ID: PRB1788540
AWS Events Driven discovery is overloading Default Semaphores.
8.5Defect ID: PRB1871576
Data visualization can be accessed by anyone with URL to visualization designer
8.5Defect ID: PRB1928008
Upgrade to Yokohama releases can hang for Haraka enabled instance because of contention on kagami query registrar