When we need information on a known problem that is affecting customers or our own instances, we visit our extensive Known Error Knowledge Base, which is updated every day. These articles help identify issues that we are aware of and are either investigating, fixing, or offering a workaround solution. Since our latest upgrades are usually at the forefront of customer's minds, we make sure we have the latest information on them documented. Most of the known errors and issues in this list involve UI challenges in Fuji. If you see something that affects you, don't forget to subscribe to the Known Error and get real time updates as they are resolved.
Here are some of the top Known Error articles on Fuji User Interface issues that ServiceNow employees referenced in August:
Seen in: Fuji Patch 3, Fuji Patch 6, Fuji Patch 7 What happens: After upgrading to Fuji Patch 7, some instances are reporting slowness due to a defect that is repeatedly triggering a cache flush. Although this does not alter any data, the constant flush and rebuild of the cache is causing a significant load on the system. Workaround: If the instance was upgraded to an affected version, implementing this workaround brings relief until the instance can be upgraded to a patched version. To implement the workaround, set the Ignore Cache flag to truefor the evt_mgmt.last_calculated_alert_job property. This prevents the cache flush on updates to the property by the Event Management - create/resolved incident job...(click to view the rest of the workaround) |
Seen in: Fuji Patch 1, Fuji Patch 3, Fuji Patch 7 What Happens: Catalog UI pages lose their style when the instance is upgraded to Fuji. This is due to a change introduced in Fuji where the call to the CSS file is done within each page, rather than globally. If customers modify the UI page before upgrading, they won't get the latest change, so their pages won't render properly. Workaround: To overcome most of the CSS issues, each one of the customized pages must include lines to call the missing scripting files...(click to see the rest of the workaround) |
Issue: Users without the admin role are unable to create knowledge articles Seen in: Fuji Patch 6, Fuji Patch 7 What happens: When a knowledge admin (or anyone who should be able to create knowledge) attempts to use the Knowledge => Articles => Create new module, they are brought to a blank knowledge form and are unable to fill in any information and thus can't create articles. Workaround: Remove the condition from sys_security_acl_65bbd9bcd71221004792a1737e610389... (Click to see the rest of the workaround) |
Issue: CMS buttons disappear when entering text into multi-line variable Seen In: Fuji Patch 1, Fuji Patch 3, Fuji Patch 5, Fuji Patch 6 What happens: As you type new lines of text into the multi-line variable, it will push the Cancel and Submit buttons for the record producer within the iFrame. Workaround:If you are able to upgrade, review the Fixed Infield to determine the versions that have a permanent fix to this issue. You can also subscribe to this known error article (click Subscribebutton at the top of the article) to receive notifications when more information is available about this issue. |
Seen In: Fuji Patch 1, Fuji Patch 2, Fuji Patch 3 What happens: Reference fields made read-only through a UI Policy or a Client Script can still be edited using the lookup icon (magnifying glass). Workaround:Make the affected fields read-only through the ACL or make them read-only in the dictionary. |
