Upload
pinkan-rout
View
218
Download
0
Embed Size (px)
Citation preview
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 1/30
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 2/30
2 of 30Copyright © 2007, Oracle. All rights reserved.
Module Objectives
After completing this module you should be able to:
Edit business component properties to capture business logic
Describe business component view modes
Edit field properties to capture business logic
Specify business component and field user properties
Why you need to know:
Editing the properties of business components and fields helpsyou to more accurately and fully capture your business logic
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 3/30
3 of 30Copyright © 2007, Oracle. All rights reserved.
Business Component Properties
Capture business logic
Include: Properties for editing
No Delete
No Insert
No Merge
No Update
Owner Delete
Search Specification
Sort Specification
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 4/30
4 of 30Copyright © 2007, Oracle. All rights reserved.
Business Component Properties
0/4
Properties for Editing
Owner Delete Property
Search Specification Property
Sort Specification Property
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 5/30
5 of 30Copyright © 2007, Oracle. All rights reserved.
Properties for Editing
Set editing properties at the business component level to
prevent deleting, inserting, merging, and updating records in allapplets
Example: To maintain record continuity, users cannot delete orchange price lists once they have been created
1/4
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 6/30
6 of 30Copyright © 2007, Oracle. All rights reserved.
Properties for Editing Continued
These properties also appear on applets
Most restrictive settings are always used
Set these properties to FALSE at the business component level soyou can make exceptions at the applet level
Affects all applets referencingthis BC, or. . .
. . .can be customized foreach applet
Business Component Applet
1/4
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 7/307 of 30Copyright © 2007, Oracle. All rights reserved.
Owner Delete Property
Set the Owner Delete property to TRUE to enable only theowner of a record to delete it
The primary on a team-based business component is the owner ofthe record
JRUBIN is primary owner;only JRUBIN can delete
2/4
/
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 8/308 of 30Copyright © 2007, Oracle. All rights reserved.
Search Specification Property
Specifies records to be retrieved by the business component
Typically used when there are multiple business componentsbased on the same table
3/4
Conditionalstatement
BC field
3/4
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 9/309 of 30Copyright © 2007, Oracle. All rights reserved.
Search Specification Expression
Consists of field names, constants, functions, logical operators,and comparison operators
Example: For a given user, Contact(All) retrieves:
All contacts where the Personal Contact flag is “N”
All personal contacts belonging to the user
Field name in [ ]. . .
Logical operator
Operator
Function
. . .must match
exactly
3/4
3/4
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 10/3010 of 30Copyright © 2007, Oracle. All rights reserved.
Search Specification Considerations
Appear on business component properties and applet properties
Search specifications are part of the WHERE clause for all appletsthat display this business component
Predefined queries may also contribute to the WHERE clause
Search specifications on the applet are combined with searchspecifications on the business component with an AND in the
resulting SQL statement Avoid mutually exclusive search specifications
Avoid competing search specifications that preclude record display
Screen Application
Business
Component
Business
Object
ViewApplet
Field
List Column
or Control
UI
Layer
BusinessLayer
3/4
4/4
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 11/3011 of 30Copyright © 2007, Oracle. All rights reserved.
Sort Specification Property
Determines the sort order of the retrieved records
Use (DESC) or (DESCENDING) to sort that field in reverse order
Cannot be set at the applet level
. . .configure asort specification
Must matchexactly
To sort by lastname, then first
name. . .
4/4
Ensure that an indexexists to support the
sort specification
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 12/3012 of 30Copyright © 2007, Oracle. All rights reserved.
BusComp View Mode
Specifies that the BC is subject to Access Control
Owner Type property identifies the Access Control mechanismthat limits records a user can access
BCs may have multiple access mechanisms
Allows records to be associated with different owner types
Supports multiple view modes
Identifies the
AccessControlmechanism
BC field usedto specifyvisibility
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 13/3013 of 30Copyright © 2007, Oracle. All rights reserved.
BusComp View Mode, Example
The Opportunity business component has a position-basedBusComp View mode
Invoked when user navigates to the My Opportunities or My
Team’s Opportunities view
Visibility MVField property is set to Sales Rep, so applicationreads list of positions from Sales Rep MVF to determine record
visibility The My Opportunities view shows records with the user’s current
position listed in the Sales Rep MVF
The My Team’s Opportunities view shows records where user’s
direct or indirect reports are primaries on the Sales Rep MVF
Person- or position-basedBusComp View modes
are invoked by My views
For each record, theapplication compares theuser’s current position to
positions in Sales Rep MVF
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 14/3014 of 30Copyright © 2007, Oracle. All rights reserved.
Field Properties
Customize fields by editing property values
Setting field properties at the business component level setsthem across all applets that reference the business component
Each applet references one, and only one, business component
Properties set at thebusiness componentlevel affect all applets
that reference thebusiness component
0/4
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 15/3015 of 30Copyright © 2007, Oracle. All rights reserved.
Business Component Field Properties
0/4
Required and Read Only
Validation
Default Values
Calculated Fields
1/4
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 16/3016 of 30Copyright © 2007, Oracle. All rights reserved.
Required and Read Only Properties
Setting Required to TRUE prevents user from leaving field blank
Setting Read Only to TRUE prevents user from editing the value
1. Contacts requirelast names
2. Required fieldmarked with
asterisk
3. Attempting to savewithout last name causes
error message
1/4
2/4
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 17/3017 of 30Copyright © 2007, Oracle. All rights reserved.
Validation Property
Checks the rule when a record is saved to ensure that the fielddata is valid
Message is customizable
Can refer only to business component fields in the same record
2/4
Birth datemust be
prior to thecurrent date
Text displayedwhen
validation fails
Specifyexisting string
in SRF. . .
. . .or enter acustom
message
Option toinclude
system errormessage
2/4
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 18/3018 of 30Copyright © 2007, Oracle. All rights reserved.
Validation Property Continued
Rules are expressed as a combination of logical operators,constants, field names, and predefined functions
Constant
Operator
Field name
Logical operator
2/4
3/4
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 19/30
19 of 30Copyright © 2007, Oracle. All rights reserved.
Default Values for Fields
Pre Default Value
Automatically assigns a value to a field for a new record Post Default Value
Assigns a value to a field, if not entered by the user, before therecord is inserted into the database
Example: If the user does not designate a contact as personal,
the system assumes it is not personal, and sets it to N
3/4
4/4
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 20/30
20 of 30Copyright © 2007, Oracle. All rights reserved.
Calculated Fields
Derive their value from values in other fields in the same recordof the business component in which the calculated field resides
Cannot be stored in the database; therefore, there is noassociated column
To enable, set Calculated property to TRUE (checked)
4/4
Column propertyis empty because
calculated fields are notstored in the database
4/4
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 21/30
21 of 30Copyright © 2007, Oracle. All rights reserved.
Restrictions on Calculated Fields
Calculated fields are read-only
System does not validate values of calculated fields Sorting on calculated fields is not supported
Querying on calculated fields is supported
Performance depends upon whether functions in the queryexpression can be incorporated into the SQL statement
4/4
4/4
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 22/30
22 of 30Copyright © 2007, Oracle. All rights reserved.
Calculated Value Property
Is an expression built from:
Field names in the same business component
Field names from the parent business component
Current BC must have the child in a detail view
Standard functions
String, numeric, and logical operators
System functions
4/4
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 23/30
23 of 30Copyright © 2007, Oracle. All rights reserved.
User Properties
Are object definitions added as children to an applet, businesscomponent, control, field, or list column
Used to configure specialized behavior beyond what isconfigured in the parent object definition's properties
Each user property contains its own conditional logic
Can implement specific, custom IF/THEN logic
Many use their own unique syntax
Can be used as a declarative alternative to scripting
A wide variety of user properties exist, such as:
BC Read Only Field, Field Read Only Field, and On Field Update
Set
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 24/30
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 25/30
25 of 30Copyright © 2007, Oracle. All rights reserved.
User Property, BC Read Only Field Example
Create a calculated field on the Order Entry – Line Itemsbusiness component whose value is either Y or N
BC Read Only Field user property requires an input value of Y orN, so create a calculated field whose values are limited to thosetwo values
For this example, create a calculated field named BC Read Only
Flag with the expression: IF([Status] = "Shipped," "Y," "N") This sets the value of the calculated field to Y if the status is
shipped, N otherwise
BC Read Only Flag SVF has avalue of Y if the status of theitem is shipped, N otherwise
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 26/30
26 of 30Copyright © 2007, Oracle. All rights reserved.
User Property, BC Read Only Field Example Continued
Add the BC Read Only Field user property
Set the Value property to BC Read Only Flag
Value is the name of the calculated field on the BC
When the value of this field is “Y,” the current record is read-only
Create User Property whichreferences the calculated field
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 27/30
27 of 30Copyright © 2007, Oracle. All rights reserved.
. . .depending on theBoolean value in this field
User Property, Field Read Only Field
Sets a specific field in a business component to be read-only
Field Read Only Field: Location sets Location field as the target ofa conditional statement
Value is the name of a field that contains a Boolean value
At run-time, if condition is met, field is set to read only
. . .this target field. . .
S_ORG_EXT
ROW_ID INT_ORG_FLG
1 Y
This condition
affects. . . Location is ready only
Location is
not readonly
Y
N
INT_ORG_FLG
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 28/30
28 of 30Copyright © 2007, Oracle. All rights reserved.
Adding a User Property
Is done via a picklist in the Name property in the BusinessComponent User Properties window
Only those user properties allowed for parent BC are displayed
Displays user propertiesallowed for this BC
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 29/30
29 of 30Copyright © 2007, Oracle. All rights reserved.
Module Highlights
BC properties are set to control behavior:
Editing properties, Owner Delete, Search Specification, and SortSpecification
BC field properties are set to control behavior:
Required, Read Only, Validation, Pre and Post Default, and ForceCase
BusComp View Mode specifies BC is subject to access control Calculated fields derive their value from other fields in the same
record of the BC in which the calculated field resides
User Properties have their own specialized logic that can be
added to a BC Declarative alternative to scripting
8/3/2019 Business Layer Configuration Existing Business Components and Fields 29
http://slidepdf.com/reader/full/business-layer-configuration-existing-business-components-and-fields-29 30/30
Lab
In the lab you will:
Incorporate business logic into the application by configuringproperties of business components and fields