Recently I have met with the Problem in form of defect. The Problem was related to Record Visibility in Activity.
There were activities created for SR as a result of Email Response and properly visible in Activity List Applet under SR. We have Pick Applet in SR Applet for fetching all Email related activities. But strangely same activities were not visible in the Pick Applet.
Previous post regarding new custom columns mapping in EIM table seems very useful for Siebel developers. Especially, the ones that are planning a new move to this territory of Siebel. Brijesh has written it beautifully which you can read from the link below:
SIEBEL EIM – CUSTOM COLUMN MAPPING
I have also applied the same tips given in SIEBEL EIM – CUSTOM COLUMN MAPPING. In one of our implementations, we have number of custom columns in S_ORDER table and have the requirement to update two of the existing custom fields X_TEST_DUMMY_COLS_VALUE and X_TEST_VAL.
In Siebel, we generally tend to use the fields on the BC level in a number of ways, one of them being their use in Siebel scripts. The most common functions for operating on BC fields are GetFieldValue() and SetFieldValue() used for getting a value, or setting a value of the corresponding field in the BC. However, Siebel requires using ActivateField() before operating on any field of the BC.
Fields that are not active at runtime should not be used in script. Runtime errors, flawed logic and lost data may be the result of such a practice.
Assets Screen Load is a major problem in Siebel, and a major pain area for the concerned developer. I am sure many of you would have come across it in one implementation or the other.
If there are more than 10,000 records in Assets screen, vanilla Siebel Application will not load the screen.