USER INTERFACE LAYER "CONFIGURATION"
PUIL & UIL
PUIL = web template objects = .swt (Siebel Web Template)
# Web template provides a layout / Design to Applet/view Objects.
Web template file contains: (from ver. [Link] unwards)
Html 5 Tags
CSS 3 Files (cascading style sheets)
SWE Tags (Siebel Web Engine)
Script JavaScript
J-Query (NEW)
Image paths
Locations /or File Paths:
root:\client\webtemplate\.swt web template files - for client
root:\tools\webtemplate\.swt " " - for tools
root:\siebsrvr\webtemplate\.swt " " - for server
root:\client\public\enu\files .css file path
root:\client\public\enu\images images path
root:\client\public\enu\xx12xx99\script .js file path
Types of Web Template Files
1. List Applet web template
2. Form Applet web template
3. View Web Template
4. Web Page template files
[Web page templates used at Application object level
Cc-container page/cc error page/cc login page]
Types of relationships for template files:
(a) Registering
(b) Association
(c) Binding
Registering: Whenever a template is created or altered by renaming the existing
File, then that new file must be Register in Siebel tools. Once we register then we can start
using/Associating that web template.
Navigation: go to tools Web template Object create a new record ([Link])
Name:
cre_chandra_list_applet (object definition)
Navigation: go to tools child of web template web template Item Object
Name: web template file
cre_chandra_list_applet [Link] (physical - root\client\web template)
Association: Already registered "web template object definition" can be associate/attachment
with list/ (or) form applet. This process is called association.
Navigation: go to applet object query with applet name.
Select web template child object
Add newly created web templates for Base/Edit/Edit list Mode(s):
Binding: Placing a control (applet's) on web template designer's "place holder" or
Placing an applet (view's) on web template designer's "place holder" is called binding. (I.e. attaching a
control to a place holder is binding.)
Applet Object:
Basically applets are two types (frequently used):
1) List Applet List columns Fields
2) Form Applet Controls Fields
We use web template for form/list applet to get a layout/-design.
We have 3 types of Modes: (frequently used):
1) Base Mode Read only (Form / List)
2) Edit Mode Editable (Edit / New / Query) (for form/list applet only)
3) Edit List Editable (New / Query) (for list applet only)
Note: We must drag and drop controls on all modes in design time.
Symbolic Strings:
Predefined string names used as "dictionary of words."
String Reference: (Predefined)
String over Ride: (to Over-ride Pre-defined)
We display symbolic strings as Captions/titles/lables etc.
e.g.: list column/control name. Applet title name etc.
Why do we need ss: We define SS for standardizing the configuration?
(e.g.: If we do not predefine SS then each developer may use their own names
In each entity then it may leads to confusion for end users)
User defined labels / captions also can be used:
We can over-ride existing SS by using "String Over-ride" properties:
Application Object: It is collection of screens;`
Page Tab: Is used to display name on "Screen Tab"
Screen Menu Item: Is used to display view name in "Sitemap"
Application Layout set by "CC container Page"
Application Menu set by "Generic Web"
Error Messages set by "Error Page"
Acknowledgement web view Default view for the application to display.
Screens and Screen View Types:
There are 4 types of Screen Views.
1) Aggregate Category
2) Aggregate View
3) Detail Category
4) Detail View
By using different Screen View Types, we can display views in different places.
Note: Once View is created it can be displayed in 5 different places.
Views can be displayed in various places in the UI: like
1) Screen Link Bar
2) Visibility Filter
3) Detail View Tab & 4) Detail View Link Bar
5) In the Site Map
# Site Map Application Screen Menu Item.