Debug OScript code with Builder

We have a workflow with one associated event script. Unfortunately, we can't make Content Server Builder debug the script, despite the use of scheduler.debugbreak(). The problem is specific to an instance, we confirm a bunch of others and all went well.The error message in log is "error finishing step", quite vague...

Thanks for all

Find more posts tagged with

Comments

appuGmail

in which condition is the event script going to fire if it was working?

as in Step Entered/Exit or one of the main condition that is applied to the Execution Lifecycle(Started/archived/stopped) that kind?

In generality eventscripts can only be debugged if the work is committed as in a transaction went through or in the absence of the eventscript

one would be able to find it in select* from WWork where Work_ID=<workid> of the workflow

If you try to debug a script before the work is committed it can be done but not very easily

some related info in my blog there is a link that will show you one of the gurus of WF Jeff Lang uses

in that. https://appukili.wordpress.com/2013/10/25/event-scripts-debugging/

similarly another friend Ossie has this http://www.oscriptadventures.com/2013/03/observer-effect-quantum-physics-and.html

I think most of us who do not have advanced ways like OT programmers use echo and others to print out and debug...

..... appnair appunair( Livelink Rocks )

Well, if I called the wrongnumber, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

On Wed, Aug 16, 2017 at 2:49 PM, eLink Entry: Content Server Development Forum <development@elinkkc.opentext.com> wrote:

Debug OScript code with Builder Posted byOliveira, DuarteOn 08/16/2017 03:45 PM

HiWe have a workflow with one associated event script. Unfortunately, we can't make Content Server Builder debug the script, despite the use of scheduler.debugbreak(). The problem is specific to an instance, we confirm a bunch of others and all went well.The error message in log is "error finishing step", quite vague... Thanks for all
[To post a comment, use the normal reply function]
Forum: Content Server Development Forum
Content Server: Knowledge Center CS16

Duarte Oliveira

Hi Krishnankutty

The script starts when the step is done. I have select it in the "event script" tab.

I checked in SQL Server that the work was commited.

The most annoying is that i know the debugger is working (i made some tests, in development environment, with debugbreak in other instance and the script was catched) but specifically in this instance, in production, it doesn't stop, or so it seems. The error is kicked right in Livelink (i took the liberty to use the image from your blog since the error is the same).

what a headache

Many thanks!

appuGmail

Well then in production why do you think it is this eventscript that was aborting it? any specific reason why an IH or some other event script is rolling it back?

if you out a echo in CSIDE (not builder) and scheduler.debugbreak() in production i would think that your problem is the saved script or locked one is saving a break point.

If you look in your thread log you will see something like "user break" or something of that sort.

So for posterity i will say this

Event Script Debugging in Builder

System should run in builder
scheduler.debugbreak() will stop the script from proceeding further and on the GUI you will most likely see a error also not a good idea to leave that in code when you get into production
If you accidentally have saved a debug instruction "red icon" then export your source and import the source back with your work unlocked.You can also use utilities like "remove saved breaks" etc or look closely in the code.
There is no way to debug eventscript in running threads like in service unless you log them.

Event Script Debugging in CSIDE

Depending on the most stable version of CSIDE the scheduler.debugbreak() is honored only while it is running in CSIDE a.k.a builder mode
If you leave the debug instructions or written down scheduler.debugbreak() in code only CSIDE running will intercept them,you can safely run that in prod code(Not a good idea to leave a bunch of debugging things in there)
There is no way to debug eventscript in running threads like in service unless you log them.

I always echo the script so that I know my code is getting executed.

In newer livelinks the echo itself is very difficult unless you did this Set the Log Level at `func=admin.configurelogging` cortest our slack group and Christopher Meyer ,Greg Griffiths,John simon

..... appnair appunair( Livelink Rocks )

Well, if I called the wrongnumber, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

On Fri, Aug 18, 2017 at 11:10 AM, eLink Entry: Content Server Development Forum <development@elinkkc.opentext.com> wrote:

Debug OScript code with Builder Posted byOliveira, DuarteOn 08/18/2017 12:04 PM

Hi KrishnankuttyThe script starts when the step is done. I have select it in the "event script" tab.I checked in SQL Server that the work was commited.The most annoying is that i know the debugger is working (i made some tests, in development environment, with debugbreak in other instance and the script was catched) but specifically in this instance, in production, it doesn't stop, or so it seems. The error is kicked right in Livelink (i took the liberty to use the image from your blog since the error is the same).what a headacheMany thanks!
[To post a comment, use the normal reply function]
Topic: Debug OScript code with Builder
Forum: Content Server Development Forum
Content Server: Knowledge Center CS16

Duarte Oliveira

Hi Krishnankutty, and thanks for the effort

I suppose the error is in the code because the workflow stops in this step and there's nothing special here unless the event script. The previous steps, in workflow map, are displayed as completed.

I think if it is because break points or saved scheduler.debugbreak() then every created instance should break, and they tell me they created many more after the problematic one and walked through the end; the client problem is in this specific workflow instance.

I've also tried spread some echo in the code but none return in logs. It looks like is not read.

Thanks