Abstract: A computer implemented approach which identifies secondary entities associated with a (primary) entity selected by a user, and enables the user to find entity instances of interest by performing a search based on the attributes of the user selected primary entity and one or more of the identified secondary entities. In an embodiment, the secondary entities are identified based on a schema defining the entity types in a database system. The search may be used to retrieve (and provide to the user) only the entity instances matching the conditions specified based on the attributes of the primary entity and the secondary entities. The user interface may accordingly be simplified.

Abstract: A computer implemented approach which identifies secondary entities associated with a (primary) entity selected by a user, and enables the user to find entity instances of interest by performing a search based on the attributes of the user selected primary entity and one or more of the identified secondary entities. In an embodiment, the secondary entities are identified based on a schema defining the entity types in a database system. The search may be used to retrieve (and provide to the user) only the entity instances matching the conditions specified based on the attributes of the primary entity and the secondary entities. The user interface may accordingly be simplified.

Abstract: A CRM client architecture conducive to interaction with other applications executing in a same client system. In an embodiment, an agent is displayed a toolbar in response to an incoming contact from a CRM server, and the user can select one of the options based on the buttons contained in the toolbar. When the user selects an appropriate button (e.g., accept option), the CRM client application is executed to facilitate the handling of the incoming contact by the agent. On a reject option being selected by the agent, a corresponding action (e.g., appropriate notification to a CRM server) may be performed.