BugZero | ServiceNow BugID PRB1561711 - Existing record for life_cycle

ServiceNow - Defect ID: PRB1561711

Existing record for life_cycle_mapping not loading values correctly on the form

ServiceNow - Defect ID: PRB1561711

Existing record for life_cycle_mapping not loading values correctly on the form

Last updated on April 7th, 2025

BugZero Risk Score
5.8 Medium

Overall: 5.8

Severity: 6.4

Community: 3.7

Lifecycle: 9.1

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: 599
Affected Component: Cloud Management

Description

Existing record for Life Cycle Mapping [life_cycle_mapping] is not loading values correctly on the form, such as the " legacy_field_value " field. Values are correctly displayed in the list [/life_cycle_mapping_list.do]. Steps to Reproduce 1. Go to /life_cycle_mapping_list.do 2. Edit any record Notice that the form does not load the values correctly for legacy field value.

Workaround

This problem is currently under review. You can contact ServiceNow Technical Support or subscribe to this Known Error article by clicking the Subscribe button at the top right of this article to be notified when more information becomes available.

Related Problem

PRB1561711

Change history

2025-04-07 Added: Rome Patch 1, Rome Patch 10 Hot Fix 2b, Rome Patch 10 Hot Fix 4b, Rome Patch 3, Rome Patch 7, Rome Patch 9a, Rome Patch 9b, San Diego Patch 1 Hot Fix 1, San Diego Patch 10, San Diego Patch 10 Hot Fix 1, San Diego Patch 10 Hot Fix 1a, San Diego Patch 10 Hot Fix 1b, San Diego Patch 10 Hot Fix 2b, San Diego Patch 3, San Diego Patch 7a, San Diego Patch 7b, San Diego Patch 9, San Diego Patch 9a, San Diego Patch 9b, Tokyo, Tokyo Patch 1, Tokyo Patch 1b, Tokyo Patch 3, Tokyo Patch 4a, Tokyo Patch 4b, Tokyo Patch 5, Tokyo Patch 6, Tokyo Patch 6 Hot Fix 1, Tokyo Patch 6 Hot Fix 2, Tokyo Patch 7, Tokyo Patch 7 Hot Fix 1, Tokyo Patch 7a, Tokyo Patch 7b, Tokyo Patch 8, Tokyo Patch 8 Hot Fix 1, Tokyo Patch 9, Tokyo Patch 9 Hot Fix 2, Tokyo Patch 9 Hot Fix 2a, Utah, Utah Patch 1, Utah Patch 1 Hot Fix 1, Utah Patch 1 Hot Fix 1a, Utah Patch 1 Hot Fix 1b, Utah Patch 2, Utah Patch 3, Utah Patch 3 Hot Fix 1, Utah Patch 4, Utah Patch 4 Hot Fix 2, Utah Patch 4 Hot Fix 2a, Utah Patch 4 Hot Fix 3, Utah Patch 5, Vancouver

Relevant Products

Click on a version to see all relevant bugs

Affected versions:Rome Patch 1, Rome Patch 10 Hot Fix 2b, Rome Patch 10 Hot Fix 4b, Rome Patch 3, Rome Patch 7, Rome Patch 9a, Rome Patch 9b, San Diego Patch 1 Hot Fix 1, San Diego Patch 10, San Diego Patch 10 Hot Fix 1, San Diego Patch 10 Hot Fix 1a, San Diego Patch 10 Hot Fix 1b, San Diego Patch 10 Hot Fix 2b, San Diego Patch 3, San Diego Patch 7a, San Diego Patch 7b, San Diego Patch 9, San Diego Patch 9a, San Diego Patch 9b, Tokyo, Tokyo Patch 1, Tokyo Patch 1b, Tokyo Patch 3, Tokyo Patch 4a, Tokyo Patch 4b, Tokyo Patch 5, Tokyo Patch 6, Tokyo Patch 6 Hot Fix 1, Tokyo Patch 6 Hot Fix 2, Tokyo Patch 7, Tokyo Patch 7 Hot Fix 1, Tokyo Patch 7a, Tokyo Patch 7b, Tokyo Patch 8, Tokyo Patch 8 Hot Fix 1, Tokyo Patch 9, Tokyo Patch 9 Hot Fix 2, Tokyo Patch 9 Hot Fix 2a, Utah, Utah Patch 1, Utah Patch 1 Hot Fix 1, Utah Patch 1 Hot Fix 1a, Utah Patch 1 Hot Fix 1b, Utah Patch 2, Utah Patch 3, Utah Patch 3 Hot Fix 1, Utah Patch 4, Utah Patch 4 Hot Fix 2, Utah Patch 4 Hot Fix 2a, Utah Patch 4 Hot Fix 3, Utah Patch 5, Vancouver

Fixed versions: No known fixed versions

Relevant Products

Click on a version to see all relevant bugs

Affected versions:Rome Patch 1, Rome Patch 10 Hot Fix 2b, Rome Patch 10 Hot Fix 4b, Rome Patch 3, Rome Patch 7, Rome Patch 9a, Rome Patch 9b, San Diego Patch 1 Hot Fix 1, San Diego Patch 10, San Diego Patch 10 Hot Fix 1, San Diego Patch 10 Hot Fix 1a, San Diego Patch 10 Hot Fix 1b, San Diego Patch 10 Hot Fix 2b, San Diego Patch 3, San Diego Patch 7a, San Diego Patch 7b, San Diego Patch 9, San Diego Patch 9a, San Diego Patch 9b, Tokyo, Tokyo Patch 1, Tokyo Patch 1b, Tokyo Patch 3, Tokyo Patch 4a, Tokyo Patch 4b, Tokyo Patch 5, Tokyo Patch 6, Tokyo Patch 6 Hot Fix 1, Tokyo Patch 6 Hot Fix 2, Tokyo Patch 7, Tokyo Patch 7 Hot Fix 1, Tokyo Patch 7a, Tokyo Patch 7b, Tokyo Patch 8, Tokyo Patch 8 Hot Fix 1, Tokyo Patch 9, Tokyo Patch 9 Hot Fix 2, Tokyo Patch 9 Hot Fix 2a, Utah, Utah Patch 1, Utah Patch 1 Hot Fix 1, Utah Patch 1 Hot Fix 1a, Utah Patch 1 Hot Fix 1b, Utah Patch 2, Utah Patch 3, Utah Patch 3 Hot Fix 1, Utah Patch 4, Utah Patch 4 Hot Fix 2, Utah Patch 4 Hot Fix 2a, Utah Patch 4 Hot Fix 3, Utah Patch 5, Vancouver

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