Comments on: Scriptless Siebel solutions – Part2

By: bhargav

Thu, 26 Mar 2009 19:36:52 +0000

hi
nice work dude !!!!!
You could have also tried this using a data validation manager.
as action BC is the child BC you can do validation by selecting all records from the DVM.You can invoke the DVM from workflow using business service and can get the error message captured in the workflow. Added advantage of using a DVM in workflow is, you can display the messages in multilingual format. Main draw back of using DVM is it is not supported on mobile and handheld applications.

By: Pankaj

Thu, 26 Mar 2009 12:41:03 +0000

Hi Neel,

I think there is a very simple way to do it . You went in a very complex way. Since Opportunity is Parent and Action is the Child.There would be a link that is existing bewteen Opportunity and Action.
There is a function called COUNT(MVL).

To use that you should have constructed a MVL on top of existing link in Oppty BC.

Then create a calculated field in Oppty BC and its value would be – COUNT(MVL). It would give you the child record count.

Then you could have used Runtime Events or WF to just verify the value of this field and then thorwn the Error.

Let me know your views on this !!

By: @lex

Thu, 26 Mar 2009 12:11:27 +0000

Hi Neel,

Great solution! I believe that it proves that is is really worth the extra effort to investigate scriptless alternatives. The overall skill level of the Siebel developer increases over time as he/she becomes more familiar with all the administrative solutions like workflow, pre-built business services and runtime events. And the well designed and upgradeable solution comes at the lowest performance penalty.

have fun

@lex

By: Kantesh

Thu, 26 Mar 2009 10:46:16 +0000

I think you could also try the data validation manager which uses runtime events as well. You could probably use the GetNumBCRows function to get the record count. Just a thought.