Comments on: Siebel – Fetch Active view properties http://geeksbloggingat.com/2009/07/22/siebel-fetch-active-view-properties/ Let's share... Tue, 20 Jul 2010 19:37:26 -0400 http://wordpress.org/?v=2.8.4 hourly 1 By: Nitin Jain http://geeksbloggingat.com/2009/07/22/siebel-fetch-active-view-properties/comment-page-1/#comment-652 Nitin Jain Sat, 08 Aug 2009 08:52:16 +0000 http://geeksbloggingat.com/?p=656#comment-652 I understand. Nice tip, Denis! This problem would come up when you are trying to access a BO different from the one defined on Workflow Definition. I generally used a different kind of solution in this case. Let's sum it all up: 1) Use this.BusObject() in script in this case, as suggested by Denis. 2) Use a sub-process within the workflow if you want to work on a different BO. You can avoid scripting this way. 3) Don't use a BO on the Workflow Definition at all, unless absolutely necessary. This works just as well. :-) Thanks for sharing, Denis. Cheers! I understand. Nice tip, Denis!

This problem would come up when you are trying to access a BO different from the one defined on Workflow Definition. I generally used a different kind of solution in this case. Let’s sum it all up:

1) Use this.BusObject() in script in this case, as suggested by Denis.
2) Use a sub-process within the workflow if you want to work on a different BO. You can avoid scripting this way.
3) Don’t use a BO on the Workflow Definition at all, unless absolutely necessary. This works just as well. :-)

Thanks for sharing, Denis. Cheers!

]]> By: Denis Mittakarin http://geeksbloggingat.com/2009/07/22/siebel-fetch-active-view-properties/comment-page-1/#comment-641 Denis Mittakarin Fri, 07 Aug 2009 15:00:19 +0000 http://geeksbloggingat.com/?p=656#comment-641 One thing I'd like to add here is a note about Integration. We had a requirement to refresh (ExecuteQuery()) a bc after a record was written. Lets call this BC-A. Initially we simply had some code in the WriteRecord() event using ActiveBusObject(). We also had an integration piece that was accessing BC-A using workflow. As we all know, when defining a workflow we define a Business Object. What happened is that when the workflow ran, the business object defined did not include all of the bcs that were defined on BC-A's script. So what we had to do is first determine if we were on the correct view. For this we used ActiveViewName(). But then what we used to determine the correct BO was to use this.BusObject() which will determine the bc's BO. This approach made sure we were accessing the BC's business object and not the Workflow's business object. Hope I was clear and not too confusing. The gist is that you may need to use this.BusObject() in some cases as I did. One thing I’d like to add here is a note about Integration.
We had a requirement to refresh (ExecuteQuery()) a bc after a record was written. Lets call this BC-A. Initially we simply had some code in the WriteRecord() event using ActiveBusObject().
We also had an integration piece that was accessing BC-A using workflow. As we all know, when defining a workflow we define a Business Object.
What happened is that when the workflow ran, the business object defined did not include all of the bcs that were defined on BC-A’s script. So what we had to do is first determine if we were on the correct view. For this we used ActiveViewName(). But then what we used to determine the correct BO was to use this.BusObject() which will determine the bc’s BO.
This approach made sure we were accessing the BC’s business object and not the Workflow’s business object.

Hope I was clear and not too confusing. The gist is that you may need to use this.BusObject() in some cases as I did.

]]>