Siebel Tech Blog

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