Istanbul Patch 11c : Known Errors
This article presents notable known errors in Istanbul Patch 11c, grouped by severity and organized by category. Not all known errors appear on this page. Click the link in the Article column to view details about each known error. To view other families and versions, see the Known Error Portal.
Note: The severity level does not indicate the order in which issues will be fixed, which is determined by a combination of variables.
To view the release notes for this release family, see Istanbul Release Notes.
There are no widely impacting Severity 1 known errors in this patch
The following table lists notable Severity 2 known errors in this patch.
|KB0598373||PRB665890||UI Components||When personalizing the Knowledge article form, unselecting (or hiding) the fields changes them to read-only|
|KB0598175||PRB663869||Server Side Scripting||EmailLogger is not available in global scope|
|KB0523209||PRB583653||Service Level Agreement (SLA)||Workflows do not stop when the task SLA and the workflow context are domain separated|
|KB0549804||PRB630133||Workflow||In list view, task.stage breaks UI rendering and throws a "jQuery is not defined" error when using UI11|
|KB0534771||PRB580382||When HTML is added to the "incident event" business rule, the HTML is being escaped|
|KB0597848||PRB632390||Import / Export||The sys_update_version table grows excessively due to XML-based imports|
|KB0529930||PRB591140||Viewing last two comments when using getJournalEntry to add a journal entry to a notification|
|KB0621950||PRB732813||Asynchronous Message Bus||After upgrading to Helsinki, HttpClient thread count grows on the MID Server|
|KB0536645||PRB585971||Email triggering twice for users that have the same email address with different upper/lower case addresses|
|KB0564063||PRB590079||UI Components||UI Macro/Formatter containing |
Associated Community Threads
There is no data to report.