Documentos de Académico
Documentos de Profesional
Documentos de Cultura
Go to Object List Explorer (OBLE) on the left hand side and click + sign beside join there will
be two options Join Specification and Join Constraints
4. Configure Join Specification
Create New Record.
Give Name in the Name field.
Destination Column is given by default when insert a new record. You can change it if you
want to.
In the Source field give the name of the source field (OptyID) which you have configured
earlier to be used as Foreign Key.
5. Configure the field (Opportunity Name) which you want to display on the User Interface.
Go to Business Component > Field
Insert New Record
Give Name in the Name Field
Enter the Join Alias which you have given for the join you created.
Select the Name (for Opportunity Name) in the column field. Column name here represent
the data that you want to pull from opportunity.
6. Configure the Control in the Applet (UI).
Go to Applet > Control (if Form Applet)
Go to Applet > List > List Column (if List Applet)
Create New Record.
Enter the Name
Enter the name you want to display on UI in Caption Override Field
Enter the Name of the field you created in Field column
Don’t forget to map this field in Applet. Right Click on the corresponding Applet and map it.
Now compile the entire project which you have made the changes and you will be able to see
this joined field in the Quote Applet as shown in the picture below.
When you see this field in User Interface it will be read only because when the data is pull
from the join table it is only read only, to make it editable you have configure Pick Applet on
this field
Shuttle Applet B/W Contact and Opportunity( For M:M relation Ship b/w 2 Table)
1 Create a Link or use existing Link B/W Contact and Opportunity. Link must have
Property i.e Inter Table , Inter Parent Column and Inter Child Column
2 Create a New Multivalue Link having properties like..i.e
Name--Test Con Opp MVL
Destination Business Component—Opportunity
Destination Link--Contact/Opportunity
Primary Id Field—
Note : Here Primary Id Field is a field that specifies the name of the field in the
master business component that holds the Row ID values pointing to the primary
record in the detail business component.
3 Create New MVF Under same BC with following Properties .i.e
Name--Test Con Opp
MVL--Test Con Opp MVL (use which you have created)
Field--Key Contact Id(Field exist on child BC )
4 Create New MVG Applet with the help of Wizard having diff properties like...i.e
Name--Test Con Opp MVG
Project—Contact
B.C—Opportunity(Child B.C )
Associate Applet--Test Con Opp Asso
Type—MVG
Child Object—Applet Web Template
5 Create Associate Applet by the help of wizard choosing MVG Applet and having diff
properties like...i.e
Name-- Test Con Opp Asso
Project—Contact
B.C—Opportunity(Child B.C
Type— Association List
And for Applet Web template
Contact form Applet6 In Contact-- ---Create new control to display Shuttle Applet
In Controls
Name-- Test Shuttle
Field-- Test Con Opp(MVF you have created)
MVG Applet--- Test Con Opp MVG(MVG applet that already created)
Now go to Edit web layout---->and place that Control that you have created
7. Compile All Changes
Hierarchial Picklist:while for hierarchical, both fields(parent and child) uses the
same picklist and picklist is based on PickList Hierarchical Business component.E-x
Country--State-District.
Name .Auto Primary .Destination .BC Dest Link .Primary Id Field Use .Primary Join
Manish Link .Default .Revenue .Opportunity/Revenue .Primary Revenue Id .Yes
Note: Primary Id Field..This property specifies the name of the field in the master
business component that holds the row ID values pointing to primary records in the
detail business component
Note: Name –Manish MVF will be created automatically in the Field as well.
Field—Here it is Field in child BC-i,e a foreign key column field to the parent bc field.
I,e under Link Opportunity/Revenue the value of destination field will be here.
Next
Next
Finish.
Add one more list column to this Applet (Manish MVG Applet)
List—List Column—
Name-Primary
Field = SSA PRIMARY FIELD
Display Name = Primary
Html Type = Check Box
Html Icon Map = Check
Run Time = True.
Note..We can create a mvg applet withough wizard as well
Final Step.
Name ..Caption ..Field .Html Row Html Type MVG Applet Runtime Visible
Manish .Manish .Manish MVF Y .Field .Manish MVG Applet Y .Y
Go to the applet -- Opportunity Form Applet – Child—right Click—Edit Web Lay Out.
Add the Control i,e. Label and Text Box(Drag and Drop to the Applet) named Manish.
Here is a cookbook style example (tested on Siebel Industry Applications 8.1) how to
implement a hierarchical picklist with indefinite levels:
Use the Siebel Web Client to enter the data for the picklist. You should use the same TYPE
and distinguish the levels using the Parent field.
Create one field for each level. For all levels but the lowest set the property Immediate
Post Changes to true (for resetting the lower fields when changing the value in the
applet).
Use the Picklist wizard to create a static bounded picklist object for the new fields. Create
separate picklist objects for the first level and all subsequent levels (you will use 2 different
picklist objects). When the wizard is finished, navigate to the picklists and make the
following changes manually:
For the first level picklist, change the Business Component property to PickList
Hierarchical and set the Search Specification property to [Parent Id] IS NULL.
For the second (and subsequent) level picklist, change the Business Component Property to
PickList Hierarchical.
Navigate to the Pick Map specifications for the new fields and set the following:
For the first level field add pick map records for all dependent fields and enter Dummy as
the picklist field. Dummy is a calculated field (evaluating to an empty string) in the PickList
Hierarchical BC.
For the subsequent fields add the Dummy mapping for all remaining dependent fields and
add an additional record for the upper level field where you set the Picklist Field to Value
and the Constrain flag to true.
Do not add a dummy mapping for the last field in the hierarchy. The screenshot should give
you the general idea:
The dropdown for field 1 should only display the highest level values and lower level fields
should be constrained to the child values of the higher level field value. When changing an
upper level field, the lower level fields should be reset to empty strings. Users should not be
able to select values in "wrong order".