Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd
Upload
225 views

Module 38: Understanding Siebel Event Models

This document discusses Siebel event models. It describes how events occur when a user interacts with object instances in memory and how Siebel handles events. Siebel uses event handlers to define how it responds to events. Events can trigger workflows, personalization rules, data validation, and call of business services. The document explains the Siebel object model, different types of events, and how Siebel processes events through pre- and post-operation handlers.

Uploaded by

AkhamiePatrickOshioke
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
225 views

Module 38: Understanding Siebel Event Models

This document discusses Siebel event models. It describes how events occur when a user interacts with object instances in memory and how Siebel handles events. Siebel uses event handlers to define how it responds to events. Events can trigger workflows, personalization rules, data validation, and call of business services. The document explains the Siebel object model, different types of events, and how Siebel processes events through pre- and post-operation handlers.

Uploaded by

AkhamiePatrickOshioke
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 15

Essentials (Siebel 7.

7)

Module 38: Understanding


Siebel Event Models
Module Objectives

After completing this module you will be able to:


 Describe Siebel object instances and events
 Explain Siebel Event Handling
 List the processes that can be triggered by events

Why you need to know:


 Understanding the Siebel Event model allows developers
to successfully extend the behavior of the standard Siebel
application

Module 38: Understanding Siebel Event Models 2 of 15


Siebel Object Model: Object Instances
 When a user is using the Siebel application, instances of Siebel
objects are loaded into memory

View Business Object


(Account Detail (Account)
Contacts View)

Applet Business
(Account Entry Component
Applet) (Account)

Applet Business
(Account Contact Component
List Applet) (Contact)

Module 38: Understanding Siebel Event Models 3 of 15


Events and Event Handlers
 An event is a user or system action that occurs while the Siebel
application is running
 An event handler is a process in the Siebel application that
defines how the Siebel application responds to an event
 The event: After creating a new record, the user steps off the
record
 The event handler: The Siebel application commits the record to
the database

Module 38: Understanding Siebel Event Models 4 of 15


Object Instances and Events
 Events occur on the object instances in memory
 Example: After creating a new record, the user steps onto next
record in the applet

Applet
(Account List Applet) User steps off record Siebel Event Handler tells the
business component a new
record has been created
ChangeRecord Event fires

Business Component WriteRecord Event fires


Siebel Event Handler causes the
(Account) record to be written to the
database
Record is committed
to the database

Module 38: Understanding Siebel Event Models 5 of 15


Event Processing
 When a selected event occurs, the Siebel execution engine:
 Fires a pre-operation event
 Executes the standard Siebel built-in event handler
 Not visible or configurable by developers
 Part of the C++ class specified for each object
 Executes a post-operation event-handler process
 Note: Not all exposed events are paired (have pre and post)

“pre” operation
Name prefixed
with “pre”
Siebel event
Siebel handler
Application Name not
prefixed with
“post” operation “post”

Module 38: Understanding Siebel Event Models 6 of 15


Pre-Operation Processing
 The Siebel application can be configured to perform checks
before the standard Siebel event handler is executed and either:
 Continue to the regular Siebel event handler, or
 Cancel the regular Siebel event handler

“pre” cancel
operation
continue
Siebel Siebel event
Application handler

“post”
operation

Module 38: Understanding Siebel Event Models 7 of 15


Post-Operation Processing
 The Siebel application can be configured to perform additional
processing that occurs after the standard Siebel event handler
has been executed
 Processing is not executed if pre-operation cancels

“pre” cancel
operation
continue
Siebel Siebel event
Application handler

“post”
operation

Module 38: Understanding Siebel Event Models 8 of 15


Siebel Object Types with Exposed Events
 Each object type is designed to handle certain processing
 Application: Events occur at the application level
 Example: Log in to application
 Applet: Events occur at the applet level
 Example: Drill down on hypertext link or click an applet button
 Business Component: Events occur at the business component
level
 Example: Update or insert a record

Module 38: Understanding Siebel Event Models 9 of 15


Runtime Events
 The Object Manager monitors events occurring in the current
Siebel application instance
 Select Site Map > Administration – Runtime Events > Events
 A runtime event requires no compilation and can trigger:
 Workflow processes
 Personalization
 Data validation
 Business services

Module 38: Understanding Siebel Event Models 10 of 15


Siebel Workflow Processes
 A workflow process is an ordered set of steps executed in
response to a defined set of conditions or an event
 Covered in later modules

Workflow process

Event specified here Workflow step

Module 38: Understanding Siebel Event Models 11 of 15


Personalization
 Siebel Personalization helps control content delivery and
enforce business rules
 Allows the creation of rules that react to the user’s behavior at run
time
 Example: When an eSales user adds printers to the shopping cart,
Personalization adds cables and ink cartridges to the Recommended
Products lists
 Allows the creation of rules that determine which views, applets,
and records a given user will see
 Example: The My Quotes applet will only appear in the home page if
the user chooses to add it to their home page layout

Module 38: Understanding Siebel Event Models 12 of 15


Data Validation
 Siebel Data Validation allows field values or records to be
validated against business rules
 Enables application administrators to create complex business
rules using a declarative interface
 Define messages to be displayed to user if rule is violated
 Validation history can be used to view log of rule violations

Module 38: Understanding Siebel Event Models 13 of 15


Business Services
 A business service is a type of program that can be called within
the Siebel application
 Encapsulates business logic
 Business service types
 Siebel-provided: Shipped with the application
 Example: Outbound Communications Manager—allows you to send an
email
 Custom: Business services created by Siebel developers
 Example: Custom code to verify a credit card

Module 38: Understanding Siebel Event Models 14 of 15


Summary

This module showed you how to:


 Describe Siebel object instances and events
 Explain Siebel Event Handling
 List the processes that can be triggered by events

Module 38: Understanding Siebel Event Models 15 of 15

You might also like