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.

Severity 1

There are no widely impacting Severity 1 known errors in this patch


Severity 2

The following table lists notable Severity 2 known errors in this patch.

KB0598373PRB665890UI ComponentsWhen personalizing the Knowledge article form, unselecting (or hiding) the fields changes them to read-only
KB0598175PRB663869Server Side ScriptingEmailLogger is not available in global scope
KB0523209PRB583653Service Level Agreement (SLA)Workflows do not stop when the task SLA and the workflow context are domain separated
KB0549804PRB630133WorkflowIn list view, task.stage breaks UI rendering and throws a "jQuery is not defined" error when using UI11
KB0534771PRB580382EmailWhen HTML is added to the "incident event" business rule, the HTML is being escaped
KB0597848PRB632390Import / ExportThe sys_update_version table grows excessively due to XML-based imports
KB0529930PRB591140EmailViewing last two comments when using getJournalEntry to add a journal entry to a notification
KB0621950PRB732813Asynchronous Message BusAfter upgrading to Helsinki, HttpClient thread count grows on the MID Server
KB0536645PRB585971EmailEmail triggering twice for users that have the same email address with different upper/lower case addresses
KB0564063PRB590079UI ComponentsUI Macro/Formatter containing
breaks tabs on forms

Seen In

There is no data to report.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2019-05-21 11:37:44