PeopleSoft Technical Training - Day 1 PDF

PeopleSoft Technical
Training
Stone Apple Group| 04 July – 11 July 2013
Private and Confidential 1

AGENDA - DAY 1
Navigating PeopleSoft Application
PeopleSoft Architecture
Data Organization
Data Validation
Introduction To Application Designer
The 8 Design Steps

Navigating PeopleSoft – Overview
AGENDA
• Navigate a PeopleSoft application using Basic and Favorites

• Identify and use the elements that make up a search page
• Control and Save search criteria.
• Set Homepage / Personalize Homepage
• PeopleSoft Architecture
• Identify Data dan Metadata Architecture
Private and Confidential

3
Navigation Basic
AGENDA
• Open Web Browser and Enter application URL
• Input UserID
• Input Password
• Sign In
http://192.168.2.72:6010/psp/PSHCSD/?cmd=login&languageCd=ENG&
http://203.7.171.34:6010/psp/PSHCSD/?cmd=login&languageCd=ENG
When you Sign In successfully, you will see the homepage with application
menu and contents.
4
Navigation Basic – Login Page
AGENDA

5
Navigation Basic – Home page
AGENDA
Navigation
Header
Personalize Area /
Target Area

6
Navigation Basic – Home page
AGENDA
• Navigation : The navigation is a hierarchy of folders and content references.
You click here to navigate to content most of the time.
• Header : The header contains quick access to navigational aids.
• Target Area : The target area displays content. Depending on where you
are in the application, this area can contain pagelets, a list of choices to
help you navigate to data, or pages that enable you to view, edit, or add
information.

7
Navigation Basic – Using Navigation
AGENDA
• The navigation is made up of two elements: folders and content references.
• Folders define the hierarchy.
• Content references are links to PeopleSoft components that hold content.
• Folders are apparent from the triangular icon to the left. Click a folder to
open it. Folders can contain folders, content references, or both.

8
AGENDA
• Folder and Content
Folder
Content

9
AGENDA
• Folder and Content
Folder
Folder
10
AGENDA
Open a Menu / Component

11
Navigation Using Favorites
AGENDA
Let’s say that you are constantly navigating to the
Workforce Administration >> Personal Information >> Add a Person

component.
You can identify this or any content reference as a personal favorite.

Favorites are associated with your user ID and are available under the top
folder in the navigation structure.

12
Navigation Using Favorites – How to Add
AGENDA
Click

13
AGENDA
• Favorites Alias field will shown as below.

14
AGENDA
• Favorites Menu save successfully message.
Click

15
Navigation Basic – How to Access
AGENDA
• Next, try to access favorites Menu after save.
Favorite
Menus

16
Navigation Basic – How to Access
AGENDA
• When you click, selected component will be show.

17
Personalize Content
AGENDA
• Two Personalize Content :
1. Content : Feature for change menu option.
2. Layout : Feature that allow you to select pagelets and

change the layout menu of the homepage.

18
Personalize Content - Content
AGENDA
• Select Content on Homepage screen
Click

19
AGENDA
• Content on Homepage screen

20
AGENDA
• Select Menu Save, or Return to Home
Save Changes
Return to Home
/ Discard

21
Personalize Content - Layout
AGENDA
• Select Layout on Homepage screen
Click

22
AGENDA
• Layout on Homepage screen

23
AGENDA
• Select Menu Save, or Return to Home
Save Changes
Return to Home
/ Discard

24
Basic and Advanced Search
AGENDA
• Advanced and Basic Search Feature on a component
or page is depending on how it is configured.
• Advanced Search Features allow user to search some

record with more than 1 criterion.
• Basic Search Features allow user to search some

record with only 1 criterion.

25
AGENDA - DAY 1
Data Organization
Data Validation
The 8 Design Steps

Architecture - PeopleSoft Data and Metadata
AGENDA
• Tables in PeopleSoft Databases

27
AGENDA
• System Catalog Tables
• System catalog tables are analogous to a table of contents for a book or to file
allocation tables on a hard disk
• The structure and table names vary depending on which RDBMS is being used
• These tables keep track of all the objects that reside in the database instance
• These tables store information like Table names, column names, and index names
• These tables are created and owned by the RDBMS
• These tables are often described as System Metadata

28
AGENDA
• PeopleTools Tables
• PeopleTools tables contain definitions that make up an application.
• The structure of tables is the same for all applications, but the content varies
• Each application enters data into the PeopleTools tables when it is installed.
• Can be modified by PeopleTools such as PeopleSoft Application Designer
• Use the naming convention PS*; for example, PSPNLDEFN

29
AGENDA
• Application Tables
• Application data tables contain data entered for use by your organization
(Transactional Data)
• Developers can create more of these tables
• Structure and Content is modified using Application Designer
• Tables use naming convention PS_*; for example, PS_LEDGER

30
Architecture – Delivering UI
AGENDA
• PeopleSoft Pure Internet Architecture (PIA)
• The databases that act as the foundation for all PeopleSoft applications have
undergone change over the years, but the most significant changes have been in the
user interface. PIA removes the requirement for client setup or administration.
• PIA transfer data from the database to the application server, where the data is
transformed to HTML that is assembled by the web server and presented to the
user on a browser.

31
AGENDA
• PIA Elements
• Browsers
• Web Server
• Application Server
• Database Server

32
AGENDA
• Browsers as Clients
• PeopleSoft is based on PIA, a server-centric component architecture that enables
secure user access to PeopleSoft applications.
• In PIA, there are no PeopleSoft executables on the client.
• The client can be an Internet device that uses standard Internet technologies, such
as HTTP, HTML, and XML, to communicate with the PeopleSoft application.
• Simple application maintenance and deployment
• Platform Independence
• Low bandwidth access

33
AGENDA
• Web Server : A Web server acts as the front end of PIA, as illustrated in
the following diagram:

34
AGENDA
• Application Servers : In PeopleSoft, there is added functionality and a very
tight association with the Web server, as shown in the following diagram.

35
Architecture – Development Environment
AGENDA
• Two Tire Connection : If you make a two-tier connection, you are using
database connectivity software to connect to the database directly.
Ilustration :

36
AGENDA
• Three-Tier Connections
• The three-tier client uses BEA Tuxedo and an application server to manage the
database connection.
• This speeds performance over wide area network (WAN) connections and makes for
a thinner client because no database client software is required.
• This system requires Microsoft Windows and the PeopleSoft client software.
• The connection to the application server requires the TCP/IP protocol.

37
AGENDA
• Three-Tier Connections :

38
AGENDA - DAY 1
Data Organization
Data Validation
The 8 Design Steps

Data Organization - Terminology
AGENDA
• relational databases are used in a variety of contexts, RDBMS terminology
includes multiple expressions for the same element. The following table
lists some of these expressions
PeopleSoft Terms Equivalent Terms
Table File, set
Row Record, occurrence, entry, line
Column Field, item, data element attribute.
40
Data Organization - Table Structure
AGENDA
• Relational database models separate data into separate tables that are
related to one another.
• The links between tables are established with key structure.
• Relationships generally fall into two categories – parent / child and
prompt relationships. Keys play a role in each.
41
Data Organization – Table Structure
AGENDA
Field Example
42
Record / Table Example
43
AGENDA
High Level
Key
Parent Table
Data
Key from
Prompt Table
44
Relationship Between
Prompt, Parent, and Child tables
AGENDA
• Many development projects include a data organization

component. You might receive a list of data fields in a flat
file format to put online for viewing, editing, and data entry.
• The process of organizing data into logically related tables is

called normalization.
45
AGENDA
High Level Key
(Parent)
Secondary Key
(Child)
46
AGENDA
PER_ORG_ASGN_VW
ADDL_PAY_ERNCO
ADDL_PAY_DATA 47
Data Organization - Data Model
Data models depict the relationship between tables and their data.
Physical Data Model : A conceptual model shows table names and

relationships. A physical model is more detailed and includes column
names and key structure. PeopleSoft delivers physical data models for all
database applications. This is critical information for any PeopleSoft
developer.
48
Data Organization - Data Model
AGENDA
• Physical Data Model
49
AGENDA - DAY 1
Data Organization
Data Validation
The 8 Design Steps

Data Validation – Introduction
AGENDA
• PeopleSoft provides several methods for ensuring data accuracy. Prompt

tables are application data tables that store a predefined set of values
that are available to users during data entry.
• The most common method for validating data entry in PeopleSoft

applications is the prompt table edit.
• By tying a field’s value to a list in a separate table, you can limit entry or
edits to approved values only.
51
Data Validation – Prompt Table Edits
AGENDA
• Structurally, a prompt table is no different from any other application

data table. It stores values that other tables can validate against.
• The term prompt table edit refers to the way that field values can only
be filled or edited from a list of values in the prompt table.
52
AGENDA
In the example below, PER_ORG_ASGN_VW is a prompt table for the
Employee in the ADDL_PAY_DATA.
This ensures that only valid Employee can be entered in the .
Validated
Prompt table
Field
ADDL_PAY_ERNCD
EARNINGS_TBL
53
AGENDA
• Prompt Table Detail : ADDL_PAY_ERNCD
54
AGENDA
• Table Parent Detail : EARNINGS_TBL
55
Data Validation – Prompt and Search Page
AGENDA
• Below is search prompt example
• Navigate to :
> Payroll Interface
> Update Payroll Information
> Additional Pay
56
AGENDA
• Or we can directly search which page we want to access like example below
(on the menu screen) :
OR
57
AGENDA
• Below is “additional pay” search result :
Click here
58
AGENDA
• We can also search page in Advance Mode :
Advance search page Click here
Click here
59
AGENDA
• Below is “additional pay” search result in Advance:
Click here
60
AGENDA
• Additional Pay screen
61
AGENDA
• Click like example to show prompt search page
Click here
62
AGENDA
• Prompt search page
63
Data Validation – Prompt without Edits
AGENDA
• Prompt table edits require that the value entered matches a value from
the prompt table. If you try to enter something not on the list, you get an
error message.
Try to input 00 on Earning Code.
64
Data Validation – Effective Dates
AGENDA
• Tables containing an effective date (EFFDT) field as a key are called
effective-dated tables.
• Effective dating retains historical data and stores data for future use.
• To be effective-dated, a table must include the field EFFDT as a descending

order key.
65
Data Validation – Effective Date
AGENDA
• Basic : The application uses the date entered in this field to determine
the current data row. Effective-dated tables include three types of rows
(Future, Current, History)
• Data Entry Action : Effective dating is used on prompt tables for data
validation. When users click the prompt icon, they see only choices that
are active and valid for the current date. When entering rows into
effective-dated tables, you have four action choices for data entry, two
more than on tables that are not effective-dated (Add, Update, Include
History, Correct History)
66
AGENDA
• Data Entry Action Summary :
Action Can View Can Insert Can Update
Add N/A New High Level Key N/A
Update / Display Current / Future New Effective Date Future Only

(Current or Future)
Include History History, Current, Future New Effective Date Future Only
(Current or Future)
Correct History History, Current, Future Any effective Date All rows
67
AGENDA
Start Date
End Date
68
AGENDA - DAY 1
Data Organization
Data Validation
The 8 Design Steps

PeopleSoft Application Designer
AGENDA
70
PeopleSoft Application Designer Interface
AGENDA
Project Define
Workspace Workspace
Development Minimize
Tab screen
Upgrade Tab
Output
windows
71
Definitions in PeopleSoft Application Designer
AGENDA
• First, access Modify a Person page like previous training session :
• Navigate to :
> Workforce Administration
> Personal Information
> Modify a Person
72
AGENDA
• Modify a person screen, search select 1 person
73
AGENDA
• All content in PeopleSoft applications is organized around component
definitions.
• When you click a link on the search page, you see is a component.
• This component includes 5 pages (indicated by the tabs), and each page has
a number of fields.
74
AGENDA
• In Application Designer, open a component.
Or press Ctrl + O to do open shortcut.
75
AGENDA
• Then open dialog will be show :
1. Choose
Component
3. Click Open
4. Choose
PERSONAL_DATA
76
AGENDA
Below is all pages in PERSONAL_DATA component
77
AGENDA
• Open pages PERSONAL_DATA1
Prompt table
Dropdown List
78
AGENDA
• Record Definition
A record definition groups fields together and adds properties that allow a
table to be built. Remember, the record definition is not a table in the
database; it is a blueprint for an application data table that can be
constructed.
Do several step to open Record Definition.
79
Record Definition
AGENDA
• View page component definition or double click on it
Click
80
Record Definition
AGENDA
• Below is a Record opened
81
Record Definition
AGENDA
• Then view record definition or double click on it
Click
82
82
Record Definition
AGENDA
• Here is detail field for each Record
83
Project
AGENDA
• The PeopleSoft Application Designer project feature is a simple and
efficient way to organize definitions.
• A project tracks definition types as a list of names.
• While the project provides a way to view and organize related object
definitions, it does not store the objects.
• Development objects exist within your PeopleSoft database. The project

references these objects, enabling you to view a subset of definitions.
84
Project - Introduction
AGENDA
• An application is made up of many separate definitions that are related to
each other. Even in a simple application, you may have to juggle dozens of
definitions.
• Projects help you stay organized by grouping objects into logical areas.
• A project is not a definition used to create the user interface; it is a bucket

that holds references to definitions. Projects appear in the project
workspace on the left side of PeopleSoft Application Designer.
85
Project – Opening a Project
AGENDA
• Open PeopleSoft Designer Application
• Open a Project by choose :
• File > Open
Or
• Ctrl + O
• Definition : Project
• Name : Training
• Open
86
Project – Create a Project
AGENDA
• Default, when we open PeopleSoft Application Desainer, Untitled Project
will opened.
87
AGENDA
• If there already exist project name / opened project,
we can open a project or create new project also.
New Project
Open Existing
Project
88
88
AGENDA
• Next, save dialog will be shown like below. We just
need to input Project Name, and click OK.
Click
89
89
AGENDA
• Conglatulation, your first project created successfully!
• Make sure project shown on the left side of PeopleSoft Designer
Application.
• This Project will be use later on next training day. So, don’t forget your
Project Name.
Your Project Name
90
AGENDA - DAY 1
Data Organization
Data Validation
The 8 Design Steps

Design Application – First Step
AGENDA
92
92
Design Application - Planning
AGENDA
• The first step of application development–design–also encompasses the
first phase, Planning. With a solid plan, the remaining steps fall into place
easily. Don’t rush into development without understanding the project
goals. Any time saved by cutting design corners is lost in development
inefficiencies down the road.
93
Application Design Outputs
AGENDA
• Functional : Lists the functional requirements for the application.
• Specification : Describes data, business rules, user groups, and other
considerations.
• Technical Specification : Lists the definitions that are required to build the
application, complete with properties. Maps out the data model,
showing relationships between application tables.
94
Design Application – Functional Specifications
AGENDA
Final Functional Specification. We must determine :

• What parts of the specification are incomplete?
• What parts of the specification are unclear?
• What parts of the specification are missing?
95
Design Application – Technical Specifications
AGENDA
• Technical specifications should act as a roadmap for developers to
create application definitions. As such, organize it by definition type
where possible.
• You will not understand everything in this specification at this point. As
we develop the application, the value of the technical specification will
become clear for each definition as we cover it.
Further specification description and detail will be discuss in next chapter.
96
Define Fields
AGENDA
• Fields are the basic building blocks in PeopleSoft development.
• In database terms, fields represent columns in a table.
• In PeopleSoft, fields are developed independently and can be used in
multiple tables.
• Fields have 3 types of properties:
• Those that apply to the standalone definition
• Those that determine how fields integrate into a database table
• Those that determine how fields appear on a page.
97
Field Definition and Application Development
AGENDA
98
Fields and Fields Definition
AGENDA
• In traditional database terminology, the term field is often synonymous
with the term column. In the example below, the entries ADCRM1001,
ADCRM1006, etc are considered data in the Empl ID field.
99
AGENDA
• When working with PeopleSoft, avoid confusion by saying that
ADCRM1001 and ADCRM1006 are entries in the Empl ID column. In
PeopleSoft, field definitions are created as separate entities, completely
apart from the tables into which they are placed.
• Because of this design, field definitions can be created once and used
multiple times in multiple tables, as the following diagram illustrates.
100
AGENDA
When working with PeopleSoft, avoid confusion by saying that ADCRM1001 and ADCRM1006
are entries in the Empl ID column. In PeopleSoft, field definitions are created as separate
entities, completely apart from the tables into which they are placed.
First, Open Additional Pay in Payroll Interface > Update Payroll Information > Additional Pay.
101
AGENDA
• And then, open the other table in Administer Referrals screen for exampe :
• Open Administer Referrals screen on menu : Recruiting > Employee Referrals >
Administer Referrals
102
AGENDA
Empl ID Field Definition
103
Fields Properties
AGENDA
• Field properties include : • Pages Field Properties Include :
• Name • Source (Table and Column)
• Type • Alignment and display options
• Length • Label
• Label Option
• Translate values
• Record Fields properties include :
• Key Structure
• Search
• Default Value
• Required Setting
• Edit Type (Prompt, Translate, or Y/N)
104
Field Type
AGENDA
• Character ( Char ) : Alphanumeric field of fixed length (maximum of 254 characters).
• Long Character (Long) : Alphanumeric field of variable length used for text entries,
such as comments or descriptions (maximum length limited by platform only; up to
2 gigabytes [GB]).
• Number (Nbr) : Positive numeric field of fixed length for which decimals are allowed.
• Signed Number (Sign) : Positive or negative numeric field of fixed length for which
decimals are allowed.
105
Field Type
AGENDA
• Date : Date field of constant length. The system edits dates and prohibits incorrect
ones, such as day 42 or month 20. Date fields always store a four-digit year.
• Time : Time field of a constant length. Built-in edits prohibit impossible times, such
as hour 26, minute 70, or second 94.
• DateTime (DtTm) : Date and time field of constant length. Built-in edits prohibit
impossible dates and times, as defined in the individual Date and Time
fields. DateTime fields always store a four-digit year.
106
Field Type
AGENDA
• Image ( Img ) : Image field to store images in a user-defined format, such
as JPEG or Graphics Interchange Format.
• ImageReference ( Iref ) : Image field to store a static image that is the
same for all rows. Can change an image dynamically using PeopleCode.
• Attachment ( Att ) : Field that maps to a binary large object (BLOB)
database type to hold the contents of a file attachment. However, use
the existing field definition, FILE_DATA, if a BLOB column is needed.
107
Examining Field Definition
AGENDA
• Field Definition properties
• Now, let’s try create a field to see Field Definition
• Open PeopleSoft Desainer and choose New or press Ctrl + N as create
new shortcut.
108
AGENDA
• Choose Field on New Dialog Definition.
• After that press Enter or Click OK
Click OK
109
AGENDA
• Try to create some field on Field Definition :
110
AGENDA
• After Enter some field, let’s save the field.
111
AGENDA
• Open Existing PeopleSoft Fields, example Comment Field.
• Open PeopleSoft Desainer.
• Choose Open on menu or press Ctrl + O as open shortcut.
Click Here
112
AGENDA
• Open Existing PeopleSoft Fields, example Comment Field.

• Open PeopleSoft Desainer.
• Choose Open on menu or press Ctrl + O as open shortcut.
Click Here
113
AGENDA
• Open Field “Comment” 1. Choose Field
3. Click Here
2. Input
“Comment”
4. Choose Comment
Field
114
AGENDA
• Below is Comment field definition.
115
AGENDA
• Now, try to open other Field, example DATETIME_CREATED.
116
AGENDA
• The Date, Time, and DateTime field types all have a fixed length. The only
configuration value of note on the Date field is the default century. When
users enter a date with a two-digit year, this value determines to the
appropriate century.
• In Time and DateTime field types, the only additional configuration option is
the formatting of the time output, as shown in the following screen shot.
117
Assigning Translate Values
AGENDA
• We have one more task before we are through with this development step.
• You need to enter values for any fields that require translate values.
• Values stored in the Translate table are tied to specific field definitions.
• Each one Field can contain more than one translate value.
118
AGENDA
• Entering Translate Values in a Field
• Open SEX field like below screen.
1. Choose Field 3. Click Here
4. Choose SEX Field

2. Input “SEX”
119
AGENDA
• Next, click right button on the mouse to show menu. You can click
anywhere contain the field area.
Choose Field
Properties
120
AGENDA
• We can also access the field Properties by click Properties menu like
shown below :
Click here
• If you use the Translate table for data validation, translate values are
entered as a property of the field definition. Translate values can be
assigned to any character field whose length is four or less.
121
AGENDA
• Below is SEX field properties.
• There are contains 2 Tabs, General and Translate Values
Select “Translate Values”

tab
122
AGENDA
• Default there are 3 translate value for SEX field.
123
Define Records
AGENDA
• Record definitions are sets of fields and associated properties that serve as the
front end to database tables, views, dynamic views, derived/work records, and
subrecords. In this course, we focus on records that create tables.
• Each field in a record definition has two sets of properties: field properties that
are inherited from the field definition and record field properties that define
how the field functions in the record.
124
PeopleSoft Record Definitions
AGENDA
125
Database Records and PeopleSoft Record Definitions
AGENDA
• Chronology for Record Definition :
• Define Fields : Field definitions are created as separate entities.
• Create Record Definitions : Field definitions are organized, with further configuration
properties applied.
• Build Tables : A process builds database tables based on record and field definition
properties.
126
Database Records and PeopleSoft Record Definitions
AGENDA
• The illustrates relationship between the steps :
127
Four Views of a Record Definition
AGENDA
• Record definitions include properties for individual field definitions, properties for
each field in the record definition, properties for any PeopleCode assigned to events
with specific fields, and properties for the record definition as a whole.
• Open a Record for views it’s Definition, below is that four Views :
• View field properties
• View record field display properties
• View record field edits properties
• View record field PeopleCode
128
AGENDA
• Open a Record / Field Display
• First, open PeopleSoft application desainer.
• Open Record by click Open Menu or press Ctrl + O.
Click here
129
AGENDA
• Open NAMES record on Open Dialog as show below :
1. Choose Record
3. Click Here
4. Choose NAMES
2. Input “NAMES” Record
130
AGENDA
• Then NAMES record will be shown.
131
AGENDA
• Record Menu
Field Display
Use Display PeopleCode

Edits Display
Display
132
AGENDA
• Use Display - Some field added
133
Four ViewsAGENDA
of a Record Definition
• Edits Display – Right Field all different
134
AGENDA
• PeopleCode Display – all field became yes / no
135
Field Definition
AGENDA
• Properties, can be selected on Properties Menu
Click here
136
Field Definition
AGENDA
• Or we can choose from the field menu by click right mouse button.
Choose Record
Properties
137
Field Definition - Properties
AGENDA
• Uses Tab
138
Field Definition - Properties
AGENDA
• General
139
Field Definition – Record Field Properties
AGENDA
• Record Properties vs Record Field Properties
• Record Properties is Properties for record and only contain record
information without field detail information.
• Record Field Properties is detail information how field working in it’s
record.
• Record Field Properties contain two tab like Record Properties, Uses and
General.
140
Field Definition – Record Field Properties
AGENDA
• Uses Properties
141
Field Definition – Uses Properties
AGENDA
• Record Field Uses Properties divided into several part :
• Key structures in PeopleSoft record definitions
• Record field key configuration options
• Search keys and list box items
• Label Ids
• Default values
• Default page control
142
AGENDA
• Key Structure, in PeopleSoft record definitions, the following rules pertain
to key structure:
• Typically, every record definition must include at least one key field.
• If a record definition is acting as a child, it must include the same key values of its
parent, in the same order, plus at least one more key.
• If a record definition uses effective dating, the EFFDT field must be a key field with
descending order.
• All key fields must appear before any non-key fields in the order of fields.
143
AGENDA
If you double-click the EMPLID field, the Record Field Properties dialog
box appears. The first configuration option on the Use tab is Keys.
144
AGENDA
Sinopsis :
• Key : Select to identify the field as the search criteria that uniquely
identifies each row. Duplicate values are not allowed.
• Duplicate Order Key : Select to indicate a key that allows duplicate
values.
• Alternate Search Key : Select to identify the field as an alternate path
into the table data. Duplicate values are allowed in an alternate search
key field. Alternate keys are not a part of the table key structure.
145
AGENDA
• The position of keys relative to one another is critical in a record definition
— always list them in order of importance.
• Keys must be the first fields in the record. Key fields are followed by
duplicate order keys, in order of importance, then by fields that are not
keys. You can scatter alternate search key fields anywhere among regular
fields, in any order. They don’t need to be grouped.
• Key, duplicate order key, and alternate search key are mutually exclusive.
146
AGENDA
Sinopsis :
• Descending Key : Select to identify the field as descending if you want
rows of data to be retrieved in reverse alphanumeric order (order is
ascending if not selected). Used primarily for the EFFDT key.
• Search Key : Select to make a key field available on the basic and
advanced search page. A search key is valid only for key fields.
• List Box Item : Select so that values from this field appear in the results list
box on the search page (or on prompt lookup pages).
147
AGENDA
Key, Dup, or Alternatif Key Plus Search
List Box Items
148
AGENDA
• Default Pages Controls

Characteristic System Default Example
Data Field Edit box with prompt button
Translate table edit Drop-down list box
Prompt table edit Edit box with prompt button
Yes/No edit Check box
Long character Long edit box
All other fields Edit box
149
AGENDA
• You don’t have to use the system defaults, as illustrated in the following
screen shot.
150
Field Definition – Edits Properties
AGENDA
• Record Field Edits Properties divided into several part :
• Edits Display view
• Required check box
• Translate table edits
• Yes/No table edits
• Prompt table edits
• Prompt table with no edits
151
Field Definition – Edits Properties
AGENDA
152
AGENDA
• You can select any control from the list, however; many controls might not be
appropriate. Some typical examples are in this table.
Characteristic System Default Optional Page Control
Radio buttons
Translate table edit Drop-down list Edit box (with prompt button)
Check box (if only two values)
Prompt table edit Edit box (with prompt button) Drop-down list box
Yes/No edit Check box Drop-down list box
153
AGENDA
• Table Edits – Prompt table with No Edit
154
Creating Record Definitions
AGENDA
• First, open PeopleSoft Developer Designer
• Select New menu from menu bar or select menu File > New.
Click here
155
AGENDA
• Choose Field on New Dialog Definition.
• After that press Enter or Click OK
Click OK
156
AGENDA
• Then we must create record like below :
157
AGENDA
• First, open your own project that we created on the first day training,
example from the trainer is “TRAINING_NAME” project.
• To open a project, press Ctrl + O or select
> File
> Open
> Project
Or
Click Here
158
AGENDA
1. Choose Project
3. Click Here
2. Input 4. Choose TRAINING_NAME

“TRAINING_” Project
159
AGENDA
• Next, open a Field where we need like previous training.
• Open each field and below is one example for EMPID field.
160
AGENDA
• Open Definition Dialog
1. Choose Project
3. Click Here
2. Input “EMP”
4. Choose EMPID
Field
161
AGENDA
• EMPID opened, then we add to our project.
Choose Insert > Current Definition

into Project
162
AGENDA
• When we add field successfuly to project, Project workspace will be
updated like below :
163
AGENDA
• Next, create a new record.
Click OK
164
AGENDA
• Then add field the record.
165
AGENDA
• Add all field to the record.
166
AGENDA
• Now, record ready to save.
• Choose File > Save
• Or click Save directly like below.
Click Save
• Then save dialog will be show.

Click OK
167
AGENDA
• After Save, add current Definition to current Project.
• Then Project Workspace will be added a record.
168
Build SQL Tables
AGENDA
• After you create a record definition, you create a corresponding SQL table
that stores the application data.
• The fourth development step is the final one in the Data Design phase.
• When completed, the underlying tables our application requires will be in

place, ready to accept application data, as shown in the following
diagram.
• You can also modify an existing table without deleting data.

169
SQL Tables and Application Development
AGENDA
170
Build SQL Table
AGENDA
• PeopleSoft Application Designer includes a build process that creates
tables and views based on the properties of a record definition.
• The create table process creates a new application data table and
applicable indexes on the underlying database, using the information
stored in the PeopleTools tables and System Catalog tables for a specific
record definition.
171
Build SQL Table
AGENDA
• Opening Build Dialog Box
Click Here
172
Build SQL Table
AGENDA
• Then Build SQL Table dialog box will be shown :
173
Build SQL Table
AGENDA
• Build Scope : This is the list of definitions to be processed. It is
informational only and cannot be edited.
• Build Option :
• Create Tables : Creates SQL tables for all listed record definitions. If tables
already exist for listed definitions, they may be skipped or replaced, depending
on your settings.
• Create Indexes : Creates indexes for a table based on record definition
properties. Indexes are automatically created when you select Create Tables.
174
Build SQL Table
AGENDA
• Build Option :
• Create Views : Creates SQL views for all listed record definitions. If views already
exist for listed definitions, they may be skipped or replaced, depending on your
settings.
• Alter Tables : Alters existing SQL tables with changes made to the record definition
since the previous build. Settings affect how columns with existing data are
handled.
• Create Trigger : Enables subroutines that synchronize data between mobile
devices and SQL tables.
175
Build SQL Table
AGENDA
• Build Execute Options
• Build script file : Select to review and update the SQL before running the
script. The name and location of the script is determined by the build settings.
• Execute SQL now : Select if you don’t want to invoke another program to run the
SQL; the SQL runs as part of the Build process. You cannot review the SQL before
it is committed to the database.
• Execute and build script : Select to run the SQL immediately and generate a
script file for review after the process has run.
176
Build SQL Table
AGENDA
• We can also set some Setting.
Click Here
177
177
Build SQL Table
AGENDA
• Determining Build Setting
178
Build SQL Table
AGENDA
• Setting Alter Tab : Use the Alter tab settings when altering tables. You can determine
which is more important: the data or the alteration. We cover this detail during the
Impact Analysis chapter.
179
Build SQL Table
AGENDA
• Setting Logging Tab : You are allowed three levels of logging when you
run the build process. The default is the highest level, including errors,
warnings, and information.
• Log to output window : The text of the log appears in the output window at the
bottom of PeopleSoft Application Designer.
• Log to file : The text of the log is written to a log file on a drive. The name and
location of the log file appears in the Log file name text box.
• Log settings : The build settings are written to the log.
180
Build SQL Table
AGENDA
• Setting Logging Tab
181
Build SQL Table
AGENDA
• Setting Script Tab
• If you generate a SQL script, determine its characteristics here. You can choose a
single script for all build actions or have separate scripts for each type of build
(create table, create view, alter table, and so on).
• As with the log file, you can specify the name and location for the generated SQL
script file.
182
Build SQL Table
AGENDA
• Generating SQL Script
• If you do not have direct access to the database, you build a script file and give it
to the database administrator for execution. In class, we have direct access and
can run the SQL to build the table from the Build dialog box.
183
Build SQL Table
AGENDA
• Generating SQL Script
184
Build SQL Table
AGENDA
• Let’s start to Build a Table now.
3. Click Build
1. Select Create
Table
2. Choose this
185
Build SQL Table
AGENDA
• After Build Table dialog box closed, on the Output Windows will be
generate some message like below:
A log is generated, both as a file and in the output window of PeopleSoft Application
Designer. What you want to see is the message 1 records processed, 0 errors, 0
warnings.
That message mean you was create a Table successfully.
186
Build SQL Table
AGENDA
• Window Output message, Build Successfully!
187
AGENDA
188
Page Definitions
AGENDA
• Page definition is the first step in the User Interface phase of
development
189
Page Levels
AGENDA
• Page is divided into levels
• Pages can have up to four levels, all related in a one-to-many relationship
Page with 0 Level Level 0 Key With Level 1
190
Related Fields in Page
AGENDA
• To display additional information on pages that is actually not necessarily
a part of the underlying data table
Table: It e m : 0001
ITEM DESCR TYPE D e s c r ip t io n : A p p le

0001 Apple V
It e m T y p e : V
0002 Granite M
0003 Emu A
What actually PSFT Table needs, but not informative
CODE DESCR
A Animal It e m : 0001 Related field (read-only; data
comes from prompt table)
M Mineral D e s c r ip t io n : A p p le
V Vegetable It e m T y p e : V V e g e ta b le
191
Page Definition Properties
AGENDA
• Define the page properties as page
type (standard or sub page), size of
the page, etc.
192
Configuring Page Fields Properties - Field
AGENDA
• Double click the field in page to display the page field properties
193
Configuring Page Field Properties – Record Tab
AGENDA
Record and Record field
associated with the page field
Alignment of text within field

HTML Style – Leave the default
value
Miscellaneous display options
194
Configuring Page Field Properties – Label Tab
AGENDA
Label type option
Label text and appearance
Label alignment
Miscellanous options
195
Configuring Page Field Properties – Use Tab
AGENDA
To set read only or hide It e m : 0001
the fields
D e s c r ip t io n : A p p le
It e m T y p e : V V e g e ta b le
To set this field is display control field /

Display Field Related Field
related field
Enabled/disabled field
196
Configuring Page Fields Properties – OTHERS
AGENDA
197
Configuring Page Fields Properties – OTHERS (Cont.)
AGENDA
Drop-Down List Checkbox
Set value for

checkbox
198
Page Controls
NO Controls Name Description

1 Frame Draws a display-only box of variable size to visually group a set of controls.
2 Group box Draws a display-only box of variable size with a text label to visually group and identify related controls, such as
radio buttons.
3 Horizontal rule Draws a horizontal line to visually separate parts of a page.
4 Static image Draws a frame that you can associate with an image definition.
5 Static text Adds a static text item, a display-only alphanumeric field with a maximum length of 60 characters, to describe a
page, control, or group of controls.
6 Check Box Adds a small square box that operates as a toggle switch—on and off—for data controls that can have one of two
values.
7 Drop-Down List Box Adds a drop-down list box from which users selects a single value from a list of values.
8 Edit Box Adds an edit box, used for data entry.
9 Long Edit Box Adds a long edit box, a variable-length, alphanumeric control that is used for entering long text items, such as
comments.
10 Radio Button Adds a small, round button that represents one value for a control with multiple defined values.
199
Page Controls (Cont.)
NO Controls Name Description

1 Subpage Adds a predefined, presized group of controls, such as address controls, that are defined on a separate subpage
definition.
2 Image Draws a frame that you can associate with a variable image from a record field in the database.
3 Grid Adds a grid that looks and behaves like a spreadsheet that is embedded in a page; defines a level on a page.
4 HTML Area Adds an area within which your own HTML can be run.
5 Push Button or Link Adds a push button or link that represents an internal or external link, PeopleCode command, process through
PeopleSoft Process Scheduler, prompt action, scroll action, secondary page, or toolbar action.
6 Scroll Area Groups or repeats multiple fields of data in a defined area; defines a level on a page.
7 Scroll Bar Like the scroll area, contains push buttons and links for navigation, but not in the form of navigation bars. You must
manually position navigation items.
8 Secondary Page Adds an invisible control that associates a secondary page with the primary page.
200
Page Controls (Cont.)
AGENDA
• Several hot key
Toolbar Button Insert Menu Command Hot Key
Frame F
Group Box B
Horizontal Rule N
Static Text X
Check Box C
Drop-Down List Box D
Edit Box E
Long Edit Box L
Radio Button R
Grid G
Scroll Area S
201
Change Page Control
AGENDA
• Page control determined in record level
202
Page Field Ordering
AGENDA
• To see a list of page controls in order, select the Order tab
203
Page Preview in Browser
AGENDA
204
Component Definition
AGENDA
• Defining the component is the last development step, as illustrated in
the following diagram
205
Component and Pages
AGENDA
• Component is a group page definitions
• A component can consist of a single page or a set of pages that are
processed as one.
206
Component, Navigation and Security
AGENDA
• Component definitions are combined with menu definitions to create a
reference point
• Combination of component and menu is then used as a hook to assign
navigation and security access to the pages on the component
N a v ig a tio n S e c u r ity
C om ponent /
M enu
D e fin itio n
207
Component and Search Record
AGENDA
• Primary Record
• The record that we drag onto the page when we create page definitions. It represents
the table that holds the data we want to view, update, or insert rows into.
• Search Record
• The record that holds the search keys and alternate search keys for when you search
for a row of data.
208
Action in Component
NO Button Component Property Description
1 Add Add Adds a new high-level key. Use only if the search record and primary record are
the same. Limit the addition of new high-level keys to base tables.
2 Update/Display Update/Display Allows viewing of data at all levels and inserting of new rows at levels below 0.
3 Include History Update/Display All Allows viewing (but not editing) of past effective dates and inserting of new rows
if the effective date is equal to or later than today. Used on effective-dated
records only.
4 Correct History Correction Allows editing of data for all effective dates. Used on effective-dated records only.
209
Basic Component Configuration
AGENDA
• The default item name for each page is the page name. It is used internally by the
application.
210
Component Structure
AGENDA
211
Component Configuration
AGENDA
• There are 3 tabs in Component Configuration:
• General Tab : Specify the description, comments, and owner ID.
• Use Tab : Define the search record and actions.
• Internet Tab : Determine options for what users see in the browser.
212
Component Configuration (Cont.)
AGENDA
• We must configure at least two areas on the Use tab:
• The search record
• The actions
213
AGENDA
• Search Record
• Builds the search page for the component (includes the data that helps users find what
they need)
• Populates level 0 on all pages in the component
• Provides high-level key to the primary records on the component.
• Actions
• Virtually all components include the Update/Display action. Components for base tables
(search and primary records are the same) are candidates for the Add action. Only
effective-dated components ones can use the other two actions.
214
• For internet tab, there are 3 section that is important:
• Search page options

• To setup the initial tab page when the page appear
• Page navigation and processing modes

• To setup the tabs and link in page
• Toolbar selections
• To setup the button that appears in page
215
Page Navigation
Search Page
Toolbars
216
Component Configuration
AGENDA
217
AGENDA
218
Menu Definitions
AGENDA
• Menu definitions is not generate navigation
• Menu definitions are still made up of three elements:

• Menu name, a grouping of bar items
• Bar item name, one of the choices in a menu
• Menu item, the individual choice under a bar item that is associated with a
component
219
Menu Definitions (Cont.)
AGENDA
Menu Name
Bar Item Name

Menu Item Name
220
Menu Definition (Cont.)
AGENDA
221
Register Component
AGENDA
• Registering the component is the final step in the User Interface phase
• Once completed, component can view the component in a browser and begin testing, which
is the final step in application development.
222
Registration Component Task
AGENDA
• The registration wizard performs these tasks:
• Attaches a component definition to a menu definition
• Assigns the component and menu combination to a security permission list
• Assigns the component and menu combination to a content reference in a

folder for user navigation
• Before running the registration wizard, the menu definition, permission list, and
folder must exist.
223
Registration Component Task (Cont.)
AGENDA
• Attaches a component definition to a menu definition
Attaches Component to menu

definition
224
AGENDA
• PeopleSoft security is designed around three definition types.
• Permission Lists
• A set of access rights to application objects, including processes and reports, weblib functions, and
other elements
• Roles
• A definition of a functional role or job definition. Roles link users to appropriate permission lists.
• User IDs
• A unique identifier for each person who signs in to the system. User IDs, associated with user profiles,
do not carry security access rights—they are granted access by virtue of the roles (and therefore
permission lists) that they are associated with.
225
AGENDA
Create permission list
Navigation: People Tools – Security –
Permission & Roles – Permission Lists
226
AGENDA
Create role
Permission & Roles – Roles
227
AGENDA
Create User ID
User Profiles – User Profiles
228
Folder and Content References
AGENDA
Folder Content References
229
229
Folder and Content References
AGENDA
• For the registration wizard to work, a folder must exist in the portal
registry.
• The wizard creates a new content reference for the component that we
are registering in the folder that we select.
• Configuration details of both folders and content references can be

viewed by clicking the Edit link next to their names
230
Content References
AGENDA
231
Content References (Cont.)
AGENDA
No Label Description
1 Name Key field that uniquely identifies the content reference internally. When
using the registration wizard, the component name is the default value.
2 Label Text that appears in the navigation as the link.
3 Long Description Optional mouse-over text that helps users determine what the content
reference is used for.
4 Sequence Number Number that determines content reference order of appearance in the
folder. If sequence numbers match, content references are sorted
alphabetically by label.
5 Node Name Stick to the Always use local option unless you are implementing a
multidatabase enterprise portal.
6 Menu Name The menu that the component is attached to.
7 Component The name of the component that you’re navigating to.
232
Registration Component
AGENDA
Registration Button
233
Registration Component (Cont.)
AGENDA
• The first screen asks which tasks to
perform. When we are registering a
new component, we need to do all
three
• Select all three options
• Click Next
234
AGENDA
• Selecting Menu Definition To select menu definition
235
AGENDA
• Configuring the Content Reference
236
AGENDA
1 Target Content/Homepage Select Target Content for components that include full-size pages. Pagelets
Pagelet are reserved for portal homepages.
2 Portal Name Leave the default setting. It indicates which portal registry you are editing.
3 Folder Name Use the Select button to choose from a list of existing folders in the registry.
4 Content Reference Name Displays the content reference name, including the component name plus
market code as the suffix..
5 Content Reference Label Displays the content reference link that the user sees in navigation
6 Long Description Enter the mouse-over text for the content reference link.
7 Sequence Number Enter a numeral to control the order the component appears within the
chosen folder
237
AGENDA
8 Product Optionally, enter a product code to allows searches by product.
9 Template Name Leave the default value.
10 Object Owner ID Keeps track of which application development groups own the object.
11 Node Name Leave blank unless you are configuring an enterprise portal with multiple
application databases
12 Always use default local node Always select this option unless you are configuring an enterprise portal
with multiple application databases.
13 "Open" URI Base Enter the URI that specifies for PeopleSoft Application Designer the location
of your PeopleSoft Internet Architecture site
238
AGENDA
• Assigning the Permission List
To select permission list
239
AGENDA
• Finishing Up
240
AGENDA
Window Result
c
241
Test The Application
• Testing is last step of development
• If we find problems, we move back to the appropriate step to resolve it, and walk
through the process again until we are ready to test
242
Chapter Objectives
• Describe how projects transport definitions between databases
• Export a project to a file
• Import a project from a file and build its tables
243
Transporting Definitions
• Projects are containers for the definitions that make up applications

• To transport projects and definitions, you can copy a project to a
database or a file.
• Copying to a Database (Direct Method)
S y s te m C a ta lo g S y s te m C a ta lo g
P r o je c t P r o je c t
P e o p le T o o ls P e o p le T o o ls
A p p lic a tio n D a ta A p p lic a tio n D a ta

D e v e lo p m e n t
S o u rc e W o r k s ta tio n T a rg e t
D a ta b a s e D a ta b a s e
244
Transporting Definition (Cont.)
• Copying to a File (creates a series of XML files in a folder
S y s te m C a ta lo g
P r o je c t
P e o p le T o o ls
P ro
A p p lic a tio n D a ta je c t
S o u rc e W o r k s t a t io n P r o je c t
D a ta b a s e F iPl er so j e c t
F ile s
je c t
S y s te m C a ta lo g P ro
P r o je c t
P e o p le T o o ls
A p p lic a tio n D a ta
T a rg e t W o r k s t a t io n
D a ta b a s e
245
Definitions and Application Data
• The definitions that are stored in projects are data from PeopleTools
tables
• Projects do not hold application data
• If we have record definitions in our project, we will have to build them in

the new database to create the application data tables
• We can migrate application data with data mover script (DMS) files.
246
Exporting Projects
• Here are the steps to take when exporting a project to a file

• Open the project in PeopleSoft Application Designer.
• Select Tools, Copy Project, To File.
• Select the definitions to copy.
• Enter the output directory.
• Click Copy.
247
Importing Projects
• Here are the steps to take when exporting a project to a file:

• From PeopleSoft Application Designer, Select Tools, Copy Project, From File.
• Browse to select the project file.
• Select the definitions you want to copy.
• Click Open.
• Verify project integrity.
248
AGENDA
End Of Presentation

249

PeopleSoft Technical Training - Day 1 PDF

Uploaded by

Copyright:

Available Formats

You might also like

PeopleSoft Technical Training - Day 1 PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PeopleSoft Technical Training - Day 1 PDF

Uploaded by

Copyright:

Available Formats

PeopleSoft Technical

Private and Confidential 1

Introduction To Application Designer

The 8 Design Steps

Private and Confidential 2

• Navigate a PeopleSoft application using Basic and Favorites

Private and Confidential

Private and Confidential

Private and Confidential

• Header : The header contains quick access to navigational aids.

Private and Confidential

• Folders define the hierarchy.

• Content references are links to PeopleSoft components that hold content.

Private and Confidential

Private and Confidential

Private and Confidential

Workforce Administration >> Personal Information >> Add a Person

You can identify this or any content reference as a personal favorite.

Private and Confidential

Private and Confidential

Private and Confidential

Private and Confidential

Private and Confidential

Private and Confidential

1. Content : Feature for change menu option.

2. Layout : Feature that allow you to select pagelets and

Private and Confidential

Private and Confidential

Private and Confidential

Private and Confidential

Private and Confidential

Private and Confidential

Private and Confidential

• Advanced Search Features allow user to search some

• Basic Search Features allow user to search some

Private and Confidential

Introduction To Application Designer

The 8 Design Steps

Private and Confidential 26

Private and Confidential

Private and Confidential

Private and Confidential

Private and Confidential

Private and Confidential

Private and Confidential

Private and Confidential

Private and Confidential

Private and Confidential

Private and Confidential

Private and Confidential

Private and Confidential

Introduction To Application Designer

The 8 Design Steps

Private and Confidential 39

PeopleSoft Terms Equivalent Terms

Table File, set

Row Record, occurrence, entry, line