You are on page 1of 19

Siebel 8.

0 Essentials

Responsibilities and Views

1 of 19

Module 4: Responsibilities and Views

Module Objectives
To understand a Responsibility and describe its purpose To create a new Responsibility and modify an existing one

Responsibilities and Views

3 of 19

Business Requirement
Large-scale enterprise applications should selectively grant access to

its users, for example:


Access to system administration views should be visible to a limited number of users Users should have access to only relevant data

Responsibilities and Views

4 of 19

Solution: Access Control


Siebel Application provides Access Control mechanisms to restrict

access to views and data


Positions control access to data Responsibilities control access to views
These mechanisms are independent of one another

Responsibilities and Views

5 of 19

Views and Job Functions


Users should see only those views required to perform their job

functions
Prevents unauthorized access to sensitive and administrative views Improves user efficiency by restricting the number of views

Responsibilities and Views

6 of 19

Responsibilities
Responsibilities are collections of views for a particular job function Are assigned to users according to their job functions Users may have more than one responsibility attached to them, since

they may have more than one job function Properties:


A view may be contained in many responsibilities Multiple users may share the same responsibility

Responsibilities and Views

7 of 19

Seed Responsibilities
Seed responsibilities are a set of responsibilities provided with the Siebel

application
Created during application installation
They cannot be modified or deleted, but can be copied to create new

responsibilities

Seed Responsibilities created when the application is installed

Responsibilities and Views

8 of 19

Assigning Responsibilities to Users


Users are assigned responsibilities according to their job function(s)

Users with multiple responsibilities see a union of all the views Users with no responsibilities see nothing
The pick applet shows the list of Responsibilities available, which can be assigned to Andrea Alexis

Responsibilities and Views

9 of 19

Primary Responsibilities
Each user is assigned a primary responsibility The primary responsibility determines the initial tab layout during user

log in
Administrator decides the tab layout User can edit it to create a different layout
The primary responsibility for Andrea Alexis is ALL USER RESPONSIBILITY

Responsibilities and Views

10 of 19

Creating a Responsibility

Copy/Create a Responsibility Add/Remove Views Test the Responsibility

Responsibilities and Views

11 of 19

Copy/Create a Responsibility
Navigate to the Administration-Application > Responsibilities view Copy an existing Responsibility with views matching your needs Alternately, create a new Responsibility and add views
Right click and select Copy Record [Ctrl+B] to create duplicate responsibility

Responsibilities and Views

12 of 19

Copying or Creating Responsibilities


Copying seed responsibilities:

helps you to create new responsibilities with many views, similar to an existing responsibility may provide more views than required by the business logic Seed responsibilities often contain hundreds of views May include administrative views
Creating new responsibilities:

- allows application-logic to exactly match business requirements - requires determining exactly which views a user requires and adding those to the responsibility

Responsibilities and Views

13 of 19

Add/Remove Views
A pick applet provides querying functionality and improves efficiency

when selecting views

Click Add to add a view to the Responsibility

Pick applet supports querying functionality

Responsibilities and Views

14 of 19

Read-Only Views
Views can be marked as read-only for a given responsibility, if

required
Allows different levels of access to views from different responsibilities

Mark a view as Read Only to prevent editing

Responsibilities and Views

15 of 19

Clear Cache
Click Clear Cache to clear the responsibility cache

This ensures that users see their updated responsibilities the next time they log in
Click Clear Cache after creating/modifying responsibilities

Responsibilities and Views

16 of 19

Test the Responsibility


Assign the responsibility to a sample user

Use the Administration-User > Users view


Log in as that user and verify the views available in Site Map

Examine the Site Map to confirm that only the views associated with the responsibility are seen

Responsibilities and Views

17 of 19

Module Highlights
Responsibilities are collection of views used to limit views to a user Responsibilities have an M:M relationship with users and views

Create new responsibilities, either by copying seed responsibilities or

creating new ones Assign responsibilities to users and clearing cache to enable new changes

Responsibilities and Views

18 of 19

Lab
In the lab you will:

Explore seed responsibilities Create and test a new responsibility

Responsibilities and Views

19 of 19

You might also like