Professional Documents
Culture Documents
0 Essentials
1 of 19
Module Objectives
To understand a Responsibility and describe its purpose To create a new Responsibility and modify an existing one
3 of 19
Business Requirement
Large-scale enterprise applications should selectively grant access to
4 of 19
5 of 19
functions
Prevents unauthorized access to sensitive and administrative views Improves user efficiency by restricting the number of 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
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
8 of 19
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
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
10 of 19
Creating a Responsibility
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
12 of 19
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
13 of 19
Add/Remove Views
A pick applet provides querying functionality and improves efficiency
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
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
16 of 19
Examine the Site Map to confirm that only the views associated with the responsibility are seen
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
creating new ones Assign responsibilities to users and clearing cache to enable new changes
18 of 19
Lab
In the lab you will:
19 of 19