Siebel Tech Blog

We got the below error message while validating a workflow in Siebel 8.1 Validation failed for the workflow process 'XYZ' for the branch 'Connector 33' The 'WF Branch Criteria Value' - field such as LO_.. or HI_.. for the respective data type is null or empty. Solution: Run the sql below with the source as workflow row id, you will see all the branch conditions in your workflow. Pick the one which has the same name as the error message, isolate the wf step (you can modify this sql to get that) and then delete and re-add the condition step. SELECT WFBRANCRIT . ROW_ID , WFBRANCRIT . NAME , WFBRANCRIT . BRANCH_ID FROM SIEBEL . S_WFR_PROC WF , SIEBEL . S_WFR_STP WFSTEP , SIEBEL . S_WFR_STP_BRNCH WFSTPBRANCH , SIEBEL . S_WFR_PROC_FLOW WFSTEPCON , SIEBEL . S_WFR_COND_CRIT WFBRANCRIT WHERE WF . ROW_ID = WFSTEP . PROCESS_ID (+) AND WFSTEP . ROW_ID = WFSTPBRANCH . STEP_ID (+) AND WFSTPBRANCH . ROW_ID = WFSTEPCON . FOR_BRNCH_ID (+) AND WFSTPBRANCH...

Not too sure if you ever faced it, but at one time I found it really difficult to build siebel searchspecs. I had to copy already built searchspecs and manipulate it to cater to my needs.. :). However recently I figured out it's not that difficult to build these specs. In general if you are not using a process property (in a workflow) or a function (like LookupValue) searchspec is pretty straight forward. The below is an example. '[Status]='"In Progress"' (In progress within double quotes and the whole statement within single quotes, the vice versa is also okay, but make sure you use one particular quotes within the statement) If you need two fields in the searchspec and it will look like below: '[Status]="In Progress" and [Type]="Administrative"' and so on and so forth. Simple right. Now comes the little difficult part, when you have a process property or a function, e.g. '[Status]="In Progress" and [Type]="...

Siebel architecture explained in layman terms: nice one .

In Siebel version 8.0 and higher, when extracting a local database with the default settings, the local database is now encrypted. This is the standard behavior and differs from the earlier versions when you needed to make changes in order to encrypt the local database. One result is that if you download the local database using Siebel Tools, you will not automatically be able to connect to it using the Siebel Mobile Web Client (MWC). This FAQ demonstrates how in Siebel 8.0 and higher you can use the Siebel Mobile Web Client (MWC) to connect to a Local Database extracted by Siebel Tools. Steps 1. Run Generate New Database (GenNewDB). 2. Run Database Extract (DBExtract). 3. Start Siebel Tools and Connect to Local using your USER_ID and PASSWORD. Due to the fact the local database does not exist on the PC, you will be prompted to download the Local Database. 4. Once the local database had downloaded, please ensure you can connect correctly using Siebel Tools. 5. Copy the fil...

Detailed information on how to extract a local DB can be found on at this nice blog . While trying to initialize the local DB I got an error msg saying 'An internal error has occurred within the authentication subsystem for the Siebel application. Please contact your system administrator for assistance.(SBL-DAT-00565)'. This was because the DLL parameter under tool.cfg Local header was wrongly set as 'SSCDW8.DLL'. Upon changing this to 'sscdw9.dll' the DB init started working perfect.

Divisions, organizations, and accounts are instances of the Organization party type. A division, internal or partner, is also an organization if its internal organization flag is TRUE (INT_ORG_FLG = "Y") and it has an associated S_BU record. Every division is associated with one organization: either itself or the closest ancestor division that is also an organization. Every position is associated with a division. The position is then also automatically associated with one organization: the organization with which the division is associated. Persons (contacts), users, employees, partner users are instances of the Person party type. Typically, you associate each employee and partner user with one or more positions. The employee or partner user has only one active position at one time. The employee or partner user is automatically associated with one division and one organization at a time—the division and organization associated with the active position. CAUTION: Merging emplo...

Configuring Visibility of Pop-Up or Pick Applets in Siebel PRM Pop-up visibility determines what data is shown when a pop-up pick applet is displayed—for example, when a user associates a contact with an account, or adds a sales representative to the sales team. Pop-up visibility is usually set using the Popup Visibility Type property of the business component object in Siebel Tools. When pop-up visibility is set in this way, any pop-up window based on that business component shows the same data for all users. There are often circumstances where you need greater flexibility when determining what data should be shown in pop-up pick applets. For example: Most employees of your company need to see only positions for your organizations when they are assigning a sales representative to the sales team. Partner managers need to see positions for your organization, as well as the partner organizations that they manage. There are also many scenarios where your partners should have more ...

We have seen a Status Indicator Icon for Server Components in Server Management Screen and now with the help of tip given by balaji_xp it is possible for us to add that to any entitiy. For example if I want a Service Request to display different colors for different severities or Quotes to display different color based on status. You can use the example given below by balaji_xp and adapt it according to your needs. We can implement the same behavior in a list applet. Please follow the below steps: Select a List applet (e.g., Activity List Applet) and its BC (e.g., Action). In the business component, create a new calculated field. In the calculated value (e.g., Status Indicator), frame the logic that returns any of the status value as mentioned above(e.g., IIF([TimeDiff] >0, “Unavailable”, IIF(([TimeDiff] > -24), “Offline”,”Online”)) Go to the List Applet. and create a new List Column “Status Indicator” and set the following properties as below. HTML Icon Map =...

BC read only and Parent read only doesn't disable New button. It's good to use Parent RO property as we can add many instances of this based on different Parent BC. Few noteworthy things about this Parent Read Only user property are: The Field that is being evaluated should have its link specification property set to true otherwise it is not going to work The syntax of the value of this user property should be Buscomp.Field where buscomp is the name of the parent buscomp and Field is the name of the field that should be evaluated. The business component which contains the field that is to be evaluated should be the parent or grandparent by way of link or series of link relationships