Search icon
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Oracle Siebel CRM 8 Developer's Handbook

You're reading from  Oracle Siebel CRM 8 Developer's Handbook

Product type Book
Published in Apr 2011
Publisher
ISBN-13 9781849681865
Pages 576 pages
Edition 1st Edition
Languages
Concepts
Author (1):
Alexander Hansal Alexander Hansal
Profile icon Alexander Hansal

Table of Contents (33) Chapters

Oracle Siebel CRM 8 Developer's Handbook
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Siebel Tools and the Siebel Repository Developer Tasks Case Study Introduction Symbolic Strings Creating and Configuring Applets Views and Screens Business Components and Fields The Data Layer Business Objects and Links Pick Lists Multi Value Fields Configuring Access Control User Properties Configuring Navigation Customizing the Look and Feel of Siebel Applications Menus and Buttons Business Services Supporting Integration Interfaces Siebel Workflow Advanced Siebel Workflow Topics Siebel Task User Interface Extending Siebel CRM Functionality with eScript Advanced Scripting Techniques Deploying Configuration Changes between Environments Installing a Siebel CRM Self-Study Environment Importing Code Files More Information

Understanding views and screens


From the discussion of Siebel Repository objects in Chapter 1, we know that a screen is a set of views and a view is a container for one or more applets. To deepen our understanding of views and screens, we will discuss these object definitions and their related objects in greater detail in the following sections.

Understanding views

Views define the largest visible area in the Siebel UI. The following screenshot shows the preconfigured All Service Request List View. The two applets in the view consume most of the screen estate:

From a business process perspective, a view is the UI element that must be available to the end user at a certain step in the process. Only then can a user accomplish the tasks defined in that step.

Views are made available to end users by administering responsibilities. A responsibility is a group of users who must execute the same business processes. A responsibility also defines a list of views that its associated users have access...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime}