à What was done to fix it.
Go to the Activity Home Page Applet. Check for all drilldown objects on ActivityType
Add ‘Id’ (specifically) in Source & Destination fields
Compile n release the SRF
Siebel v7.7 has a different query than v8.1..
System columns are exposed as BusComp fields. These columns can be exposed as controls or list columns on applets without explicitly defining them in the BusComp definition.
| System Field | System Column Name | Description |
| Id | ROW_ID | Primary key for the table |
| Created | CREATED | Creation date and time of the row |
| Created By | CREATED_BY | User logon ID of the person who created the row |
| Updated | LAST_UPD | Date of last update of the row |
| Updated By | LAST_UPD_BY | User logon ID of the person who last updated the row |
Consequence
The fields Id, Updated, Updated By, Created, and Created By are available system fields that can be exposed and presented in the user interface or used in script without explicitly defining them as BusComp fields.
This introduces a data integrity issue, if such a field is exposed in the UI and the user enters data into it, the data will not be saved to the database. The application will ignore the user’s data and use the system data. When a user enters a value in such a field and later accesses the same record, they will not see the value entered.
Recommendation
Do not create BusComp fields mapped to system columns, as they are available for use in configuration and scripting without being explicitly defined, and doing so may introduce the type of issues indicated above in the consequence section.
Where such fields have been created, remove them from the BusComp definition and remap any existing references, such as list columns, controls, joins, and so forth to the supplied system column. Do not forget to verify that any script that references the custom fields is also updated.
Join specification to Party extension table has been created with the destination column property set to ROW_ID.
Consequence
Only the PAR_ROW_ID column should be used as the destination column in join specifications to S_PARTY extension tables. This is because the PAR_ROW_ID column contains the proper foreign key relationship to S_PARTY.
Although ROW_ID and PAR_ROW_ID is equivalent in most cases for party extension tables, configuring a join in this manner is not recommended, and this unexpected behavior may not be the case in future releases and this accidental success may not be the case in future releases if the table structures change.
Recommendation
When creating joins to S_PARTY extension tables such as S_ORG_EXT, S_CONTACT, S_POSTN or S_USER make sure that the join specification has a destination column of PAR_ROW_ID. Perform a search in the Siebel Tools and look for the Base table property to identify the S_PARTY related tables. The screenshot below shows some of the S_PARTY tables in the customer repository.
3. Non-Indexed Search / Sort Specifications
Several search and sort specifications were identified as keying off non-indexed columns. When specifying search and sort specifications it is important to use fields mapped to indexed columns, whenever possible.
Sorting or searching on non-indexed fields can have detrimental effects on database performance, especially on large tables, as it will produce table scans and temporary tables in the SQL execution plan.
Keep in mind that pre-defined queries where the filter or sort is based on a non-indexed column will also result in a performance impact.Issue: We have 3 buttons with same method as “Show Popup” for showing popup applets, but the buttons need to enable/disable based on the conditions. It would be difficult to enable/disable button as the all buttons are sharing the same method name.
Solution:
Inputs taken from another Siebel blog.
Give different method names for 3 buttons.
Alternative way to invoke the show popup using browser script
Write the below Browser script to invoke the “Show popup” method, when the button is clicked.
function Applet_PreInvokeMethod (name, inputPropSet)
{
// code to enable the buttons as show popup
try
{
if(name == "XXX" || name == "YYY" || name == "ZZZ")
{
inputPropSet.SetProperty("SWEMethod","ShowPopup");
this.InvokeMethod("ShowPopup",inputPropSet);
return("CancelOperation");
}
}
}
Write the server script in Pre Can Invoke method as usual to disable/enable button based on conditions.
function WebApplet_PreCanInvokeMethod (MethodName, &CanInvoke)
{
try
{
var pstntype = TheApplication().GetProfileAttr("Primary Position Type");
if((MethodName == "XXX" || MethodName == "YYY") && (pstntype == "CCC" || pstntype == "DDD"))
{
CanInvoke = "FALSE";
return(CancelOperation);
}
else
{
CanInvoke = "TRUE";
return(CancelOperation);
}
}
catch(e)
{
TheApplication().RaiseErrorText(e.tostring());
}
finally
{
pstntype = null;
}s
return (ContinueOperation);
}
There are times when you wished you should be in the mountains away from mobile network reach.
Or sometime you wanted to avoid a call but did not want the caller to know you are not picking calls intentionally?
Definitely you will not switch-off the mobile. The caller will hear a message saying your mobile is switched off. That means you intentionally switched it off! and some phones got features like offline mode .but still the end user will hear mobile switch off message. Excuses like your phone charge went off ..you didn’t take the charger wont make any sense .So we need some good excuse .
So what if the caller hears a message like “the phone is not reachable”, or “out of network”?
‘Mobile not reachable’ is a good excuse for everything you wanted to avoid. Now see how easily you can do it. After all it was the operator’s fault. Not yours!
Problems being not reachable on cell phone:
Yes, there could be problems. You never know when you miss a very important call.
Pre-requisite
--Call your family , Gal frd /boy frd.[Otherwise thy will get afraid] :-)
Step
1) This trick is very simple . Without switching it off remove the Battery of ur mobile.WE normally do it when our phone got hang ,Do the same . And don’t switch it on .
Nw if someone is trying to call you thy will hear Mobile not reachable message .. ;-) Cool naaa
Tested in Sony ericsson and Nokia
2) If the end user is intelligent .they will drop a sms with delivery report on . that means whn u switch it on message will get delivered and the end user will get the Delivery report and he will come to know tht ur phone is on .
For this .. Go to message setting in your fone >>Text Message >> Message Centers >> find the correct SMS Center for ur service operators .
there will be a number note that number some where and remove the number and save it .Once you back from your cover you can update the number back.
Now you wont receive any sms and the end user wont get any delivery report .if there is any emergency you can switch on your Phone .Make the call and again switch it off .. ;-)
Note : I wont be responsible for any personal or professional issues by using this trick .:-)
Fact 1
clicks on the "Generate Reporting Relationships" button :
Records in the S_PARTY_RPT_REL are created when a new record is inserted in S_POSTN, or when a user clicks on the "Generate Reporting Relationships" button in the Position administration view.
It would be extremely difficult to describe an unknown number of iterations of the position/parent position relationship with a single SQL statement. Siebel solves this problem by writing each position's reporting relationships to a table called S_PARTY_RPT_REL
Fact 2
Error
SBL-DAT-00309: You do not have the privileges required to view detailed information for this record. Please contact your systems administrator if you would like access to this record.
Corrective Action
1. Inspect the record where the user receives the error:
a. Determine if the user is on the access list for the record. To determine what controls the visibility of the record, review the BusComp View Modes set up for the business component and check the Visibility Field and Visibility MV Field properties.
b. Make sure there is at least one user on the access list for the record, especially if the record was imported using EIM or if you have customized the visibility settings for the related objects.
c. If the drilldown is on the same buscomp, any constraint on the original context of the buscomp, such as a query executed by the user, will be maintained.
2. In Siebel Tools, check the configuration of the drilldown, drilldown view and applet, and related business component to determine why the user does not have visibility to the drilldown record.
a. On the destination view, check the Visibility Applet and Visibility Applet Type properties. Check for a default PDQ, or a Search Specification defined on the driving applet or destination business component, which would prevent the user from seeing the drilldown record
b. On the Drilldown Object, check the following:
i. Visibility Type property on the Drilldown Object. For more information, refer to Siebel Bookshelf version 8.1 > Siebel Security Guide for Siebel eBusiness Applications > Configuring Access Control > Additional Access Control Mechanisms > Configuring Drilldown Visibility.
ii. Business Component setting on Drilldown Object
iii. Make sure the Hyperlink property is set.
iv. If you have defined the Source Field and Destination Field properties, make sure the field values will be an exact match. For example, if you use a non-System field that defaults to a Row Id, ensure that records created through EIM will have this field set appropriately.
3. If you have configured a dynamic drilldown, check the following in Siebel Tools:
a. The logic in the configuration of the dynamic drilldown must ensure that users will drill down to a view where they can see the records in question.
b. The parent Drilldown Object should have Sequence = 1.
c. The destination view defined for the parent Drilldown Object should be available in the user's responsibilities.
d. The Field property on the Dynamic Drilldown Destination object must be active in the buscomp instance.
e. Check the Value property defined in the Dynamic Drilldown Destination object
For more information on the above suggestions, refer to Siebel Bookshelf version 8.1 > Object Types Reference > Siebel Object Types for the Drilldown Object, View, BusComp View Mode, Business Component, and Applet object types. Also refer to Siebel Bookshelf version 8.1 > Configuring Siebel eBusiness Applications > Configuring Screens and Views > About Drilldowns.
4. If you have customized the Calendar Drilldown behavior,
5. You must extract a mobile client before you can drill down on the mobile client name.
6. Create bookmarks from list views instead of detail views.
7. When registering a Partner, you need to check the Organization flag.
Fact 3
Why does my -Pick Applet- display all records for a user who does not have -All- visibility?.
When the Popup Visibility is set to FALSE, no visibility is applied to Pick and Association Applets.
For example, in the standard Siebel configuration, the ‘Popup Visibility’ for ‘Account’ Business Component is set to FALSE. Hence, any Pick Applet or Association Applet based on the ‘Account’ Business Component will display all the Account records irrespective of whether the user has visibility to ‘All’ Accounts or not.
Setting the Popup Visibility of a Business Component to TRUE, should limit the records displayed in Pick Applets and Association Applets to only those records that are displayed in a ‘My’ view of that Business Component.
For example, in the standard Siebel configuration, the ‘Popup Visibility’ property on the ‘Opportunity’ Business Component is set to TRUE by default. Hence, all Pick Applets and Association Applets based on the ‘Opportunity’ Business Component will always display only those Opportunity records that are visible to a user in the ‘My Opportunities’ view.
