Exception Object Has Undefined Properties In Case Of Catch(e)
(Doc ID 2060655.1)
Last updated on FEBRUARY 14, 2019
Applies to:Siebel CRM - Version 188.8.131.52.15 [IP2013] and later
Information in this document applies to any platform.
If an error is raised in a try-catch eScript structure, the errCode and errText properties of the exception object (e) are undefined.
Additional information has been to recreate the problem:
The error type that is generated is important too. Trying to access an unavailable/non existent object function/property errors work as expected, but errors in browser scripts show the described error behavior.
The attached browser script is executed in the simulator without properties. It's the same error as if it were to be started from an Applet.PreInvoke for WriteRecord.
The missing property e.errText can be replaced via e.message. But we couldn't find any details in the bookshelf regarding this, so we are not sure if this is some sort of undocumented functionality. If so, we are not allowed to use it.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document