My Oracle Support Banner

IP2014 And IP2015 - Siebel Tools Debugger Issues (Doc ID 2104208.1) (Doc ID 2339217.1)

Last updated on SEPTEMBER 14, 2018

Applies to:

Siebel Tools - Version 16.9 [IP2016] and later
Information in this document applies to any platform.

Symptoms

Context: Siebel Tools Debugger

When debugging script, Siebel Tools stops at a specified breakpoints. When using 'Step Over' or 'Step In' to try to move through the code, Siebel Tools just flickers wildly for several seconds then fails to progress the code pointer. Sometime, pressing F8 / Step Over 5 or 6 times will progress to the next line but often this doesn't work either.

Changes

 1. Navigate and lock Contact BC
2. Open Server Script and choose eScript option
3. Select BusComp_PreGetFieldValue and enable pre-default code i.e.
function BusComp_PreGetFieldValue (FieldName, &FieldValue)
{
return (ContinueOperation);
}
4. Write below code in writerecord event:
function BusComp_WriteRecord ()
{
var BO : BusObject = TheApplication().GetBusObject("Account");
var BC : BusComp = BO.GetBusComp("Account");
BC.ClearToQuery();
BC.ExecuteQuery(ForwardOnly);
if(BC.FirstRecord())
{
var WshShell = COMCreateObject("WScript.Shell");
WshShell.Popup("Popup");
}
}
5. Compile changes and open webclient in debug mode.
6. Put break points on code written in write record.
7. In webclient navigate to Contact List View.
8. Select one record and save record.
9. Observer that execution stops at break point
10. Use F8 to debug, notice screen starts flicking and execution stays on the
same point.

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.