Loading...
Loading...
In Zurich Patch 12 and Australia, workflow-type fields across forms, list views, and workspaces display incorrect values. Fields that should show the configured choice labels — for example "Approved", "In Review", or "Completed" — instead show "Pending - has not started" or "In progress" regardless of the actual value stored on the record. This affects custom workflow fields and any OOB workflow-type fields visible in workspace or UIB list views. The incorrect labels appear consistently across the instance for all users. Note: There are a few related issue: 1. Affected workspace lists (for example, Knowledge Center → Articles), the Workflow column displays "No workflow stages available" for every record [PRB2030898] a. The attached xml includes the fix for this issue 2. Affected workspace lists stage details pop up do not align with the shown stage details, all stages (including the active one) show "Pending - has not started" as the status label [PRB2058580]
Steps: 1. Open /kb_knowledge_list.do 2. Check the Workflow column 3. Notice the workflow shows "Pending - has not started' 4. Open the associated record and notice that the workflow state has a status (i.e. Draft/Review/Scheduled/etc)
Status should change at each stage
Status remains 'Pending - has not started' even after completion. 'Pending - has not started' is not even available as a choice option for status field, same with 'state' field as well.
Our recommendation is to upgrade to a fixed version, in that case Zurich Patch 13 and Australia Patch 5 or above. Please subscribe to this article to receive the latest updates. Meanwhile, if your instance has been impacted, the below workaround can be applied: 1. Navigate to All > Script Includes. 2. Import the xml attached to this KB article: DEF0822555_script_include.xml 3. Navigate to All > System Definitions > Scripts - Background and run: GlideCacheManager.prefixFlush('sys_choice_compiled', '<table>'); Replace <table> with the affected table. Important: This workaround modifies an out-of-box script include directly. Once your instance is upgraded to a release/patch line that includes this fix officially (Zurich Patch 13, Australia Patch 5 or later), revert this script include back to out-of-box. Otherwise the platform upgrade may treat it as a customization and skip re-applying the official version, which could cause you to miss later improvements to this same component.
PRB2009991
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.