Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Pharma Handheld Guide > COM Extensibility > About COM Extensibility > Receiving Event NotificationsTo intercept Siebel object events, a customer must create a SCEC that implements one of the exported SHCE COM Event Interfaces (SCEI) derived from ISHCEEvent. Although both the Siebel object and the SCEC are within the Siebel Handheld application process boundary, the SCEC is the COM server, and the Siebel Handheld application is the COM client consumer. All SCECs are free-threaded, in-process (.dll) COM servers. A SCEC implements one of the event interfaces derived from the generic event interface (ISHCEEvent). The event interfaces are listed in Table 50. Table 50. SCEI InterfacesFor example, to receive notifications that a business component (such as Account) is committing a record, a SCEC implements the event interface corresponding to the business component events (ISHCEBusCompEvent interface), and adds the specialized handling code in the method (PreWriteRecord). User properties of the Siebel object in Siebel Tools indicate the events for which a SCEC will be notified. For more information about Tools configuration, see Configuring SCEC User Properties in Siebel Tools. When a Siebel event, to which a SCEC is subscribed, occurs, the Siebel object will instantiate the SCEC and notify it of the event by invoking one of the SCEI interface methods. A SCEC can manipulate the program flow by returning one of the HRESULT codes listed in Table 51.
COM extensibility supports the following Siebel events:
|
![]() |
![]() ![]() |
Siebel Pharma Handheld Guide | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |