Comments for Siebel Tech Blog

Comment on Siebel SQL Log Analyser by Oli

Oli — Wed, 22 Feb 2012 10:03:09 +0000

Hi Benny!

Long time no hear – I hope you are doing well and that BI Publisher isn’t giving you too much trouble!

Great to hear that the little application worked for you – that’s brilliant! Sometime’s it’s the simple utilities that give the most benefit.

Regards,

Oli

Comment on Siebel SQL Log Analyser by Benny

Benny — Wed, 22 Feb 2012 09:15:27 +0000

Thank you Oli for sharing this, will definately come very handy some time!
Just tried it on a ~50MB log file and it worked great – thanks a lot!!!

Comment on Siebel Code Challenge – #3 by Oli

Oli — Tue, 21 Feb 2012 15:28:35 +0000

Hi Mario and thanks for posting!

By definition, EVERYTHING will end up in the finally block. Through hell and high water, the code in finally will be invoked. The code does not handle the case where no record is found and in such a case the calling Workflow will fail.

Regards,

Oli

Comment on Siebel Code Challenge – #3 by Mario

Mario — Tue, 21 Feb 2012 14:30:37 +0000

I can only see the code is assuming that always will find a record so in case there is no record for such id, always will end in the finally block.

Regards.

Comment on Siebel Code Challenge – #3 by Oli

Oli — Tue, 21 Feb 2012 11:50:48 +0000

Hi Piyush,

Use of ForwardOnly would not cause any untoward behaviour in this context as we’re operating on a new instance of Contact.

Regards,

Oli

Comment on Siebel Code Challenge – #3 by Oli

Oli — Tue, 21 Feb 2012 10:00:27 +0000

Hi Ranjith,

Yes, spot on. See the update for the issue that this was causing us.

Regards,

Oli

Comment on Siebel Code Challenge – #3 by Oli

Oli — Tue, 21 Feb 2012 09:59:56 +0000

Hi Rahul,

That would definitely have been a good idea, but is not the deliberate mistake in this case.

Regards,

Oli

Comment on Siebel Code Challenge – #3 by Oli

Oli — Tue, 21 Feb 2012 09:58:34 +0000

Hi Rick,

Yes, you’re right – I guess I need to flesh out my scenarios a bit better. In this case, the Contact Id is arbitrary and used just as an example of how the code might be called. Bonus lager tops to you for pointing this out though.

Regards,

Oli

Comment on Siebel Code Challenge – #3 by Rahul

Rahul — Tue, 21 Feb 2012 07:00:48 +0000

We should check whether the value coming in property set ContactId is a null value or not prior executing with block.
var sContactId = Inputs.GetProperty(“ContactId”);
if(sContactId != null && sContactId != “”)
{
with(…)
….
}
Regards,
-Rahul-

Comment on Siebel Code Challenge – #3 by ranjith

ranjith — Tue, 21 Feb 2012 02:05:20 +0000

Well, im guessing its a logical error again. The calling WF is expecting something in the output argument, right ? So there should be an else condition tooo ?

if (FirstRecord())
{
Outputs.SetProperty(“Found”, “true”);
}
else
{
Outputs.SetProperty(“Found”, “false”);
}