Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
The set of Siebel CRM mechanisms that control the records that the user can access and the operations that the user can perform on the records. A financial entity that represents the relationships between a company and the companies and people with whom the company does business. A loosely defined set of technologies developed by Microsoft for sharing information among different applications. A specific way to implement ActiveX technology. It denotes reusable software components that use the component object model (COM) from Microsoft. ActiveX controls provide functionality that is encapsulated and reusable to programs. They are typically, but not always, visual in nature. Work that a user must track. Examples include a to-do, email sent to a contact, or a calendar entry with a contact. An object in the Action business component of the Siebel data model that organizes, tracks, and resolves a variety of work, from finding and pursuing an opportunity to closing a service request. An Activity also captures an event, such as scheduling a meeting or calendar entry that occurs at a specific time and displays in the calendar. Anyone who uses an administrative screen in the client to configure Siebel CRM. The Administration - Server Configuration screen is an example of an administrative screen. The applet object in the Siebel Runtime Repository that contains information that Siebel Open UI uses to bind the user interface to the business component. A logical representation of one or more Siebel tables that usually contains information for a particular functional area, such as opportunity, account, contact, or activity. A business component can be included in one or more business objects. A logical representation of CRM entities, such as accounts, opportunities, activities, and contacts, and the logical groupings and relationships among these entities. A business object uses links to group business components into logical units. The links provide the one-to-many relationships that govern how the business components interrelate in this business object. For example, the opportunity business object groups the opportunity, contact, and activities business components. The physical renderer that bridges the JCarousel 3rdParty Control plug-in to the list presentation model that the listpmodel.js file defines. The client of a Siebel business application. Siebel Call Center is an example of a Siebel business application. Siebel Open UI renders the user interface in this client. The computer that the Siebel Open UI user uses. A file that Siebel Open UI uses on the client computer. A person with whom a user might be required to phone or email to pursue a selling relationship. Various business objects can refer to a contact, and this does not require a relationship between the customer and contact. In Siebel CRM, a contact attribute in the context of a business object is a party that might or might not have a relationship defined. A software application that helps a business track customer interactions. The process of modifying Siebel Open UI to meet the specific requirements of your organization. To calculate a value by using one more properties as input. For example, Siebel CRM can derive the value of a physical renderer property from one or more other properties. For more information, see Deriving Presentation Models, Physical Renderers and Plug-in Wrappers. Indicates the currently active object in the client. Siebel CRM typically sets the border of this object to a solid blue line to identify the object that is in focus. For example, if the user edits the value of field A, then Siebel CRM places a blue border around the perimeter of field A. If the user tabs from field A to field B in a record, then Siebel CRM removes the blue border from field A and adds a blue border to field B. A feature that allows the user to scroll through records in a list applet indefinitely. An object-oriented programming technique that Siebel Open UI uses where one class modifies another class. Physical renderers that Siebel Open UI uses to render a list applet in Siebel Mobile. An object that uses the jqmgridrenderer.js file to render data in a grid in the client. An XML file that identifies the JavaScript files that Siebel Open UI must download to the client browser. It maps applet user properties to JavaScript files. The Siebel Web Engine gets the JavaScript implementation file information from the Manifest File the first time a user accesses an applet during a user session. To get this information, it looks up the keys that match the user property values for this applet. Object definitions in the Siebel repository that describe the current state of Siebel Open UI. XML files that hold information on how the user experience must be shaped. Siebel Open UI uses metadata files to perform field mapping with the user interface, look ups in the user interface, application object mapping, and general representation of the user interface. A user interface mode that allows you to deploy Siebel Open UI to the native Siebel Open UI client. The metadata that Siebel Open UI uses to run a Siebel application. The Account List Applet that Siebel Tools displays in the Object List Editor is an example of an object definition. It includes metadata that Siebel Open UI uses to render the Account List Applet, such as the height and width of all controls in the applet, and all the text labels that it must display on these controls. A qualified sales engagement that represents potential revenue where a sales representative is willing to officially commit to the pipeline and to include revenue in the sales forecast. The sales representative monitors the opportunity life cycle. This representative might be compensated depending on the results of cumulative sales and potentially how well the representative maintains details about the opportunity. A system manager that hosts a Siebel application, providing the central processing for HTTP transactions, database data, and metadata. The Siebel Web Engine and data manager operate as facilities in the object manager. A business component that provides the one in a one-to-many relationship between two business components in a parent-child relationship. A JavaScript file that Siebel Open UI uses to build the user interface. It allows you to use custom or third-party JavaScript to render the user interface. It binds a presentation model to a physical control. It allows this presentation model to remain independent of the physical user interface objects layer. Life cycle methods that you code into any renderer. The ready-to-use version of Siebel Open UI that Oracle provides you before you make any customization to Siebel Open UI. An object that comes defined with Siebel CRM. The objects that Siebel Tools displays in the Object List Editor immediately after you install Siebel Tools and the Siebel Runtime Repository, but before you make any customization are predefined objects. A JavaScript file that allows you to customize behavior, logic, and content in the client. It contains the metadata and data from the applet and business component that Siebel Open UI uses to render a simple list applet or form applet. It determines the logic to apply, captures client interactions, such as the user leaving a control, collects field values, and sets properties. A class that includes life cycle methods that you code for the presentation model and control methods that Siebel Open UI uses to add presentation model properties and behavior. A type of field that only allows the record owner to view the record. for more information, see Siebel Object Types Reference. An object instance that Siebel Open UI uses for the client proxy. An entity in the Siebel data model that determines the views that the user can access. For example, the responsibility of the sales representative allows the user to access the My Opportunities view, whereas the responsibility of the Siebel CRM developer allows the user to access administration views. A Siebel CRM developer or system administrator defines the responsibilities. A type of object that Siebel Open UI uses for client scripting. An application that is part of Siebel CRM, such as Siebel Call Center. Business data that is created in Siebel Open UI, data that is created in the client of a Siebel Business Application, such as Siebel Call Center, or data that resides in the Siebel database on the Siebel Server.Examples include an opportunity, account, or activity. An open architecture that you can use to customize the user interface that your enterprise uses to display business process information. A set of database tables that stores object definitions. Examples of types of objects include applets, views, business components, and tables. You use Siebel Tools to create or modify an object definition A hierarchy that Siebel Open UI uses to communicate between objects that reside on the Siebel Server and the proxies that reside in the client. The server that runs the Siebel Server software. The Siebel Server processes business logic and data access for Oracle's Siebel Open UI. Provides access to an existing Siebel business service or workflow process as a Web service to be consumed by an external application. A type of request that Siebel Open UI sends to the Siebel Server and then waits for a reply to this request before it continues any other processing. An object that exposes scripting interfaces that allow you to modify the applet so that it can control the business component or business service that this applet references. A person who uses the client of a Siebel business application to access Siebel CRM data. The graphical user interface that the user uses in the client. |
![]() ![]() |
Configuring Siebel Open UI | Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |