Scribd
Upload
692 views

40ESS - Using Siebel State Model

This document discusses how to use Siebel State Model to control field values and restrict data changes. It describes creating a state model, defining state values and transitions, specifying authorized positions, and enabling state models for business components. An example state model is provided to restrict the Service Request status field so only managers can change it from Open to Cancelled. The module objectives are to describe how Siebel State Model works and how to create and define a new state model.

Uploaded by

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

40ESS - Using Siebel State Model

This document discusses how to use Siebel State Model to control field values and restrict data changes. It describes creating a state model, defining state values and transitions, specifying authorized positions, and enabling state models for business components. An example state model is provided to restrict the Service Request status field so only managers can change it from Open to Cancelled. The module objectives are to describe how Siebel State Model works and how to create and define a new state model.

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/ 17

Essentials (Siebel 7.

7)

Module 40: Using Siebel State


Model
Module Objectives

After completing this module you will be able to:


 Describe how Siebel State Model works and how it is
used
 Create and define a new state model

Why you need to know:


 Siebel State Model is a simple way to address business
requirements for restricting or authorizing the change of a
field value

Module 40: Using Siebel State Model 2 of 17


Business Challenge and Solution
 Business challenge
 Need to control field value changes for opportunities, service
requests, and activities
 Need to allow only certain positions to change field values
 Do not allow certain positions to change the status, or do not allow the
status change
 Solution
 Use Siebel State Model

Module 40: Using Siebel State Model 3 of 17


Siebel State Model
 Data-driven method that controls the value of a static picklist
field
 Uses a set of rules and conditions that define the transitions of a
field from one state to the next
 Can control which positions can change field values
 Ideal for controlling progression of records through an approval
process

Module 40: Using Siebel State Model 4 of 17


State Model Example
 Only the manager can change the status of a service request
record from Open to Cancelled
 A service request can be in one of four different states throughout
its lifecycle: Open, Pending, Closed, and Cancelled

Service Request

Open Pending Closed

Cancelled

Any User
Manager
Module 40: Using Siebel State Model 5 of 17
State Model Example Continued
 Five eligible transitions are defined from one state to the next
 No restrictions are placed except for Open to Cancelled

Service Request
State 1 State 2 Restrictions

Open Pending

Pending Closed

Closed Open

Open Cancelled Manager


Only

Cancelled Open

Module 40: Using Siebel State Model 6 of 17


0/4

Creating and Defining a New State Model

1. Create a State Model

2. Define State Values

3. Define State Transitions

4. Specify Authorized Positions

Module 40: Using Siebel State Model 7 of 17


1/4

1. Create a State Model


 To create a new state model navigate to Administration –
Application > State Models
 For example: Create a Service Request state model
 Is based on the Service Request business component
 Uses the Status field for the state values

1. Click New to
create a new 2. Enter values
record for the State
Model

Module 40: Using Siebel State Model 8 of 17


1/4

1. Create a State Model Continued


 After a state model has been created, changes will not take effect
until either a new server process is spawned or the Siebel Server is
restarted
 The state model is not stored in the Siebel repository
 State models can be created at any point through the Siebel UI without
compiling a new repository file

Module 40: Using Siebel State Model 9 of 17


2/4

2. Define State Values


 In the States view, define all the state values for the field to be
controlled
 For example: Values for service request are Open, Pending,
Cancelled, and Closed

2. Specify the
3. Specify which
1. Click New to Default value for
state transitions
create record(s) the Status field
to restrict

Module 40: Using Siebel State Model 10 of 17


3/4

3. Define State Transitions


 In the Transitions list, define valid transitions
 For example: Open to Pending, Pending to Closed, and so on

1. Click New to
create record(s) 2. Specify transitions
by choosing values in
the From State and
To State fields

3. Specify
transitions
available to any
user

Module 40: Using Siebel State Model 11 of 17


4/4

4. Specify Authorized Positions


 In the Authorized Positions list, specify positions for certain
state transitions
 For example, only the manager can change the status of a service
request record from Open to Cancelled

Open to
Cancelled
transition is
restricted
1. Click New to
create record(s)

2. Specify position(s)
to allow the restricted
transition(s)

Module 40: Using Siebel State Model 12 of 17


Enabling Business Components for State Models
 You can enable state models on any business component (not
enabled by default) that is based directly on the CSSBCBase
class
 Enabling state models for business components based on
subclasses of the CSSBCBase class is not supported
 Some Siebel-provided business components based on
CSSBCBase subclasses do support state models
 Example: The Service Request business component is based on class
CSSBCServiceRequest, a subclass of CSSBCBase, and supports
state models

Module 40: Using Siebel State Model 13 of 17


Enabling Business Components Requirements
 To enable state models on a business component, the fields
used:
 Must be of a single value
 Can only have a specific set of values as defined by the set of
records returned by querying Screens/Application/List of
Values/List of Values on the corresponding LOV_TYPE
 Should have no dependencies on other fields
 For example:
 TODO_TYPE is the set of action types, and the corresponding
field in the Activity business component can only take one of those
values

Module 40: Using Siebel State Model 14 of 17


Enabling Business Components Process
 Steps are performed in Siebel Tools:
 Lock the project for the selected business component
 Create a new business component user property with the following
properties:
 Name=State Model
 Value=Y
 Recompile the Siebel repository

Module 40: Using Siebel State Model 15 of 17


Summary

This module showed you how to:


 Describe how Siebel State Model works and how it is
used
 Create and define a new state model

Module 40: Using Siebel State Model 16 of 17


Lab
 In the lab you will:
 Create and define a state model to restrict data changes in the
Service Request status field

Module 40: Using Siebel State Model 17 of 17

You might also like