Comments on: Siebel – ActivateField() split wide open http://geeksbloggingat.com/2009/05/01/activating-fields/ 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/05/01/activating-fields/comment-page-1/#comment-48 Nitin Jain Sun, 03 May 2009 17:30:07 +0000 http://geeksbloggingat.com/?p=186#comment-48 Force Active comes with its own set of problems. The force activated field will be fetched evertime a query is made on that BC. It can give to serious performance issues in later stages of the project. Force Active comes with its own set of problems. The force activated field will be fetched evertime a query is made on that BC. It can give to serious performance issues in later stages of the project.

]]> By: Prachi Sharma http://geeksbloggingat.com/2009/05/01/activating-fields/comment-page-1/#comment-43 Prachi Sharma Sat, 02 May 2009 16:16:51 +0000 http://geeksbloggingat.com/?p=186#comment-43 activatefield in script gives a lot of problems. sometimes it does not work. it gives error that the field is not activated despite already using activatefield. also it gives script error and all. we must try to use activatefield first. if it does not work use force active property on bc field. this works best. activatefield in script gives a lot of problems. sometimes it does not work. it gives error that the field is not activated despite already using activatefield. also it gives script error and all. we must try to use activatefield first. if it does not work use force active property on bc field. this works best.

]]> By: Nitin Jain http://geeksbloggingat.com/2009/05/01/activating-fields/comment-page-1/#comment-40 Nitin Jain Fri, 01 May 2009 07:06:24 +0000 http://geeksbloggingat.com/?p=186#comment-40 Nice post, Himanshu. I am glad to see that you have covered a very important aspect related to EAI here which generally people tend to overlook. When instantiating requests through EAI (either Workflows invoked from some other BCs than the BCs being processed, or even more importantly through the B2B Channel), people tend to overlook the fact that the corresponding view is not exposed here. So, the fields which are active because of being exposed on the UI, or the BCs / BOs of the view are not active. These must explicitly be activated if being used through eScript. If standard Siebel Operation steps, or other vanilla Business Services are used for this processing, then ActivateField() may not be used. Nice post, Himanshu. I am glad to see that you have covered a very important aspect related to EAI here which generally people tend to overlook.

When instantiating requests through EAI (either Workflows invoked from some other BCs than the BCs being processed, or even more importantly through the B2B Channel), people tend to overlook the fact that the corresponding view is not exposed here. So, the fields which are active because of being exposed on the UI, or the BCs / BOs of the view are not active. These must explicitly be activated if being used through eScript.

If standard Siebel Operation steps, or other vanilla Business Services are used for this processing, then ActivateField() may not be used.

]]>