Contact Denormalization

Navigate to Site Map -> Assignment Admin -> Assignment Policy Screen
Query for following Policy Records by Name field and backdate the expiration date for these records
ASGN: Contact
Contact Denormalization
Login to Server Manager
srvrmgr /g <Gtvy Srvr Name> /e <Ent Srvr Name> /s <Siebel Srvr Name> /u <User Id> /p <User Pwd>
Start Batch Task for doing the job
Start task for comp asgnbatch with asgnmode=’Denorm’, AsgnObjName=’Account’, ObjWhereClause=<where clause of a query that filters the account records to be considered for the operation>
Exit from Server manager
exit
Observe that all associated contact records have upadted there contact list position data with the associated Account record

CursorMode for Query

The CursorMode is not defined correctly for the BC.ExecuteQuery method. If you do not specify a CursorMode when calling the ExecuteQuery BC method, the method will use the default CursorMode, ForwardBackward. In the case where you traverse the record set using an initial ‘FirstRecord’ followed by repeated calls to ‘NextRecord’, use the CursorMode ForwardOnly.   When using the ForwardOnly CursorMode, the system does not create a buffer/cache maintaining the entire record set, resulting in improved performance. If requirements dictate that script must step backwards through a record set with BusComp.PreviousRecord or by calling BusComp.FirstRecord after moving off the first record, then the scripter must use the ForwardBackward CursorMode. When manipulating the current UI context data set, it is necessary to set the query mode to ForwardBackward because the user will want to traverse the data in both directions for the applet displaying the data.
Consequence: Where a ForwardOnly cursor mode is used in a UI context or in one where reverse navigation is performed, a runtime error will occur when attempting to scroll backwards through the result set. Using a ForwardBackward cursor where one is not necessary will result in sub-optimal performance when fetching and navigating through record sets.  In most cases, a ForwardOnly record set is preferable