People Soft Tools 1

PeopleTools I
January 2004
STU-400-844
FOR
Student Guide
INTERNAL
USE
ONLY!
PeopleSoft
PeopleTools 8.44
PeopleTools I
STU-400-844
Restricted Rights
Copyright 2004 PeopleSoft, Inc.
All rights reserved.
All material contained in this document is proprietary and confidential to PeopleSoft, Inc.
and is protected by copyright laws. No part of this document may be reproduced, stored
in a retrieval system, or transmitted in any form or by any means, including, but not
FOR
limited to, electronic, graphic, mechanical, photocopying, recording, or otherwise without
the prior written permission of PeopleSoft, Inc.
This document is subject to change without notice, and PeopleSoft, Inc. does not warrant
INTERNAL
that the material contained in this document is free of errors. Any errors found in this
document should be reported to PeopleSoft, Inc. in writing.
PeopleTalk and “People power the internet.” are trademarks; and PeopleSoft, the
PeopleSoft logo, PeopleTools, PS/nVision, PeopleCode, PeopleBooks, Vantive, Vantive
USE
Enterprise and Red Pepper are registered trademarks of PeopleSoft, Inc. All other
trademarks mentioned in this document are the property of their respective owners.
ONLY!
CONTENTS
Preface PeopleTools I.....................................................................................................................ix

Typographical Conventions and Visual Cues ....................................................................ix
Related Documentation .......................................................................................................x
Lesson 1 Course Overview ...............................................................................................................1
FOR
Course Objectives ...............................................................................................................1
Agenda: ...............................................................................................................................2
Lesson 2 Technology Overview........................................................................................................7
INTERNAL
Describing PeopleSoft Application Development Methodology ........................................8
Describing the PeopleSoft Application Designer..............................................................13
Finding Information About PeopleSoft Application Designer in PeopleBooks................16
USE
Lesson 3 Navigating PeopleSoft Applications...............................................................................19
Navigating PeopleSoft Applications .................................................................................20
Activity 1: Using Basic Navigation Tools........................................................................26
Using Search Pages ...........................................................................................................27
ONLY!
Activity 2: Using Search Pages .....................................................................................34
Identifying Definitions ......................................................................................................35
Entering and Modifying Data ...........................................................................................42
Activity 3: Entering Data...............................................................................................47
Finding Information Using PeopleBooks..........................................................................48
Activity 4: Finding Information Using PeopleBooks........................................................51
Lesson 4 Explaining PeopleSoft Architecture ..............................................................................53

Describing PeopleSoft Databases......................................................................................54
Activity 5: Examining PeopleSoft Databases............................................................59
Explaining Data Transfer in PeopleSoft Internet Architecture .........................................60
Activity 6: Explaining Data Transfer in PeopleSoft Internet Architecture ..............68
Identifying Requirements for the Development Environment ..........................................69
Activity 7: Identifying Requirements for the Development Environment ...............73
Lesson 5 Organizing Data ..............................................................................................................75

Normalizing Data ..............................................................................................................76
Describing Relational Data Models ..................................................................................77
Activity 8: Normalizing Flat Data.............................................................................83
Reading Data Models ........................................................................................................84
Lesson 6 Validating Data................................................................................................................91
Describing Prompt Tables .................................................................................................92
Using Effective Dating......................................................................................................94
PeopleSoft Proprietary and Confidential iii

PeopleTools I Contents
Activity 9: Using Effective Dating..........................................................................103

Comparing Validation Types ..........................................................................................104
Activity 10: Viewing and Entering Prompt Values...................................................107
Explaining Tableset Sharing ...........................................................................................108
Activity 11: Determining Validation Strategies ........................................................110
Lesson 7 Developing Applications by Using the Eight Steps.....................................................113

Describing the PeopleSoft Application Development Process........................................114
Describing the PeopleSoft Application Designer Interface.............................................117
Activity 12: Using the PeopleSoft Application Designer..........................................119
Organizing Definitions in a Project.................................................................................120
Lesson 8
Activity 13:
FOR
Organizing Definitions in a Project.......................................................125
Designing the Application.............................................................................................127

Planning the Application .................................................................................................128
Activity 14:
INTERNAL
Choosing Design Participants ...............................................................130
Determining Functional Specifications ...........................................................................131
Activity 15: Determining Functional Specifications .................................................133
Lesson 9
USE
Determining Technical Specifications ............................................................................134
Describing the Training Application ...............................................................................138
Defining Fields ...............................................................................................................141
ONLY!
Discussing Fields in PeopleSoft Applications.................................................................142
Identifying Field Definition Types and Properties ..........................................................145
Activity 16: Examining Field Definitions .................................................................152
Creating Field Definitions ...............................................................................................153
Activity 17: Creating Field Definitions for the Course Application .........................155
Assigning Translate Values.............................................................................................156
Activity 18: Creating Translate Values .....................................................................160
Activity 19: Creating Field Definitions.....................................................................161
Lesson 10 Creating Record Definitions.........................................................................................163

Explaining Record Definitions........................................................................................164
Accessing Record Definition Displays............................................................................166
Accessing Record Definitions Displays ..........................................................................168
Activity 20: Accessing Record Definitions Displays ................................................169
Configuring Record Definition Properties ......................................................................170
Activity 21: Examining Record Definition Properties ..............................................174
Configuring Record Field Use Properties .......................................................................175
Activity 22 Configuring Record Field Use Properties .............................................184
Configuring Record Field Edits Properties .....................................................................185
Activity 23: Examining Record Field Edits Properties .............................................190
Creating a Record Definition ..........................................................................................191
Activity 24: Creating a Record Definition ................................................................194
Activity 25: Creating the T1_COURSE_MATL Record Definition.........................195
iv PeopleSoft Proprietary and Confidential

Contents PeopleTools I
Building SQL Tables .....................................................................................................197

Lesson 11
Describing the Relationship Between Record Definitions and Application Data
Tables ..............................................................................................................................198
Activity 26: Analyzing PeopleSoft Tables ................................................................201
Building Application Data Tables ...................................................................................202
Activity 27: Building Application Data Tables.........................................................209
Viewing Table Indexes....................................................................................................210
Activity 28: Viewing Indexes in a Table...................................................................212
Activity 29: Building the PS_T1_COURSE_MATRL Table ...................................213
Lesson 12 Creating Page Definitions .............................................................................................215
FOR
Identifying Page Design Principles .................................................................................216
Identifying Page and Page Control Properties.................................................................224
Activity 30: Identifying Page and Page Control Properties ......................................239
Activity 32:
INTERNAL
Adding Page Controls to a Page......................................................................................240
Activity 31: Adding Page Controls to a Page............................................................248
Creating Page Definitions ...............................................................................................249
Creating Page Definitions .....................................................................258
Activity 34:
USE
Implementing Scroll Areas and Grids .............................................................................259
Activity 33: Implementing Scroll Areas....................................................................268
Implementing Scroll Areas and Grids ...................................................269
Activity 36:
ONLY!
Finalizing Page Design and Layout.................................................................................270
Activity 35: Finalizing Page Design and Layout ......................................................275
Building the Course Materials Page......................................................276
Lesson 13 Defining Components....................................................................................................279

Identifying Component Definition Basics.......................................................................280
Activity 37: Identifying Component Definition Basics.............................................291
Defining General and Use Properties ..............................................................................292
Defining Internet Properties ............................................................................................296
Building New Components .............................................................................................300
Activity 38: Building a Component Definition .........................................................304
Activity 39: Building the T1_COURSE_MATL Component...................................305
Lesson 14 Registering Components...............................................................................................307

Explaining Component Registration ...............................................................................308
Examining Menu Definitions ..........................................................................................310
Activity 40: Examining Menu Definitions ................................................................313
Identifying PeopleSoft Security Basics ...........................................................................314
Activity 41: Identifying PeopleSoft Security Basics.................................................321
Navigating the Portal Registry ........................................................................................322
Activity 42: Navigating the Portal Registry ..............................................................326
Planning Component Registration...................................................................................327
Registering the Component .............................................................................................333
Activity 43: Registering the Component...................................................................337
PeopleSoft Proprietary and Confidential v

Activity 44: Registering the T1_COURSE_MATL Component ..............................338
Lesson 15 Testing an Application ..................................................................................................341

Creating and Analyzing Test Plans .................................................................................342
Activity 45: Creating and Analyzing Test Plans .......................................................347
Testing Applications........................................................................................................348
Activity 46: Testing Applications .............................................................................349
Troubleshooting Common Issues ....................................................................................350
Activity 47: Testing More of the Training Application ............................................356
Lesson 16 Editing the Registry Structure .....................................................................................359
Activity 48: FOR

Discussing Content Organization in PeopleTools 8.44 Navigation ................................360
Examining the Portal Registry ..............................................................370
Creating Folders ..............................................................................................................371
Activity 49: Creating Folders in the Portal Registry .................................................375
Activity 50: INTERNAL

Moving Folders or Content References to New Parent Folders......................................376
Moving Folders or Content References.................................................378
Deleting Folders ..............................................................................................................379
Lesson 17
Activity 51:
Activity 52: USE
Deleting Folders in the Portal Registry .................................................381
Working with Folders in the Portal Registry.........................................382
Creating Menu Definitions ...........................................................................................385
ONLY!
Describing the Purpose of a Menu ..................................................................................386
Locating a Component on a Menu ..................................................................................388
Editing Menu Item Labels...............................................................................................390
Activity 53: Editing Menu Item Labels.....................................................................393
Creating Menu Definitions..............................................................................................394
Activity 54: Creating a Menu Definition...................................................................398
Lesson 18 Analyzing the Impact of Design Changes....................................................................401

Determining Relationships Among Definitions ..............................................................402
Activity 55: Determining Relationships Among Definitions ....................................405
Synchronizing Record Definitions and Database Tables ................................................406
Activity 56: Synchronizing Record Definitions and Database Tables ......................411
Incorporating Upgrades in the Development Strategy ....................................................412
Lesson 19 Building Applications....................................................................................................419

Designing an Application................................................................................................420
Activity 57: Designing an Application......................................................................421
Creating Data Structures .................................................................................................422
Activity 58: Creating Data Structures .......................................................................426
Creating User Interfaces..................................................................................................427
Activity 59: Creating User Interfaces........................................................................431
Testing Applications........................................................................................................432
Activity 60: Testing the Application .........................................................................433
vi PeopleSoft Proprietary and Confidential

Contents PeopleTools I
Searching Applications by Using the Verity Search Engine......................................435

Lesson 20
Describing and Performing a Verity Search....................................................................436
Activity 61: Performing a Verity Search...................................................................442
Generating a Registry Search Collection ........................................................................443
Activity 62: Generating a Registry Search Collection ..............................................444
Adding Keywords to a Search Collection .......................................................................445
Activity 63: Implementing a Verity Search Collection .............................................448
Lesson 21 Performing Data Audits................................................................................................451

Discussing Advantages and Disadvantages of Implementing Audits .............................452
Implementing Field Level Audits....................................................................................456
Activity 64:
FOR
Performing a Field-Level Audit ............................................................458
Implementing Record Level Audits ................................................................................459
Activity 65: Implementing Record Level Audits ......................................................467
Lesson 22
INTERNAL
Importing and Exporting Projects...............................................................................469
Describing How Projects Transport Definitions Between Databases .............................470
Exporting Projects ...........................................................................................................474
Activity 66:
USE
Exporting Projects .................................................................................476
Importing Projects ...........................................................................................................477
Activity 67: Importing Projects .................................................................................479
Lesson 23
Lesson 24
Activity 68: ONLY!
Final Course Activity ....................................................................................................481
Creating a Course Evaluation Application............................................482
Course Review ...............................................................................................................483

Completed Objectives .....................................................................................................483
Navigating a PeopleSoft Application ..............................................................................484
Describing the Elements of the PeopleSoft Internet Architecture...................................486
Describing PeopleSoft Data Organization and Validation ..............................................488
Implement the Eight Step Process of Application Development ....................................490
Describing Additional Application Development Considerations ..................................495
Performing Searches and Audits of Application Data ....................................................496
Organizing Definitions into Projects ...............................................................................498
Appendix A Curriculum Map ...........................................................................................................499
PeopleSoft Proprietary and Confidential vii

FOR
INTERNAL
USE
ONLY!
viii PeopleSoft Proprietary and Confidential

Preface
PeopleTools I
Typographical Conventions and Visual Cues

This section discusses:
•
FOR
Typographical conventions.
• Visual cues.
Typographical Conventions INTERNAL

This table contains the typographical conventions that are used in this guide:
Bold
USE
Typographical Convention Description
Indicates PeopleCode function names, method names, language
constructs, and PeopleCode reserved words that must be included
Italics ONLY! literally in the function call.

Indicates field values, emphasis, and PeopleSoft or other book-
length publication titles. In PeopleCode syntax, italic items are
placeholders for arguments that your program must supply.
We also use italics when we refer to words as words or letters as
letters, as in the following: Enter the letter O.
KEY+KEY Indicates a key combination action. For example, a plus sign (+)
between keys means that you must hold down the first key while
you press the second key. For ALT+W, hold down the ALT key
while you press the W key.
Monospace font Indicates a PeopleCode program or other code example.
“ ” (quotation marks) Indicate lesson and chapter titles in cross-references and words that
are used differently from their intended meanings.
. . . (ellipses) Indicate that the preceding item or series can be repeated any
number of times in PeopleCode syntax.
{ } (curly braces) Indicate a choice between two options in PeopleCode syntax.
Options are separated by a pipe ( | ).
[ ] (square brackets) Indicate optional items in PeopleCode syntax.
& (ampersand) When placed before a parameter in PeopleCode syntax, an
ampersand indicates that the parameter is an already instantiated
object.
Ampersands also precede all PeopleCode variables.
PeopleSoft Proprietary and Confidential ix

PeopleTools I Preface
Visual Cues
Training courses contain the following visual cues.
Notes
Notes indicate information that you should pay particular attention to as you work with
the PeopleSoft system.
Note. Example of a note.
If the note is preceded by Important!, the note is crucial and includes information that
concerns what you must do for the system to function properly.
FOR
Important! Example of an important note.
Warnings
INTERNAL
Warnings indicate crucial configuration considerations. Pay close attention to warning
messages.
USE
Warning! Example of a warning.
Cross-References
Training guides provide cross-references either under the heading “See Also” or on a
ONLY!
separate line preceded by the word See. Cross-references lead to other documents, such
as PeopleBooks, that are pertinent to the immediately preceding documentation.
Example:
Example of cross-reference to a PeopleBook
Related Documentation
PeopleSoft applications are documented in PeopleBooks, which are delivered on the
PeopleBooks CD-ROM. You can also order printed, bound versions of PeopleBooks
through the Documentation section of the PeopleSoft Customer Connection website. You
can find updates and additional documentation for each release on the PeopleSoft
Customer Connection website.
See Also
PeopleSoft Customer Connection, http://www.peoplesoft.com/corp/en/login.asp
x PeopleSoft Proprietary and Confidential

Lesson 1
Course Overview
Course Objectives
•
FOR
By the end of this course, you will be able to:
Describe PeopleSoft application design and the technology behind this process.
• Navigate a PeopleSoft application.
•
INTERNAL
Describe the elements of the PeopleSoft Internet Architecture.
Describe PeopleSoft data organization and validation.
•
USE
Implement the eight steps of application development.
Describe additional application development considerations.
• ONLY!
Perform searches and audits of application data.
Organize definitions into projects.
• Demonstrate competence in PeopleSoft application development methodology.
Slide 3 ________________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
PeopleSoft Proprietary and Confidential 1

Course Overview Lesson 1
Agenda: Day One

On day one, we will provide an overview of the course content and discuss these topics:
• Navigating PeopleSoft Applications.
• Describing the PeopleSoft Internet Architecture.
• Organizing Data.
•
Validating Data.
FOR
Implementing the Eight Steps of PeopleSoft Application Development.
Slide 4 ________________________________________________________________________________________________________
Student Notes INTERNAL

______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
2 PeopleSoft Proprietary and Confidential

Lesson 1 Course Overview
Agenda: Day Two

On day two, we will discuss these topics:
• Designing the Application.
• Creating Field Definitions.
• Creating Record Definitions.
FOR
Building the Table.
Slide 5 ________________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Agenda: Day Three

On day three, we will discuss these topics:
• Creating Page Definitions.
• Creating Component Definitions.
• Registering the Component.
FOR
Testing the Application.
Slide 6 ________________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 1 Course Overview
Agenda: Day Four

On day four, we will discuss these topics:
• Editing the Registry.
• Creating Menu Definitions.
• Describing Design Considerations and Impact Analysis.
FOR
Reviewing Application Development.
Slide 7 ________________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Agenda: Day Five

On day five, we will discuss these topics:
• Describing the Verity Search Engine.
• Performing Data Audits.
• Importing and Exporting Projects.
FOR
Final Course Activity.
Slide 8 ________________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 2
Technology Overview
Objectives
•
FOR
By the end of this lesson, you will be able to describe:
PeopleSoft application development methodology
• PeopleSoft Application Designer
• INTERNAL
Find information about the PeopleSoft Application Designer in PeopleBooks.
Slide 10 _______________________________________________________________________________________________________
Student Notes USE

______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Technology Overview Lesson 2
Describing PeopleSoft Application Development Methodology

PeopleSoft application development is a four-phase process that introduces you to
creating applications in the PeopleSoft environment. The phases are:
• Planning the application
• Building the data structures
• Building the user interface
•
FOR
Testing the application
Slide 11 _______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 2 Technology Overview
Describing PeopleSoft Application Development Methodology (continued)

Phase 1, the planning phase, is the most important phase of development. Elements of
planning include:
• Design analysis
• Fit-gap analysis
• Cost analysis
•
Resource analysis
Contingency analysis
FOR
INTERNAL
Slide 12 _______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


In phase 2, the data design phase, you begin building the data structures phase. Elements
of data design include:
• Create field definitions
• Create record definitions
• Build SQL tables
FOR
Slide 13 _______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


In phase 3, the user interface phase, you begin building the user interface structures.
Elements of user interface phase include:
• Create page definitions
• Create component definitions
• Set up user navigation
•
FOR
Set up user security
Slide 14 _______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


In phase 4, the testing phase, you verify the data structures and user interface. Elements
of data design include:
• Verify navigation
• Verify security
• Enter and verify data
FOR
Slide 15 _______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Describing the PeopleSoft Application Designer

Use the PeopleSoft Application Designer to complete most development tasks in a
PeopleSoft environment. The Application Designer performs many development tasks
including:
• Creating all definitions used in a PeopleSoft environment.
• Creating PeopleCode programs.
• FOR
Creating Application Engine programs.
Creating internet workflow.
• Integrating products.
INTERNAL
Slide 16 _______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Describing the PeopleSoft Application Designer (continued)

Some development tasks that you do not perform in the Application Designer are:
• Setting up Definition Security
• Creating queries
• Creating SQR programs
• FOR
Modifying COBOL programs
Running PeopleSoft Data Mover scripts
Slide 17 _______________________________________________________________________________________________________

______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Describing the PeopleSoft Application Designer (continued)

In this course, you use the PeopleSoft Application Designer to complete each of your
development requirements. You will use the PeopleSoft Application Designer to:
• Create field definitions.
• Create record definitions.
• Build the SQL tables.
•
FOR
Create page definitions.
Create component definitions.
• INTERNAL
Set up component navigation.
Set up user security.
Slide 18 _______________________________________________________________________________________________________
Student Notes USE

ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Finding Information About PeopleSoft Application Designer in

PeopleBooks
Use the PeopleTools 8.44 PeopleBook: PeopleSoft Application Designer to find
development information including:
• Information for planning application development.
• Information for creating data structures.
• FOR
User Interface design and implementation.
Appendixes.
Slide 19 _______________________________________________________________________________________________________

This table lists the locations of additional information in the PeopleTools 8.44
Using PeopleSoft
USE
PeopleBook: PeopleSoft Application Designer:
Location Type of Information

This chapter provides general usage information.
Application
Designer
Development
chapters
ONLY!These chapters discuss development concepts and tasks:
• “Working With Projects”
• “Creating Field Definitions”
• “Creating Record Definitions”
• “Building SQL Tables and Views”
• “Creating Page Definitions”
• “Using Page Controls”
• “Creating Component Definitions”
• “Using Registration Wizard”
Appendixes The appendixes provide reference information about the reports and workflows that
are delivered with the system.
You can access related material by clicking the Help link in the top, right corner of the
application page. This automatically takes users to the relevant information in the
appropriate PeopleBook.
Note. Context-sensitive help is constrained to non-application specific pages in the

technical database.

Finding Information About PeopleSoft Application Designer in

PeopleBooks (continued)
The following PeopleBooks contain information that applies to PeopleSoft Application
Designer 8.44 and application development using PeopleTools:
• PeopleTools 8.44 PeopleBook: PeopleSoft Application Designer
• PeopleTools 8.44 PeopleBook: Security Administration
•
FOR
PeopleTools 8.44 PeopleBook: Internet Technology
PeopleTools 8.44 PeopleBook: PeopleCode Developer's Guide
Slide 20 _______________________________________________________________________________________________________

This table describes the additional PeopleBooks that contain information about
USE
PeopleSoft Application Designer and application development using PeopleTools.
PeopleBook
PeopleTools 8.44 PeopleBook:
Description
This PeopleBook describes the fundamental elements of developing
ONLY!
PeopleSoft Application Designer
PeopleTools 8.44 PeopleBook:
Security Administration
applications for PeopleSoft Internet Architecture.
This PeopleBook describes the interface, tables, and other components
associated with PeopleSoft security and how you can use them to
secure pages, fields, and other definitions.
PeopleTools 8.44 PeopleBook: This PeopleBook describes PeopleTools internet technology,
Internet Technology including PeopleSoft Internet Architecture (PIA) and PeopleTools
portal technology used for creating and managing portals.
PeopleTools 8.44 PeopleBook: This PeopleBook covers the concepts of PeopleCode, tips for using
PeopleCode Developer's Guide PeopleCode, the interaction of PeopleCode and the Component
Processor, and a number of other specialized topics, such as the use of
the PeopleCode debugger and referencing data in the component
buffer.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Review
In this lesson, you learned that:
• The PeopleSoft application design methodology creates a framework for

development.
• The PeopleSoft Application Designer is the primary tool for application development
in a PeopleSoft environment.
•
FOR
You can find information about the PeopleSoft Application Designer in a variety of
PeopleBooks.
Slide 21 _______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 3
Navigating PeopleSoft
Applications
Objectives
FOR
By the end of this lesson, you will be able to:
• INTERNAL
Navigate PeopleSoft applications.
Use search pages.
• Identify definitions.
•
USE
Enter and modify data.
Find information using PeopleBooks.
ONLY!
Slide 23 _______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Navigating PeopleSoft Applications Lesson 3
Navigating PeopleSoft Applications

To sign in to a PeopleSoft application, you need three things:
• A URL
• A valid user ID
• The correct password for the user ID
FOR
Slide 24 _______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 3 Navigating PeopleSoft Applications
Navigating PeopleSoft Applications (continued)

After signing in, the homepage appears in the browser. The homepage contains three
major areas:
• The menu pagelet, a hierarchy of folders and content references.
• The header, which contains quick access to navigational aids.
• The target area, which displays content.
FOR
Slide 25 _______________________________________________________________________________________________________
Student Notes
INTERNAL
Use the homepage to display the navigation area, header, and target area.
USE
ONLY!
PeopleSoft homepage
See Also
PeopleTools 8.44 PeopleBook: Internet Technology, “Administering Portal Homepages
and Pagelets”


Two elements make up the navigation:
• Folders.
• Content references.
Slide 26 _______________________________________________________________________________________________________
Student Notes
FOR
Use the menu pagelet to navigate using folders and content references.
INTERNAL
USE
ONLY!
The menu pagelet
See Also
PeopleTools 8.44 PeopleBook: Internet Technology, “Administering Portal Homepages
and Pagelets”
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


You can define content that you use often as a favorite. There are
• PeopleSoft favorites.
• Browser favorites or bookmarks.
Slide 27 _______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


PeopleSoft favorites are different from browser favorites or bookmarks.
Browser Favorites PeopleSoft Favorites

You can access them at any time. You must sign in to access them.
They are stored on a local hard disk. They are stored in the portal database.
They are limited to a single computer and cannot be They stay with a user ID in the database and can be
accessed from different locations. accessed from any browser after signing in.
PeopleSoft user ID. FOR

Any users can see the same favorites, regardless of Favorites are stored by user ID.
Slide 28 _______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Another method of navigation is through the search feature on the homepage. To use the
search feature:
1. Type the word that you want to search.
2. Click the Go button.
3. Select the link that best suits your needs.
FOR
Slide 29 _______________________________________________________________________________________________________
Student Notes
INTERNAL
Use the Search page as an alternate means of navigation.
USE
ONLY!
Search page
See Also
PeopleTools 8.44 PeopleBook: Internet Technology, “Understanding PeopleSoft Portal
Technology ”

Activity 1: Using Basic Navigation Tools

In this activity, you will read the activity overview and:
1. Sign in.
2. Use content references to load components.
3. Create PeopleSoft favorites.
4. Navigate with searches.
FOR
See PeopleTools I: Activity Guide, lesson 3, “Navigating PeopleSoft Applications,”
Activity 1: Using Basic Navigation Tools.
INTERNAL
Slide 30 _______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Using Search Pages

You have already seen a number of search pages; they appear when you click on most
content references in navigation. Search pages:
• Enable users to find the data they are interested in viewing.
• Are an interim step between content reference and component.
• Allow the user to select from a list of data rows.
•
FOR
Are dynamically built based on several definition properties.
Slide 31 _______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Using Search Pages (continued)

Depending on how you configure a component, you may see:
• A basic search page.
• An advanced search page.
Slide 32 _______________________________________________________________________________________________________
Student Notes
FOR
Use this page to do a basic search for student information.
Page Name Navigation
INTERNAL
Personal Information
Personal Information
Students, Personal Information
Click the Basic Search link.
USE Click the Advanced Search link.
ONLY!
Use the basic search page to find the row of data that you need.
Basic search page for Student Personal Information
• Use the advanced search page to further constrain the rows of data you need.

FOR
INTERNAL
USE
Advanced search page for Student Personal Information
See Also ONLY!

PeopleTools 8.44 PeopleBook: Using PeopleSoft Applications, “Using Keys and Search
Pages”
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


The search fields that appear on the page are determined in the record definition. They
are termed
• Search keys.
• Alternate search keys.
Slide 33 _______________________________________________________________________________________________________
Student Notes
FOR
Use the Record Field properties dialog to select search properties.
Dialog Name
INTERNAL
Record Field Properties
Navigation
File, Open,
Select Record in the Definition field.
USE Select a record.

Double click a field
ONLY!
Record field properties
See Also
PeopleTools 8.44 PeopleBook: PeopleSoft Application Designer, “Working with
Records”

Pages”
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


You can create custom searches. These searches:
• Are stored by userID.
• Are available on the Advanced Search page only.
• Are available for use in other search pages that use the same search record.
FOR
Slide 34 _______________________________________________________________________________________________________
Student Notes
Use the following navigation path to access this page:
Page Name
INTERNAL
Save Search As
Navigation
Click the Save Search Criteria link.
•
USE
Use the Save Search page to save search criteria that is used often.
ONLY!
Save Search As page
See Also
Pages”


There are four steps to creating a saved search:
1. Enter search criteria on a search page.
2. Click the Save Search Criteria link.
3. Enter a name for the search.
4. Click the Save button.
FOR
Slide 35 _______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 2: Using Search Pages

In this activity, you will read the activity overview and use the search page to locate data
in the application.

Activity 2: Using Search Pages.
Slide 36 _______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Identifying Definitions
The PeopleSoft user interface is made up of several element types, all of which you must
understand in depth to develop in the PeopleSoft environment. This section discusses:
• Definition basics.
• Component definitions.
• Page definitions.
•
Field definitions.
Definition names.
FOR
INTERNAL
Slide 37 _______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Identifying Definitions (continued)

Definitions make up the PeopleSoft user interface:
Navigation Security
Component
Page 1
FOR Page 2
INTERNAL
Record Record
Field A
Field BUSE Field E
Field F
ONLY!
Field C Field G
Field D Field H
Interdependent PeopleSoft definitions
Slide 38 _______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


The component definition is central to the user interface. Component definitions
determine:
• The search page.
• The toolbar buttons at the bottom of the screen.
• The mode of the component – update/display, history, or correction.
•
FOR
The pages that you access.
Page tabs or hyperlinks.
INTERNAL
Slide 39 _______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


The page defines what the user sees.
• Each component can hold multiple pages.
• Tabs at the top of the screen enable access to each page.
• Pages contain fields.
•
FOR
Levels segment pages.
All pages include a level 0, and many have other levels as well.
Level 0 contains the highest-level key values that make a row of data unique.
•
INTERNAL
Level 0 key values are entered once, when a new row is created.
A scroll area or a grid, if they exist, binds other levels.
USE
Slide 40 _______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Fields hold the data entered into the application database.
• Fields on a page hold data that you save to tables in the database.
• Fields support many data types.
• Fields can be interactive or display-only.
FOR
Slide 41 _______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Pages can contain many different field types represented by different controls including:
• Edit boxes.
• Drop down list boxes.
• Check boxes.
•
Radio buttons.
Images. FOR
Slide 42 _______________________________________________________________________________________________________

______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


From any component in the application, use CTRL + J to see an information page that
includes the names of the component definitions that make up the interface.
Slide 43 _______________________________________________________________________________________________________
Student Notes
Use CTRL + J to see an information page showing the interface’s component definitions.
Page Name
Personal Details
FORNavigation
Instructors, Professional Details
Select an instructor.
INTERNAL Press CTRL + J.
USE
ONLY!
Information displayed with CTRL+ J keyboard combination
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Entering and Modifying Data

Components include a series of buttons at the bottom of the screen.
• Save.
• Return to Search.
• Next/Previous in List.
•
Add.
Update/Display.
Show History.
FOR
•
INTERNAL
Correct History.
Slide 44 _______________________________________________________________________________________________________
Student Notes
USE
Configure these buttons in the component:
Component toolbar
ONLY!
See Also
PeopleTools 8.44 PeopleBook: PeopleSoft Application Designer, “Creating Component
Definitions”
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Entering and Modifying Data (continued)

If you prefer keystrokes to mouse clicks, there are keyboard alternatives for buttons and
other actions:
• Hot keys perform an action immediately.
• Access keys change the cursor focus to a button; you must press Enter to complete
the command.
FOR
Slide 45 _______________________________________________________________________________________________________
Student Notes
For an online list of hot keys and access keys, press CTRL + K on the keyboard.
See Also INTERNAL

PeopleTools 8.44 PeopleBook: Using PeopleSoft Applications, “Working with Browser-
Based Applications”
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


When you add new rows of data for an entire component, you start by entering a new
high-level (level 0) key value. You add a new level 0 value from either:
• The search page
• The component
Slide 46 _______________________________________________________________________________________________________
Student Notes
FOR
Page Name
Search page INTERNAL
Personal Details
Navigation
•
USE
Use the search page to add a new value.
ONLY!
Personal Information search page
• Use the Add button on the Personal Details page to add a new value.

FOR
INTERNAL
USE
Personal Details page
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


To update existing information or insert new rows at level one:
• Use the insert row button in the scroll area.
• User the insert row button in the grid.
Slide 47 _______________________________________________________________________________________________________
Student Notes
FOR
INTERNAL
Products by Customer
Purchase Order
Customer, Products Purchased
Purchasing, Maintain Purchase Orders
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 3: Entering Data

In this activity, you will read the activity overview and enter your student data in the
database.

Activity 3: Entering Data.
Slide 48 _______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Finding Information Using PeopleBooks

PeopleBooks document PeopleTools and PeopleSoft applications. PeopleBooks offer:
• An integrated user interface as a Help link.
• Context-sensitive assistance where possible; displaying information related to the

screen that you are viewing.
• A navigational taxonomy for locating information.
•
FOR
A text search capability.
Slide 49 _______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Finding Information Using PeopleBooks (continued)

When accessing PeopleBooks:
• You link immediately to the appropriate documentation for the page you are viewing
if context sensitive help exists.
• If no context-sensitive help is available, a page displays linking you back to the

PeopleBooks main menu.
FOR
Slide 50 _______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Finding Information Using PeopleBooks (continued)

You can navigate PeopleBooks in several ways.
• PeopleBooks library
• Verity search
• Contents view
•
Index view
Search view FOR

Slide 51 _______________________________________________________________________________________________________

The PeopleBooks library gives you multiple ways to access information:
USE
ONLY!
PeopleBooks library
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 4: Finding Information Using PeopleBooks

In this activity, you will read the activity overview and find information using
PeopleBooks.

Activity 4: Finding Information Using PeopleBooks.
Slide 52 _______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Review
In this lesson, you learned that
• You navigate a PeopleSoft application by clicking on folders to find a content

reference.
• A search page presents you with options for finding the data that you want.
• PeopleSoft definitions are interdependent.
•
FOR
You add high-level information at level 0 but you insert subordinate data at other
levels.
• PeopleBooks provide multiple ways of searching for information about an
INTERNAL
application.
Slide 53 _______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 4
Explaining PeopleSoft
Architecture
Objectives
FOR
• INTERNAL
Describe PeopleSoft databases.
Explain data transfer in PeopleSoft Internet Architecture.
• Identify requirements for the development environment.
USE
Slide 55 _______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Explaining PeopleSoft Architecture Lesson 4
Describing PeopleSoft Databases

Tables in PeopleSoft databases fall into three general areas:
System Catalog
PeopleTools
FOR
INTERNAL
Application Data
Three categories of tables
USE
Slide 56 _______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 4 Explaining PeopleSoft Architecture
Describing PeopleSoft Databases (continued)

System catalog tables contain the database metadata and:
• Track all objects in the entire database.
• Are analogous to a table of contents.
• Vary based on the platform.
FOR
Slide 57 _______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


The PeopleTools tables contain metadata about the PeopleSoft application installed on
the database. PeopleTools tables:
• Have consistent structure between applications.
• Vary in content between applications.
• Have their content modified by PeopleTools such as PeopleSoft Application
•
Designer.
FOR
Are converted to HTML, delivered to browser.
• Use the naming convention PS*, for example, PSPNLDEFN.
INTERNAL
Slide 58 _______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Application data tables hold the data that users enter into the database:
• Specific tables are determined by application.
• Developers can create more.
• Content is modified through the user interface.
FOR
Tables use the naming convention PS_, for example, PS_CUSTOMER_TBL.
Slide 59 _______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


You can use a query tool to examine the contents of the tables, but do not change the
contents outside of the approved tools because the PeopleTools tables and the application
data table could become unsynchronized.
Slide 60 _______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 5: Examining PeopleSoft Databases

In this activity, you will review the activity overview and examine the contents of the
classroom database.
See PeopleTools I: Activity Guide, lesson 4, “Explaining PeopleSoft Architecture,”

Activity 5: Examining PeopleSoft Databases.
Slide 61 _______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Explaining Data Transfer in PeopleSoft Internet Architecture

The architecture behind PeopleSoft Internet Architecture takes the raw data from the
application database and delivers it in the form of an interactive user interface on a
standard web browser. Components of PeopleSoft Internet Architecture are:
• Browsers as clients.
• Web servers.
•
Application servers.
Database servers. FOR

Slide 62 _______________________________________________________________________________________________________

______________________________________________________________________
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Explaining Data Transfer in PeopleSoft Internet Architecture (continued)

With PeopleSoft Internet Architecture, users do their work with a browser; no code is
required on the client. Advantages to delivering the user interface on a browser include:
• Easy access.
• Platform independence.
• Low bandwidth access.
•
FOR
Simple application maintenance and deployment.
Slide 63 _______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


This diagram illustrates that the client does not have native capabilities to display
database content:
Database
Server
Browser
System Catalog
HTML 4
FOR PeopleTools
Application Data
Compatible
Browser
Browser and database server INTERNAL

Slide 64 _______________________________________________________________________________________________________
Student Notes USE

ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


This graphic illustrates how a web server acts as the front end of PeopleSoft Internet
Architecture, delivering the HTML that the browser displays:
Database
Web Server Server
Browser
System Catalog
HTML
HTML 4
FOR
Web Services
PeopleTools
Application Data
Compatible
Browser
INTERNAL
USE
The HTML connection between the browser and the web server
Slide 65 _______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


As seen in this diagram, the application server completes the connection, managing
communication with the database and delivering HTML to the web server for display:
Application Database
Web Server Server Server
Browser
SQL System Catalog

HTML PeopleSoft
HTML 4
FOR
Web Services
Services
PeopleTools
Application Data
Compatible
Browser
INTERNAL
Java Servlets
Jolt
Tuxedo/Jolt
USE
The application server communicates with the web server and the database
Slide 66 _______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


When developing for PeopleSoft Internet Architecture interfaces, you must consider
issues that are not present in other prior releases:
• No code runs on the client.
• All code runs on the application server.
• Running code requires a server trip and a browser refresh.
FOR
Slide 67 _______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Deferred processing is one possible solution to limit server trips. With deferred
processing:
• User actions and processed as a single batch.
• Processing normally takes place when user saves work.
• You can specify when you want the server to process.
•
FOR
User experience is a large factor in its success.
Slide 68 _______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Multi-row insert is another development option to limit server trips. Multi-row
processing:
• Is used when entering multiple rows of data.
• Enables the user to enter the number of data rows to insert.
• Holds the data in the component buffer until you save the component.
FOR
Slide 69 _______________________________________________________________________________________________________
Student Notes
Page Name
INTERNAL
Use this page to insert multiple rows:
Navigation
Purchase Orders Purchasing, Maintain Purchase Orders
USE
ONLY!
Purchase Orders page
See Also
PeopleTools 8.44 PeopleBook: PeopleSoft Application Designer, “Guidelines for
Designing Pages”
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 6: Explaining Data Transfer in PeopleSoft Internet

Architecture
In this activity, you will review the activity overview and:
• Enter data on a page that defers processing.
• Enter data on a page that does not defer processing.
• Enter data on a page that includes a multi-row insert capability.
FOR
See PeopleTools I: Activity Guide, lesson 4, “Explaining PeopleSoft Architecture,”
Activity 6: Explaining Data Transfer in PeopleSoft Internet Architecture.
Slide 70 _______________________________________________________________________________________________________

USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Identifying Requirements for the Development Environment

The development environment primarily consists of the PeopleSoft Application Designer
and:
• Is installed on the Windows client with the installation of PeopleTools.
• Manipulates data in the PeopleTools tables on the database.
• Connects to the database directly or by means of an application server.
FOR
Slide 71 _______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Identifying Requirements for the Development Environment (continued)

This diagram shows the way that the two types of development workstations fit into the
architecture:
Development
System (2-Tier)
HTML
Development
HTML
FOR
System (3-Tier)
SQL
INTERNAL
System Catalog
USE PeopleSoft SQL

Web Services
Services
Tuxedo PeopleTools
Application Data
ONLY!
Java Servlets
Jolt
Tuxedo/Jolt Database
Server
Web Server Application

Server
Two-tier and three-tier connections
Slide 72 _______________________________________________________________________________________________________
Student Notes
This table contrasts two-tier and three-tier connections:
Connection Communication Security Connection Simplicity Functionality

Type Protocol Management
Two-tier SQL is inefficient This requires The database You point an Manages all
except when you direct database server manages ODBC tasks.
connect to a fast connectivity. this connector to
local network. There is connection. the database.
potential for This can slow
security performance
violations. when you
make multiple
connections.

Connection Communication Security Connection Simplicity Functionality

Type Protocol Management
Three-tier BEA Tuxedo and The The application You must Does not
TCP/IP are fast, connection is server manages configure an execute
especially over a managed by this application PeopleSoft
WAN. the application connection. server. Data Mover
server. There The database commands or
is less server has to perform
exposure to manage only PeopleSoft
security the connection Application
violations. to the Designer
application upgrades.
server.
FOR
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Identifying Requirements for the Development Environment (continued)

Unlike in previous releases of PeopleTools, developers need access to the entire
PeopleSoft Internet Architecture setup to test their work as this diagram illustrates:
Windows Client Windows Client

(3-Tier) (2-Tier)
FOR SQL
Browser
INTERNAL
Web Server Tuxedo
Application
Server
Database
Server
System Catalog
USE
HTML PeopleSoft SQL
Web Services
Services
PeopleTools
HTML 4
Application Data
ONLY!
Compatible
Browser
Java Servlets Tuxedo/Jolt
Jolt
PeopleSoft Internet Architecture
Slide 73 _______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 7: Identifying Requirements for the Development

Environment
In this activity, you will review the activity overview and identify terms
See PeopleTools I: Activity Guide, “PeopleSoft Architecture,” Activity 7: Identifying

Requirements for the Development Environment.
Slide 74 _______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Review
• A PeopleSoft database consists of three types of tables: System catalog tables,

PeopleTools tables, and application data tables.
• PeopleSoft Internet Architecture transfers data from the database to the application
server where it is transformed to HTML that is assembled by the web server and
presented to the user on a browser.
•
FOR
Development environments require either a direct ODBC connection or an
application server connection to the database.
Slide 75 _______________________________________________________________________________________________________

______________________________________________________________________
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 5
Organizing Data
Objectives
• Normalize data.
FOR
• Describe relational data models.
• INTERNAL
Read data models.
Slide 77 _______________________________________________________________________________________________________
Student Notes USE

______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Organizing Data Lesson 5
Normalizing Data
The process of organizing data into logically related tables is called normalization. The
goal of normalization is to ensure that data is never entered in two places. Normalization:
• Can lead to complex designs.
• Often requires compromise, trading complexity for redundancy.
• Has several standard levels of normalization.
FOR
Slide 78 _______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 5 Organizing Data
Describing Relational Data Models

Because relational databases are used in a variety of contexts, RDBMS terminology
includes multiple expressions for the same element. This table lists some of these
expressions:
PeopleSoft Terms Equivalent Terms

Table File, set
Row Record, occurrence, entry, line
Column
RDBMS terminology FOR Field, item, data element, attribute
Slide 79 _______________________________________________________________________________________________________

USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Describing Relational Data Models (continued)

Relational data modeling has three basic goals:
• Minimize data redundancy.
• Promote efficient retrieval of data.
• Maximize flexibility.
FOR
Slide 80 _______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


This is an example of non-relational data about Mark Larsen:
Name Address Company Degree Skill Level

Larsen,Mark 1776 Mt. Diablo XYZ Corp AAS CSA M
Larsen,Mark 1776 Mt. Diablo XYZ Corp MBA DBD M
Larsen,Mark 1776 Mt. Diablo XYZ Corp DUP H
Larsen,Mark
Larsen,Mark
FOR
1776 Mt. Diablo
1776 Mt. Diablo
XYZ Corp
XYZ Corp
PT
SQL
H
M
Slide 81 _______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Through normalization, relational database models separate data into tables that are
related to one another:
• Key structure establishes links between tables.
• There are two types of relationships: Parent/child and prompt.
• Keys play a role in both relationship types.
FOR
Slide 82 _______________________________________________________________________________________________________
Student Notes
Parent/Child
INTERNAL
This table defines common terms that are used in relational databases:
The parent table stores basic information related to the

high-level key. Child tables use a complex key structure;
Prompts
USE they share the same high-level key with the parent and
include at least one additional key.
The key from the prompt table is stored in the prompting
table. This is a form of data validation. In other databases,
ONLY! this is often called a foreign or candidate key.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


To understand table relationships in a PeopleSoft application, you need to know these
terms:
• Search key
• High level key
• Prompt table
•
Parent table.
Child table
FOR
INTERNAL
Slide 83 _______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


This diagram shows a prompt table, a parent table, and a child table.
T1_CUST_TBL (Prompt)
Key
CUSTOMER_ID DESCR DESCR_SHORT
CONS Consulting Services Cons Srvs
LSL LoneStar Longhorn Cattle Co. LoneStar
PSU_STUDENT_TBL (Parent) XYZ XYZ Corporation XYZ
Key
2003
XYZ
Bechingham,Carol CONS
FOR
STUDENT_ID STUDENT_NAME CUSTOMER_ID EMPHASIS
2001 Larsen,Mark D F
T
INTERNAL
2020 Carson,Kitty LSL T
PSU_STUDENT_EXP (Child)
Key Key
STUDENT_ID SKILL PROFICIENCY
2001 CSA M
2001
2001
2001
2001
DBD
DUP
PT
SQL
USE M
H
H
M
ONLY! PSU_STUDENT_ED (Child)
Key
2001 AAS
Key (Duplicate)
STUDENT_ID DEGREE SCHOOL_CODE MAJOR
NC0001 Business Management
2001 MBA MA1000 Business Administration
Prompt table, parent table, and child table
Slide 84 _______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 8: Normalizing Flat Data

In this activity, you will review the activity overview and normalize flat data.
See PeopleTools I: Activity Guide, lesson 5, "Organizing Data," Activity 8: Normalizing

Flat Data.
Slide 85 _______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Reading Data Models

Data models show the relationships between database tables:
• A conceptual model shows entity names and relationships.
• A physical model is more detailed and includes table names, key structure, and
column names.
• PeopleSoft delivers physical data models for all database applications.
FOR
Slide 86 _______________________________________________________________________________________________________
Student Notes
INTERNAL
You can find data models on Customer Connection at www.peoplesoft.com.
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Reading Data Models (continued)

This diagram shows an example of the physical data model:
PSU_STUDENT_EXP
T1_CUST_TBL PSU_STUDENT_TBL
STUDENT_ID
CUSTOMER_ID STUDENT_ID SKILL
DESCR STUDENT_NAME PROFICEINCY
DESCRSHORT CUSTOMER_ID DATE_LAST_MAINT
CUSTOMER_TYPE EMPHASIS
PHONE SAME_ADDR_CUSTOMER
PSU_ADDRESS_SBR
CONTRACT_DT
TRAINING_UNITS
DESCRLONG
FOR PSU_ADDRESS_SBR
PHONE
PROJECT_ROLE
PSU_STUDENT_ED
STUDENT_ID
DEGREE
SCHOOL_CODE
INTERNAL MAJOR
GPA
GRADUATE_INDICATOR
Physical entity relationship diagram
USE
Slide 87 _______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


This table shows the four types of connection symbols:
For each row A, row B has a minimum of one and a

maximum of one row.
For each row A, row B has a minimum of zero and a
maximum of one row.
FOR For each row A, row B has a minimum of one and a

maximum of many rows (the crow’s foot means many).
For each row A, row B has a minimum of zero and a
maximum of many rows.
INTERNAL
Slide 88 _______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


You read the relationships both ways, from A to B, then B to A. The following diagram
shows these relationships:
PSU_STUDENT_TBL PSU_STUDENT_ED
STUDENT_ID STUDENT_ID
STUDENT_NAME DEGREE
CUSTOMER_ID SCHOOL_CODE
EMPHASIS MAJOR
SAME_ADDR_CUSTOMER
FOR
GPA
PSU_ADDRESS_SBR GRADUATE_INDICATOR
PHONE
PROJECT_ROLE
Connection between two tables
INTERNAL
Slide 89 _______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


PeopleSoft data models are available in Visio, HTML, and PDF formats. Data models:
• Are included on the PeopleBooks installation CD.
• Can be downloaded from PeopleSoft Customer Connection by product line.
Slide 90 _______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Review
• You can normalize data by removing redundancies among tables.
• A relational data model is a diagram that describes how tables in an application are
related.
• In a relational data model, connecting symbols describe the relationships between

tables.
FOR
Slide 91 _______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 6
Validating Data
Objectives
•
FOR
Describe prompt tables.
• Use effective dating.
•
INTERNAL
Compare validation types.
Explain tableset sharing.
USE
Slide 93 _______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Validating Data Lesson 6
Describing Prompt Tables

In a prompt table edit, field values can be filled or edited only from a list of values in the
prompt table. This diagram shows the prompt table PSU_INSTR_TBL filling values for
the Instructor field in the PSU_CRS_SESSN table.
T1_CRS_SESSN
T1_COURSE
T1_SESSN_NBR
BUSINESS_UNIT
PSU_INSTR_TBL
INSTRUCTOR
EFFDT
EFF_STATUS
FOR T1_START_DT
END_DT
T1_MAX_ENROLL
INSTRUCTOR
TRAINING_LOC
T1_CLASSROOM
DESCR
LAST_NAME
FIRST_NAME
INTERNAL
BUSINESS_UNIT
CURR_DEV_FLAG
COURSE_TYPE
FACILITY
PSIMAGEVER
PHOTO USE
Prompt table with values for the Instructor field
ONLY!
Slide 94 _______________________________________________________________________________________________________
Student Notes
Structurally, a prompt table is no different from any other application data table. It stores
values that other tables can validate against.
See Also
PeopleTools 8.44 PeopleBook: PeopleSoft Application Designer, “Creating Record
Definitions”
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 6 Validating Data
Describing Prompt Tables (continued)

The Student page uses the customer table to provide valid values. When you select from
the search results, the key value from the prompt table is written to the field. If you enter
an invalid value, the system warns you and does not allow a save.
Slide 95 _______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Using Effective Dating

Tables containing an effective date (EFFDT) field as a key are called effective-dated
tables. Effective dating:
• Retains historical data.
• Stores data for future use.
Slide 96 _______________________________________________________________________________________________________
Student Notes
FOR
To understand the value of effective dating, here are a few examples of challenges in
trying to maintain historical data or in noting future data changes.
INTERNAL
Example 1: If Bryan Lake were promoted to senior clerk, would there be a record of his
being a clerk?
EMPLID (Key)
1724
USE NAME
Lake,Bryan
TITLE
Clerk
WAGE
10.50
ONLY!
Example 2: If Syndee Edmonds were to take a leave of absence (become an inactive
employee), how will it be recorded?
EMPLID (Key) NAME TITLE WAGE

9442 Edmonds,Syndee Associate 11.25
Example 3: If the product’s price changes at midnight, with the following table structure
you can’t make this happen.
PRODID (Key) DESCR COST RETAIL

100567 Tambourine 12.87 29.99
100568 Cowbell 4.22 11.99
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Using Effective Dating (continued)

These altered table structures solve the challenges:
EMPLOYEE PRODUCT
EMPLID (key) PRODID(key)
EFFDT (key) EFFDT (key)
EFF_STATUS EFF_STATUS
NAME DESCR
TITLE
WAGE FOR COST
RETAIL
Slide 97 _______________________________________________________________________________________________________

These examples allow for the necessary changes:
EMPLID (Key)
USE
Notice the EFFDT field in the Employee table:
EFFDT(Key) EFF_STATUS NAME TITLE WAGE

1724
1724 ONLY!
08/15/2002
05/11/2002
A
A
Lake,Bryan
Lake,Bryan
Clerk, Sr.
Clerk
12.00
10.50
9442 01/01/2004 A Edmonds,Sydnee Associate 11.25
9442 06/01/2002 I Edmonds,Sydnee Associate 11.25
Notice the EFFDT field in the Product table:
PRODID (Key) EFFDT (Key) EFF_STATUS DESCR COST RETAIL

100567 11/01/2002 A Backpack 13.22 32.99
100567 12/01/2000 A Backpack 12.87 29.99
100568 11/01/2002 A Mousepad 5.03 12.49
100568 12/01/2000 A Mousepad 4.22 11.99


Effective-dated tables include three types of rows:
• Future
• Current
• History
FOR
Slide 98 _______________________________________________________________________________________________________
Student Notes
This table defines terms that are used in effective dating:
Future
Current
INTERNAL
The effective date is greater than the current system date.
The effective date is the closest to today, but is not in the future.
History
USE The effective date is less than the current effective date.
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


When entering rows into effective-dated tables, you have four action choices:
• Add
• Update/Display
• Include History
• Correct History
FOR
Slide 99 _______________________________________________________________________________________________________
Student Notes
• INTERNAL
As you do with any other table, you use Add to create a new search key value:
EMPLID EFFDT EFF_STATUS NAME TITLE WAGE

9442
USE
11/28/1996 A Edmonds,Sydnee Associate 11.25
•
ONLY!
Use Update/Display to edit data that is subordinate to an existing search key,
including inserting rows, as shown in this table:

In Update/Display mode, only the current and future rows are available to the user. You
can update the future rows and you can insert any row with an EFFDT greater than the
current row.
• Use Include History to view (but not change) historical data, as shown in this table:

• Use Correct History to view and edit data regardless of effective date, as shown in
this table:



______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


This table summarizes each action mode:
Action Can View Can Insert Can Update

Add NA New high-level key NA
Update/Display Current, future New effective date greater Future only
than the current row
Include History History, current, future New effective date greater Future only
Correct History FOR

History, current, future
than the current row
Any effective date All rows
Slide 100 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Entering data into effective-dated pages is unique. Even though all the data resides on a
single table, the page contains two levels. The current effective date for a given high-
level key is displayed. This design enables you to enter multiple effective dates for each
high-level key. All effective-dated pages follow these rules:
• All rows are categorized as history, current, or future.
• When you insert a new row, data for all fields is copied from the current row.
•
FOR
When prompting to tables that are effective dated, only current, active values are
available.
Slide 101 ______________________________________________________________________________________________________

______________________________________________________________________
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


When a field on a page prompts against an effective-dated table, only current, active
choices appear. There are four possible combinations to consider, as described in this
table:
Table Writing To Prompt Table Behavior

No effective date No effective date All rows retrievable; displays the first 300
rows
No effective date
Effective date
FOR
Effective date
Effective date
Rows categorized against the system date;
current, active rows retrievable
Rows categorized by effective date; current,
active rows retrievable
INTERNAL
Effective date No effective date All rows retrievable; displays the first 300
rows
Slide 102 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


This example shows both tables as effective-dated tables. Consider the following row for
the Department table. The MGR column uses values from the Personal Data table.
FOR
INTERNAL
USE
MGR field prompting to the EMPLID field
Slide 103 ______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 9: Using Effective Dating

• Use effective-dated tables.
• Use prompt tables.
See PeopleTools I: Activity Guide, lesson 6, “Validating Data,” Activity 9: Using

Effective Dating.
FOR
Slide 104 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Comparing Validation Types

In addition to prompt tables, there are other types of validation:
• The translate table (PSXLATITEM) prompt.
• The Yes/No prompt.
Slide 105 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Comparing Validation Types (continued)

Prompt and translate tables provide values for the users to select. However, the fields
they represent differ visually.
This is a summary of prompt and translate table characteristics:
Prompt Table Translate Table

Developers determine table structure. PeopleSoft developers determines table structure.
FOR
Users can access from any field configured to prompt.
Users are taken to a search page to select a value.
Users can maintain values.
Values are tied to a specific field.
Users see a list of descriptions or radio buttons.
Developers maintain values.
Slide 106 ______________________________________________________________________________________________________

The Personal Details page shows every type of prompt:
Page Name
Personal Details
USE Navigation
ONLY!
Personal Details page
See Also
Definitions”

Comparing Validation Types (continued)

Using the translate table for prompts can enhance usability. Users can select a value with
two clicks instead of using the search page. This table shows considerations for when to
use prompt table edit and when to use translate table edit:
Consideration Prompt Table Edit Translate Table Edit

Number of choices Use when there are many choices. Use when there is a short list, 30 or
The lookup page can show up to fewer.
300 lines and can be filtered with
Maintenance FOR search criteria.

Use when prompt values change
often. The prompt table is
Use when the list of choices is
relatively static. The developer
accessible to the users who have enters values as a property of the
INTERNAL
Data structure
security access; users can maintain
values.
Use when more than a description
field definition.
Use when all you need is a

has to be associated with the high- description of the value.
Caching USE level key.

This table is not cached. This table is cached for quick
access.
Slide 107 ______________________________________________________________________________________________________
Student Notes ONLY!

______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 10: Viewing and Entering Prompt Values

in this activity, you will review the activity overview and view and enter prompt values.
See PeopleTools I: Activity Guide, lesson 6, “Validating Data,” Activity 10: Viewing and
Entering Prompt Values.
Slide 108 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Explaining Tableset Sharing

Use tableset sharing to filter prompt table choices based on business rules. In PeopleSoft
applications, a large percentage of the tables are keyed with one of two fields:
• Business Unit
• SetID
Slide 109 ______________________________________________________________________________________________________
Student Notes
FOR
In HCM applications, you will find these fields in many tables, although Business Unit is
not necessarily a high-level key.
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Explaining Tableset Sharing (continued)

Many PeopleSoft applications include prebuilt tableset sharing that filters results by
product line, department, reporting structure, region, and other organizational lines. This
diagram shows prompt values that have been limited by location:
Location Prompt
(USA)
Atlanta
Boston
New York
FORSan Francisco
Atlanta
Boston
Copenhagen Location
Mexico City Prompt
INTERNAL
Location Prompt
(International)
Copenhagen
New York
Paris
San Francisco
Tokyo
Table
USE Mexico City

Paris
Tokyo
Prompt values limited by location
ONLY!
Slide 110 ______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 11: Determining Validation Strategies

In this activity, you will review the activity overview and examine a data model of the
application that you will build in class. You will determine what data validation strategy
to use for a number of prompts, based on the five strategies introduced in this lesson:
• Prompt table edits
• Effective-dated tables
• FOR
Translate table prompts
Yes/No edits
• Tableset sharing prompts
INTERNAL
See PeopleTools I: Activity Guide, lesson 6, “Validating Data,” Activity 11: Determining
Validation Strategies.
Slide 111 ______________________________________________________________________________________________________
Student Notes USE

ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Review
• Prompt tables are master lists of data that you can use to constrain data that you enter
in a field.
• Effective-dating logic divides data into historical, current, and future data.
• PeopleSoft applications are delivered with multiple types of validation.
•
FOR
Tableset sharing allows you to use business rules to constrain data that a user can
access.
Slide 112 ______________________________________________________________________________________________________

______________________________________________________________________
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 7
Developing Applications by Using

the Eight Steps
Objectives
FOR
• INTERNAL
Describe the PeopleSoft application development process.
Describe the PeopleSoft Application Designer Interface.
• Organize definitions in a project.
USE
Slide 114 ______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Developing Applications by Using the Eight Steps Lesson 7
Describing the PeopleSoft Application Development Process

In PeopleSoft environments, application development requires four phases:
Test Plan
Test Design
Application Application
FOR
Register
INTERNAL
Define
Components Fields
Define
Components Define
Records
USE
User Interface Define
Pages
Build
Tables
Data Design
ONLY!
Application development phases
Slide 115 ______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 7 Developing Applications by Using the Eight Steps
Describing the PeopleSoft Application Development Process (continued)

You divide the four phases into the eight steps of application development.
1. Plan the application. 5. Define pages.
2. Define fields. 6. Define components.
3. Define records. 7. Register components.
4. Build tables. 8. Test the application.
FOR
Slide 116 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Describing the PeopleSoft Application Development Process (continued)

The eight-step process affects every layer of tables.
1. Design the Application
2. Define New Fields

System Catalog
3. Create the Record Definition
PeopleTools
FOR 4. Build the SQL Table
Application Data 5. Create the Page Definition
INTERNAL
Database Server
6. Define the Component
USE 7.
8.
Register Component
Test the Application
ONLY!
Tables affected by each development step
Slide 117 ______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Describing the PeopleSoft Application Designer Interface

The following diagram shows how the PeopleSoft Application Designer enters data into
PeopleTools tables:
Development Database
Workstation
System Catalog
Build
FOR
Definitions
PeopleTools
Application Data
Tables
INTERNAL
PeopleTools tables
Slide 118 ______________________________________________________________________________________________________
Student Notes USE

______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Describing the PeopleSoft Application Designer Interface (continued)

Pages comprise several definition types. Use the PeopleSoft Application Designer to
create and maintain definitions.
Slide 119 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 12: Using the PeopleSoft Application Designer

• Use the browser to examine a page.
• Use the PeopleSoft Application Designer to examine page elements.
See PeopleTools I: Activity Guide, lesson 7, “Developing Applications by Using the

Eight Steps,” Activity 12: Using the PeopleSoft Application Designer.
FOR
Slide 120 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Organizing Definitions in a Project

A project is a container that holds references to many definitions. Use projects to:
• Group definitions into logical areas.
• Coordinate the work of several developers who are working on the same application.
• Better understand the relationships between definitions.
•
FOR
Simplify access to definitions during development.
Organize definitions to promote them from development to production.
Streamline the migration of definitions from one database to another during the
INTERNAL
upgrade process.
Slide 121 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Organizing Definitions in a Project (continued)

You can insert definitions into a project in multiple ways:
• Select Insert, Current Definition into Project if the definition is open and active.
• Select Insert, Definition into Project if the definition is not open.
• Press the F7 key to insert a definition that is open and active.
FOR
Press CTRL+F7 to insert a definition that is not open.
Slide 122 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


You can automatically include definitions that you create or alter in the project that you
have open; you must set a few tools options.
Slide 123 ______________________________________________________________________________________________________
Student Notes
Use the following navigation path in the Application Designer to access this page:
Dialog Box Name

Options
FORNavigation
Tools, Options
Select the Project tab.
Options
INTERNAL Tools, Options
Select the Validate tab.
• USE
Use the Options dialog box to set project preferences:
ONLY!
Options dialog box
• Use the Options dialog box to set project spell checking preferences:

FOR
INTERNAL
USE
Options dialog box
See Also
ONLY!
PeopleTools 8.44 PeopleBook: PeopleSoft Application Designer, “Working with
Projects”
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


You create a project the same way that you create any definition in the Application
Designer:
1. Select File, New.
2. Select Project from the dialog box.
3. Select File, Save As.
FOR
Slide 124 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 13: Organizing Definitions in a Project

• Open an existing project.
• Insert definitions into a project.
• Set project options.
FOR
Create a new project.
See PeopleTools I: Activity Guide, lesson 7 “Developing Applications by Using the Eight
Steps,” Activity 13: to Organizing Definitions into Projects.
INTERNAL
Slide 125 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Review
• To create a PeopleSoft application, use the eight steps of application development.
• The PeopleSoft Application Designer is the primary tool for developing PeopleSoft
applications.
• You organize definitions into projects to assist you when you upgrade the definitions.
FOR
Slide 126 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 8
Designing the Application
Objectives
•
FOR
Plan the application.
• Determine functional specifications.
•
INTERNAL
Determine technical specifications.
Describe the training application.
USE
Slide 128 ______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Designing the Application Lesson 8
Planning the Application

Designing the application or the planning phase, is the first stage of application
development, which this diagram illustrates:
Test Plan
FOR
Test Design
INTERNAL Register
Components
Define
Fields
USE
Define
Components Define
Records
User Interface Define Build Data Design
Pages Tables
ONLY!
The relative importance of the design phase
Slide 129 ______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 8 Designing the Application
Planning the Application (continued)

In designing the application, consider your goals to include:
• Resource allocation.
• Cost constraints.
• Time.
FOR
Contingency planning.
Slide 130 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 14: Choosing Design Participants

In this activity, you will review the activity overview and choose the participants of the
design phase.
See PeopleTools I: Activity Guide, lesson 8, “Designing the Application,” Activity 14:
Choosing Design Participants.
Slide 131 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Determining Functional Specifications

A set of functional specifications is likely your starting point for development. Complete
specifications are:
• Well planned.
• Written by people with a variety of backgrounds.
• Sufficiently detailed with regard to table relationships, functional design, and so on.
FOR
Slide 132 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Determining Functional Specifications (continued)

PSU Training requires a list of its courses. Each course must include:
• Course code.
• Course description.
• Course type (such as PeopleTools or HRMS).
•
Course length.
FOR
Number of training units.
PeopleTools version.
•
INTERNAL
Application version.
Name of the curriculum developer (an instructor).
•
USE
On-site status.
Slide 133 ______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 15: Determining Functional Specifications

In this activity, you will review the activity overview and ask questions about creating
specifications.
See PeopleTools I: Activity Guide, lesson 8, “Designing the Application,” Activity 15:
Creating Functional Specifications.
Slide 134 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Determining Technical Specifications

The technical specifications identify:
• Field definitions.
• Record definitions.
Slide 135 ______________________________________________________________________________________________________
Student Notes
FOR
These specifications identify the field definitions:
Name Type Length Label (Long/Short) Format Translate Exists

T1_COURSE
EFFDT
INTERNAL Char
Date
6
10
Course Code / Course
Effective Date / Eff
Date
Upper
N/A
N
N
N
Y
EFF_STATUS
DESCR
USE Char
Char
1
30
Status as of Effective
Date / Status
Course Title / Title
Upper
Mixed
Y
N
Y
ONLY!
COURSE_TYPE Char 4 Course Type / Type Upper Y Y
T1_LENGTH_DAYS Num 2.1 Length (Days) / N/A N N
Length
T1_UNITS Num 2.1 Training Units / Units N/A N N
T1_ONSITE Char 1 Available at Upper N N
Customer Site / On
Site
INSTRUCTOR Char 4 Curriculum Upper N Y
Developer / CD
T1_APP_REL Char 4 Application Release / Upper Y N
App Release
T1_TOOLS_REL Char 4 PeopleTools Release / Upper Y N
Tools Release
These specifications identify the record definition, T1_COURSE_TBL:
Name Key Srch List Req Edit Prompt Table Default

T1_COURSE Key Y Y Y N/A N/A N/A
EFFDT Key N N Y N/A N/A %Date
EFF_STATUS N N N N XLAT N/A A
DESCR Alt N Y Y N/A N/A N/A
COURSE_TYPE N N N Y XLAT N/A V

T1_LENGTH_DAYS N N N N N/A N/A N/A

T1_UNITS N N N N N/A N/A N/A
T1_ONSITE N N N Y Y/N N/A Y
INSTRUCTOR N N N N Prompt PSU_INSTR_TBL N/A
T1_APP_REL N N N Y XLAT N/A 8.80
T1_TOOLS_REL N N N Y XLAT N/A 8.40
These specifications identify a page definition, T1_COURSE:
FOR
INTERNAL
USE
ONLY!
Course Details page
These specifications identify a component definition, T1_COURSE:
Element Value
Pages T1_COURSE
Item labels Course Details
Search record T1_COURSE_TBL
Actions Add
Update/Display
Update/Display All (Include History)
Correction (Correct History)
Default search mode Advanced
Default search action Update/Display
Toolbar buttons Save
Return to List
Next in List
Previous in List
Add
Update/Display

Update/Display All (Include History)

Correction (Correct History)
FOR
INTERNAL
USE
ONLY!

Determining Technical Specifications (continued)

As part of the technical specifications you must determine:
• Who can access the pages in the component.
• How the component appears in navigation.
Slide 136 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Describing the Training Application

This application is partially complete. You have been looking at lists of students and
instructors that are a part of it. You will continue development and add more components.
This section discusses:
• The production schedule for this class.
• The application data model.
FOR
Slide 137 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Describing the Training Application (continued)

To maintain your production schedule, you have to add four application elements:
• Course and Course Materials.
• Course Session and Course Enrollment.
• Course Databases.
• Course Evaluation.
FOR
Slide 138 ______________________________________________________________________________________________________
Student Notes
INTERNAL
This table provides a project plan for the remainder of the course:
Application Description Due Date
USE
Course and Course Materials Allows entry of all PSU courses
and links them to the materials
that are required to conduct them.
Two components.
Day 3
Enrollment
ONLY!
Course Sessions and Course Allows courses to be scheduled
into sessions on various dates and
at various facilities, and allows
students to be enrolled in these
Day 4
sessions. Two components.

Course Databases Links a table of master databases Day 4
used on student workstations to
the courses with which they are
used. Two components.
Course Evaluation Allows students to enter Day 5
evaluation information for each
course session. One component.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Review
• Planning an application is the most important phase of development.
• Creating the functional specifications begins the process of defining the capability of
the application.
• You use the functional specifications to create technical specifications.
•
FOR
The training application that you build will allow you to track students and the
courses they take.
Slide 139 ______________________________________________________________________________________________________

______________________________________________________________________
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 9
Defining Fields
Objectives
•
FOR
Discuss fields in PeopleSoft applications.
• Identify field definition types and properties.
•
INTERNAL
Create field definitions.
Assign translate values.
USE
Slide 141 ______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Defining Fields Lesson 9
Discussing Fields in PeopleSoft Applications

After you design an application, you can start building it. In PeopleSoft applications, this
means creating definitions. Field definitions are the foundation for all other definitions.
This diagram illustrates the define fields design phase:
Test Plan
FORTest
Application
Design
Application
INTERNAL Register
Components Define
Fields
USE
User Interface
Define
Components
Define Build
Define
Records
Data Design
Pages Tables
ONLY!
Define field step of application development
Slide 142 ______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 9 Defining Fields
Discussing Fields in PeopleSoft Applications (continued)

In this example, the entries CONS, LSL, and XYZ are data in the CUSTOMER_ID
columns:

LSL Lone Star Longhorn Cattle Company Lone Star
XYZ XYZ Corporation XYZ Corp
Customer data
FOR
Slide 143 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Discussing Fields in PeopleSoft Applications (continued)

This diagram illustrates that field definitions can be used in many different record
definitions:
CUSTOMER_ID
Field Definition
FOR
LSL LoneStar Longhorn Cattle Co. LoneStar
XYZ XYZ Corporation XYZ
INTERNALSTUDENT_ID
2001
2003
STUDENT_NAME
Larsen,Mark D
Bechingham,Carol
CUSTOMER_ID
XYZ
CONS
EMPHASIS
F
T
USE 2020 Carson,Kitty
The CUSTOMER_ID field definitions used in different tables

LSL T
Slide 144 ______________________________________________________________________________________________________
Student Notes ONLY!

______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Identifying Field Definition Types and Properties

The PeopleSoft environment supports these field types:
• Char (character).
• Long (long character).
• Nbr (number).
• Dt (date). FOR
Sign (signed number).
Slide 145 ______________________________________________________________________________________________________

See PeopleTools 8.44 PeopleBook: PeopleSoft Application Designer, “Creating Field
Definitions”
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Identifying Field Definition Types and Properties (continued)

The PeopleSoft environment also supports these field types:
• Tm (time).
• DtTm (datetime).
• Img (image).
• Att (attachment). FOR

Iref (image reference).
Slide 146 ______________________________________________________________________________________________________

______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Field properties include:
• Name.
• Type.
• Length.
•
Label options.
Translate values. FOR

Slide 147 ______________________________________________________________________________________________________

______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


As with all PeopleSoft definitions, field definitions are stored in PeopleTools tables. You
create and configure fields with the PeopleSoft Application Designer.
Slide 148 ______________________________________________________________________________________________________
Student Notes
In the PeopleSoft Application Designer, use the following navigation paths to access
these definitions:
Definition Name
FOR
INSTRUCTOR (character field)
Navigation
File, Open
INTERNAL
COMMENTS (long character field)
Select Field from the Definition drop-down list box
File, Open
USE
ADD_DT (date field)
ACTIONS (number field)

File, Open
File, Open
ONLY!
An example of a character field type is the INSTRUCTOR field:

FOR
INTERNAL
A character field type USE
ONLY!
An example of a long character field type is the COMMENTS field:
A long character field type
An example of a date field type is the ADD_DT field:

FOR
INTERNAL
A date field type USE
ONLY!
An example of a number field type is the ACTIONS field:
A number field definition


Many field definitions come delivered by PeopleSoft. Examples include:
• EFFDT
• EFF_STATUS
• DESCR
• DATE
FOR
Slide 149 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 16: Examining Field Definitions

In this activity, you will read the activity overview and examine PeopleSoft field
definitions.
See PeopleTools I: Activity Guide, lesson 9, “Defining Fields,” Activity 16: Examining
Field Definitions.
Slide 150 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Creating Field Definitions

This section discusses the basics of creating fields in the Course application:
• A review of the PSU_COURSE technical specifications.
• Steps to creating field definitions.
Slide 151 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Creating Field Definitions (continued)

To create field definitions, perform these steps in the PeopleSoft Application Designer:
2. Select Field from the list in the New Definition dialog box, and click the OK button.
3. Select the field type.
4. Configure the properties that are appropriate for the field type.
FOR
5. Enter a label ID, a long name, and a short name.
6. Select File, Save.
INTERNAL
7. Enter a unique name.
8. Click the OK button.
USE
Slide 152 ______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 17: Creating Field Definitions for the Course Application

In this activity, you will read the activity overview and
1. Enter new field labels.
2. Create new field definitions.
See PeopleTools I: Activity Guide, lesson 9, “Defining Fields,” Activity 17: Creating
Field Definitions for the Course Application.
FOR
Slide 153 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Assigning Translate Values

Values stored in the translate table are tied to specific field definitions. In this section you
will review the translate table and discuss:
• Expanding the technical specifications to include translate values.
• Entering translate values into appropriate fields.
Slide 154 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Assigning Translate Values (continued)

Translate values are assigned directly to field definitions and stored in the table
PSXLATITEM. It is best to use translate values when:
• The values are specific to one field and are not to be shared by any other fields.
• The only values that you require are labels that identify the content.
• The values do not change often.
FOR
Slide 155 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


The four fields identified to have translate values in the technical specifications are:
• EFF_STATUS
• COURSE_TYPE
• T1_APP_REL
• T1_TOOLS_REL
FOR
Slide 156 ______________________________________________________________________________________________________
Student Notes
INTERNAL
This table extends your technical specification, including the translate values that must be
in place for each field definition that uses them. These rows show existing definitions:
Field Name
EFF_STATUS
USE Values
A
I
Long Name
Active
Inactive
Short Name
Active
Inactive
COURSE_TYPE D Distribution Distrib
ONLY! E
F
H
Enterprise Performance Mgmt
Financials
Human Resources
EPM
Financials
HRMS
M Manufacturing Manuf
S Student Administration Stud Admin
T Technical Tech
V Customer Relationship Mgmt CRM
X Multiple Multi
These two rows show new definitions.
Field Name Values Long Name Short Name

T1_APP_REL 800 8.00 8.00
830 8.30 8.30
840 8.40 8.40
NA Not Applicable N/A
T1_TOOLS_REL 800 8.00 8.00
818 8.18 8.18
840 8.40 8.40
844 8.44 8.44


To enter translate values for a field, perform these steps:
1. Open the appropriate field.
2. Select File, Definition Properties.
3. Select the Translate Values tab.
4. Click the Add button.
FOR
5. Enter the name, effective date, long name, and short name.
INTERNAL
7. Save the field.
Slide 157 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 18: Creating Translate Values

• Add translate values to the application release field.
• Add translate values to the tools release field.
Translate Values.
FOR
Slide 158 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 19: Creating Field Definitions

In this activity, you will read the activity overview and create field definitions for the
T1_COURSE_MATL table.
Field Definitions.
Slide 159 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Review
• Fields are stand-alone, reusable definitions.
• You can create a variety of field types such as character, number, time, date, and long
character fields.
• To create field definitions you must choose a data type, enter values for labels, and
• FOR
provide a unique name.
Translate values are associated with specific fields.
Slide 160 ______________________________________________________________________________________________________

______________________________________________________________________
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 10
Creating Record Definitions
Objectives
•
FOR
Explain record definitions.
• Access record definition displays.
•
INTERNAL
Configure record definition properties.
Configure record field use properties.
•
USE
Configure record field edits properties.
Create a record definition.
ONLY!
Slide 162 ______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Creating Record Definitions Lesson 10
Explaining Record Definitions

Once the field definitions are in place, you organize them into record definitions, as this
chart shows:
Test Plan
Test Design
FOR
INTERNAL Register
Components
Define
Define
Fields
Define
USE
Components
Records
Pages Tables
ONLY!
Defining records in the data design phase of application development
Slide 163 ______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 10 Creating Record Definitions
Explaining Record Definitions (continued)

The data design phase consists of steps 2 through 4 of the application design process.
Creating record definitions is step 3. This diagram shows the relationship between the
definitions:
FOR
INTERNAL
USE
Data design phase of application development
Slide 164 ______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Accessing Record Definition Displays

Record definitions include properties for:
• Individual field definitions
• Each field in the record definition
• PeopleCode assigned to events with specific fields
FOR
The record definition as a whole
Slide 165 ______________________________________________________________________________________________________
Student Notes
INTERNAL
Use the following navigation path to access this definition in the PeopleSoft Application
Designer:
USE
Definition Name Navigation
PSU_STUDENT_TBL File, Open
Select Record from the Definition drop-down list box.
ONLY!
PSU_STUDENT_TBL record definition
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Accessing Record Definition Displays (continued)

When you open a record definition, you see the Field Display view:
• The display buttons on the toolbar allow access to different views.
• You can also use the View menu to see different record displays.
Slide 166 ______________________________________________________________________________________________________
Student Notes
FOR
You can use the display buttons to access a summary of record field properties:
INTERNAL
Display buttons for a record definition
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Accessing Record Definitions Displays (continued)

There are four views:
• The Fields Display view shows field properties of the record definition.
• The Use Display view shows record field properties that pertain to key structure and
default values.
• The Edits Display view shows how fields in the record definition prompt for data
•
validation.
FOR
The PeopleCode Display view shows which fields in the record definition have
PeopleCode associated with them.
INTERNAL
Slide 167 ______________________________________________________________________________________________________
Student Notes
definition.
USE
Field display values are global attributes. Other display properties are local to the record
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 20: Accessing Record Definitions Displays

In this activity, you will read the activity overview and access PeopleSoft field
definitions.
See PeopleTools I: Activity Guide, lesson 10, “Creating Record Definitions,” Activity 20:
Accessing Record Definitions Displays.
Slide 168 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Configuring Record Definition Properties

The Fields Display view shows a summary of field definition properties. You cannot
change these properties in the record definition. You access these properties through the
record definition by right-clicking the field.
Slide 169 ______________________________________________________________________________________________________
Student Notes
FOR
You can view field definition properties by right-clicking the record field and then
selecting View Definition from the pop-up menu:
INTERNAL
USE
ONLY!
Pop-up menu showing View Field Properties menu item
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Configuring Record Definition Properties (continued)

Record properties apply to the record as an entity. Record properties include:
• Documentation
• Record relationships
• Audit information
FOR
Auto update information
Slide 170 ______________________________________________________________________________________________________
Student Notes
INTERNAL
Dialog Box Name Navigation
USE
Record Properties File, Open
Select Record from the drop-down list box.
•
ONLY!
Select the General tab in the Record Properties dialog box to view general record
properties:

FOR
INTERNAL
USE
ONLY!
General tab in the Record Properties dialog box
• Select the Use tab in the Record Properties dialog box to view information about
record relationships and audits:

FOR
INTERNAL
USE
ONLY!
Use tab in the Record Properties dialog box
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 21: Examining Record Definition Properties

• Examine field definition properties.
• Examine record properties.
Examining Record Definition Properties.
FOR
Slide 171 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Configuring Record Field Use Properties

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 like a child, it must include the same key values as its
parent, in the same order, and at least one more key.
• If a record definition uses effective dating, the EFFDT field must be a key field in
•
descending order.
FOR
Key fields are followed by duplicate order keys, in order of importance, then by
fields that are not keys.
•
INTERNAL
Alternate search key fields can appear anywhere among regular fields, in any order.
They do not need to be grouped.
Key, duplicate order key, and alternate search key fields are mutually exclusive.
USE
Slide 172 ______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Configuring Record Field Use Properties (continued)

The Use Display view shows that the PSU_STUDENT_TBL record definition has a
simple key structure, with a single key field: STUDENT_ID.
Slide 173 ______________________________________________________________________________________________________
Student Notes
Key fields precede non-key fields in a record definition.
Definition Name
PSU_STUDENT_TBL
FORNavigation
File, Open,
Select Record from the Definition drop down list box.
INTERNAL
USE
ONLY!
The key structure of the PSU_STUDENT_TBL record definition
Note. You should place all long character fields and image fields as the last field in the
record definition.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


If you double-click the STUDENT_ID field, the Record Field Properties dialog box
appears. The first configuration option on the Use tab is Keys. Fields can be one of three
types of key field options:
• Key.
• Search key.
•
FOR
Alternate search key.
Slide 174 ______________________________________________________________________________________________________
Student Notes
INTERNAL
You have many options to choose for key structure:
USE
ONLY!
Key options in the Record Field Properties dialog box
A Field can be designated a key, duplicate order key or alternate search key. These are
mutually exclusive properties. A key may be designated a search key. A duplicate order
key generates a search index but allows duplicate values. An alternate search key is
available on the search page for the component, but not as a key in the table structure. An
index is generated for alternate search keys.
See Also
Definitions”


You build the search page by using the search key options. A field is available as a search
option when:
• A field is a key and a search key.
• A field is an alternate search key.
Slide 175 ______________________________________________________________________________________________________
Student Notes
FOR
Notice the search properties of the PSU_STUDENT_TBL record definition:
INTERNAL
USE
ONLY!
The Use view showing search options
In this example, the PSU_STUDENT_TBL record definition builds the Personal

Information search page:

FOR
INTERNAL
USE
ONLY!
Personal Information search page
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


When you create field definitions, you enter the label ID. Keep these points about label
IDs in mind:
• Every label ID has a long name and a short name associated with it.
• Every field definition must have at least one label ID; many field definitions have
multiple label IDs.
• FOR
Configure each record field with the appropriate label ID.
The default setting is ***Use Default Label***.
Slide 176 ______________________________________________________________________________________________________

Use the Record Field label ID to select a specific label from all of the labels associated
with the field:
USE
ONLY!
Record Field label ID drop-down list box
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


If you want new data rows to include default values for some fields, enter the value in the
record field properties. Enter values for:
• Fields that use a check box (normally Y/N edits).
• Any fields that appear as radio buttons (normally translate edit fields).
• Effective date fields, usually with the system variable %date.
•
FOR
Effective status fields, normally as active (A).
Fields that validate against the translate table.
INTERNAL
Slide 177 ______________________________________________________________________________________________________
Student Notes
USE
Use the Default Value dialog box to enter a default associated with the field:
ONLY!
Default Value dialog box
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


The page control that you assigned in the Record Field Properties dialog box determines
how the field appears when you develop the page definition.
Slide 178 ______________________________________________________________________________________________________
Student Notes
Use the Default Page Control drop-down list box to select a page control to be displayed
FOR
when this field is placed on a page definition:
INTERNAL
USE
Default Page Control drop-down list box
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


You can select any page control from the Default Page Control list box; however, many
controls might not be appropriate. This table shows examples of optional page controls:
Characteristic System Default Optional Page Controls

Translate table edit Drop-down list box Radio buttons
Edit box (with prompt button)
Check box (if only two values)
Prompt table edit
Yes/No edit
FOR Edit box (with prompt button)
Check box
Drop-down list box
Drop-down list box
Slide 179 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 22 Configuring Record Field Use Properties

1. Examine combinations of key values.
2. Examine search options.
3. Examine label ID settings.
4. Examine default values.
FOR
Configuring Record Field Use Properties.
INTERNAL
Slide 180 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Configuring Record Field Edits Properties

You configure data validation on the Edits tab of the Record Field Properties dialog box.
You can validate a record field by:
• Selecting the Required check box.
• Selecting a Translate table edit.
• Selecting a Yes/No table edit.
•
FOR
Selecting a Prompt table edit.
Selecting a Prompt table with no edit.
INTERNAL
Slide 181 ______________________________________________________________________________________________________
Student Notes
USE
The Edits view shows an overview of the record field edits properties for fields in the
record definition:
ONLY!
Edits view of the PSU_STUDENT_TBL record definition
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Configuring Record Field Edits Properties (continued)

The Required record field property on the Edits tab determines whether a field must
include data to save a row. At a minimum, mark the following as required:
• Key fields.
• Alternate search key fields.
• Radio buttons.
• Check boxes.
FOR
Slide 182 ______________________________________________________________________________________________________
Student Notes
INTERNAL
Use the Edits tab to determine various types of validation:
USE
CURR_DEV_FLAG File, Open
Select Record from the Definition field.
Double click the field.
ONLY! Select the Edits tab.
Edits properties
Marking a field as required displays an asterisk on the page in the browser.


To validate field values against a table:
1. Select Table Edit in the Record Field Properties dialog box.
2. Select the type of table validation values.
Slide 183 ______________________________________________________________________________________________________
Student Notes
FOR
Use the Edit Type drop-down list box to select a table validation:
INTERNAL
USE
ONLY!
Edit Type drop-down list box
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


There are four table edit types:
• Prompt table edit.
• Prompt table no edit.
• Yes/No table edit.
• Translate table edit.
FOR
Slide 184 ______________________________________________________________________________________________________
Student Notes
INTERNAL
The PSU_STUDENT_TBL record definition shows three of the four edit types:
USE
ONLY!
PSU_STUDENT_TBL record definition
The CUSTOMER_ID field shows a prompt table edit. The EMPHASIS field shows a
translate table edit, and the SAME_ADDR_CUSTOMER field shows a Yes/No table
edit.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


When validating against a prompt table:
1. Specify the table edit type.
2. Specify the table where you find the valid values.
Slide 185 ______________________________________________________________________________________________________
Student Notes
FOR
Use the Prompt Table drop-down list box to select a table validation:
INTERNAL
USE
ONLY!
Prompt table edit retrieving values from the PSU_TRNLOC_TBL table
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 23: Examining Record Field Edits Properties

1. Examine the Edits display view.
2. Examine the Required check box.
3. Examine translate table edits.
4. Examine Yes/No table edits.
FOR
5. Examine Prompt table edits.
INTERNAL
Examining Record Field Edits Properties.
Slide 186 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Creating a Record Definition

Before creating a record definition, revisit the technical specifications.
Slide 187 ______________________________________________________________________________________________________
Student Notes
This table shows the specifications for the T1_COURSE_TBL record definition:
Name
T1_COURSE
EFFDT
FOR
Key
Key
Key
Srch
Y
-
List
Y
-
Req
Y
Y
Edit
-
-
Prompt Table
-
-
Default
-
%Date
EFF_STATUS
DESCR INTERNAL
COURSE_TYPE
-
Alt
-
-
-
-
-
Y
-
-
Y
Y
XLAT
-
XLAT
-
-
-
A
-
V
T1_UNITS
T1_ONSITE
USE
T1_LENGTH_DAYS
-
-
-
-
-
-
-
-
-
-
-
Y
-
-
Y/N
-
-
-
-
-
Y
ONLY!
INSTRUCTOR - - - - Prompt PSU_INSTR_TBL -
T1_APP_REL - - - Y XLAT - 8.80
T1_TOOLS_REL - - - Y XLAT - 8.40
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Creating a Record Definition (continued)

To create a record definition:
1. Open a new record definition.
2. Insert the necessary fields.
3. Set the record field properties.
4. Save the record definition.
FOR
Slide 188 ______________________________________________________________________________________________________
Student Notes
INTERNAL
See PeopleTools 8.44 PeopleBook: PeopleSoft Application Designer, “Creating Record
Definitions,” Naming Record Definitions
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Creating a Record Definition (continued)

When you have inserted all of the fields that the specifications indicate, save the record
definition. Depending on the settings, you may have to:
1. Document the record definition.
2. Select the tablespace name.
Slide 189 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 24: Creating a Record Definition

1. Create a record definition.
2. Insert field definitions.
3. Configure record field properties.
FOR
Creating a Record Definition.
Slide 190 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 25: Creating the T1_COURSE_MATL Record Definition

1. Create a record definition.
2. Insert field definitions.
3. Configure record field properties.
4. Complete the record definition.
FOR
See PeopleTools I: Activity Guide, lesson 10, "Creating Record Definitions," Activity 25:
Creating the T1_COURSE_MATRL Record Definition.
INTERNAL
Slide 191 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Review
• Record definitions are collections of field definitions that serve as templates for the
SQL table.
• There are four record definition displays.
• Record properties include record relationships, audits, and set control properties.
•
FOR
Record field use properties include key structure, default values, and search
properties.
• Record field edits properties include require fields and table edits.
•
INTERNAL
Creating new record definitions requires you to set record, record field use, and
record field edits properties.
Slide 192 ______________________________________________________________________________________________________
Student Notes USE

ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 11
Building SQL Tables
Objectives
•
FOR
Describe the relationship between record definitions and application data tables.
• Build SQL tables.
• INTERNAL
View table indexes.
Slide 194 ______________________________________________________________________________________________________
Student Notes USE

______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Building SQL Tables Lesson 11
Describing the Relationship Between Record Definitions and Application

Data Tables
Once you create the record definitions, you build the database tables, as this diagram
shows:
Test Plan
FOR Test
Application
Design
Application
INTERNAL Register
Components
Define
Fields
USE
User Interface
Define
Components
Define
Build
Define
Records
Data Design
Pages
ONLY! Tables
Building tables in the data design phase of application development process
Slide 195 ______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 11 Building SQL Tables

Data Tables (continued)
This illustration shows the three types of tables in a PeopleSoft database:
FOR
INTERNAL
USE
The three types of tables in a PeopleSoft database
Slide 196 ______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Data Tables (continued)
Record definitions are a blueprint for generating the SQL to build the application data
tables, as this diagram illustrates:
Update System
Catalog
with New
System Table
Catalog
People
Tools
FOR
Information
Record
Definition
Specifications
Build
Process
Data
INTERNAL
Application
PS_<RecDefnName>
Table
USE
The build process in relationship to the three types of tables in a PeopleSoft database
Slide 197 ______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 26: Analyzing PeopleSoft Tables

1. Connect to the database.
2. Query PeopleTools tables.
3. Query application data tables.
4. Query system catalog tables.
FOR
See PeopleTools I: Activity Guide, lesson 11, "Building SQL Tables,” Activity 26:
Analyzing PeopleSoft Tables.
INTERNAL
Slide 198 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Building Application Data Tables

The create table process generates an SQL script that uses information from the record
definition to create the database table. This table explains the way that the build process
uses the record definition to create the table:
SQL Script Record Definition Property Application Data Table Property

Drop the table NA NA
if it already
exists.
Create the
application data
table.
FOR
Record definition name
Field names
Field type
Table name (add PS_ prefix)
Column names
Column type
INTERNAL
Designates
fields as NOT
NULL.
Field length
Numeric fields
Character fields
Column length
Value = 0 or default from record definition
Value = blank space or default from record
Required fields regardless of data definition
USE
Create indexes
type
Key fields
Alternate search key fields
1 per table
1 per alternate search key field
ONLY! Fields specified in a custom index

definition
1 per custom index definition
Slide 199 ______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Building Application Data Tables (continued)

This illustration shows the SQL create table process:
SQL Create Table Process
Drop Table if exists
System Catalog Tables

Create Application Data Table y SYSOBJECTS
PS_VEHICLE_TBL
FOR
y SYSCOLUMNS
Mark Fileds Not Null
Numerics - 0
People Tools Tables
Character Fields - blank
y PSRECDEFN
Reg'd fields - default value from rec defn
INTERNAL
y PSPNLDEFN
Create Indexes
Key(s)
Application Data Tables
Alternate Search Key(s)
y PS_STUDENT_DATA
Custom Index(es)
y PS_CUSTOMER_TBL
USE
ONLY!
The SQL create table process
Slide 200 ______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


To build the table::
1. Open the record that you want to build.
2. Select Build, Current Definition.
3. Set build settings, if necessary.
4. Select build options.
FOR
5. Click the Build button.
6. Execute the SQL script, if required.
INTERNAL
Slide 201 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Use the Build dialog box to set:
• Build options
• Build execute options
• Build settings
FOR
Slide 202 ______________________________________________________________________________________________________
Student Notes
Use the Build dialog box to create the SQL table from the record definition:
Build
INTERNAL
Build, Current Definition
USE
ONLY!
Build dialog box
See Also
PeopleTools 8.44 PeopleBook: PeopleSoft Application Designer, “Building SQL Tables
and Views”


Once you have selected a build option, you select build settings. There are three tabs that
you configure when building tables:
• Create
• Logging
• Scripts
FOR
Slide 203 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Select the Build option in the Build dialog boxto:
• Generate the SQL that builds the table.
• Generate a log file.
Slide 204 ______________________________________________________________________________________________________
Student Notes
FOR
The log file displays in the output window:
INTERNAL
Log file USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


To verify results, query the database with the SQL query tool.
Slide 205 ______________________________________________________________________________________________________
Student Notes
To verify the table, execute the following queries:
FOR
SELECT * FROM PS_T1_COURSE_TBL
sp_help PS_T1_COURSE_TBL
INTERNAL
SELECT * FROM sysobjects WHERE name like ‘PS_T1%;’
Note. The sp_help command is a stored procedure that is specific to Microsoft SQL
Server. Consult your DBA or platform documentation for commands appropriate to your
database.
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 27: Building Application Data Tables

1. Start the build process.
2. Change build options.
3. Set build parameters.
4. Generate SQL scripts.
FOR
5. Verify the presence of a table.
See PeopleTools I: Activity Guide, lesson 11, “Building SQL Tables,” Activity 27:
INTERNAL
Building Application Data Tables.
Slide 206 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Viewing Table Indexes

You generate most indexes when you build the table. However, you must design custom
indexes separately from the record definition. This table explains the indexes that key
fields build:
Record Definition Field Index Name Indexes Created

Key or Duplicate Order Key PS_Recname One per table
Alternate Search Key PSnRecname One per alternate search key
index definition
FOR
Any field specified in a custom
n is a number 0 to 9
PSxRecname
x is a letter A to M
One per custom index definition
INTERNAL
Slide 207 ______________________________________________________________________________________________________
Student Notes
Note these examples of indexes:
•
USE
PS_T1_COURSE_TBL is a key index.
PS0COURSE_TBL is a search key index.
•
ONLY!
The table that you created has no custom indexes.
Note. You generate the first two indexes listed in the table when you initially build an
application data table. Developers create custom indexes as necessary.
Table indexes may change over the life of an application data table. You can change the
indexes associated with a table without losing existing rows of data, because indexes are
references to data.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Viewing Table Indexes (continued)

By querying the database, you display the indexes.
Slide 208 ______________________________________________________________________________________________________
Student Notes
To view an index, execute the following query:
FOR
sp_helpindex PS_T1_COURSE_TBL
Note. The sp_helpindex command is a stored procedure that is specific to Microsoft SQL
Server. Consult your DBA or platform documentation for commands appropriate to your
database.
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 28: Viewing Indexes in a Table

In this activity, you will read the activity overview and examine the indexes for the
PS_T1_COURSE_TBL table.
See PeopleTools I: Activity Guide, lesson 11, “Building SQL Tables,” Activity 28:
Viewing Indexes in a Table.
Slide 209 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 29: Building the PS_T1_COURSE_MATRL Table

1. Build the PS_T1_COURSE_MATL table.
2. Verify the existence of the table in the database.
See PeopleTools I: Activity Guide, lesson 11, "Building SQL Tables,” Activity 29:
Building the PS_T1_COURSE_MATRL Table.
FOR
Slide 210 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Review
• Record definitions are the templates from which the SQL that builds the application
data tables is generated.
• To build an SQL table you must configure the settings such as build and scripting
options.
•
FOR
You build table indexes automatically when you build the table.
Slide 211 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 12
Creating Page Definitions
Objectives
•
FOR
Identify page design principles.
• Identify page and page control properties.
•
INTERNAL
Add page controls to a page.
Create page definitions.
•
USE
Implement scroll areas and grids.
Finalize page design and layout.
ONLY!
Slide 213 ______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Creating Page Definitions Lesson 12
Identifying Page Design Principles

Defining pages is the first step in the user interface phase of development. As this
diagram illustrates, the data design phase is complete and you are ready to connect the
data to the user:
Test Plan
FOR Test
Application
Design
Application
INTERNAL Register
Components
Define
Fields
USE
User Interface
Define
Components
Define Build
Tables
Define
Records
Data Design
Pages
ONLY!
Page definition as part of the user interface phase of application development
Slide 214 ______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 12 Creating Page Definitions
Identifying Page Design Principles (continued)

You design page definitions that are divided into levels:
• You can build pages with a maximum of four levels, all related in a one-to-many
relationship.
• The levels are numbered from 0 to 3.
Slide 215 ______________________________________________________________________________________________________
Student Notes
FOR
This diagram shows a page with three levels:
INTERNAL
Label: NNNNNNNNNNNNNNNNNNNNNNNN 0
USE
Label: NNNNNNNNNNNNNNNNNNNNNNNN
ONLY!
Label: NNNNNNNNNNNNNNNNNNNNNNNN
3
Label: Label:
Label:
Illustration of a PeopleSoft page showing multiple levels
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


You can create a page with only level 0. This type of page represents a single table in the
database.
Slide 216 ______________________________________________________________________________________________________
Student Notes
The PeopleSoft Products page shows level 0 only.
FOR
INTERNAL
USE
Page with a level 0 only
See Also
ONLY!
PeopleTools 8.44 PeopleBook: PeopleSoft Application Designer, “Creating Page
Definitions”
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


You can create a page with two levels, 0 and 1. This can represent data from:
• One table, if that table contains the EFFDT field.
• Two tables.
Slide 217 ______________________________________________________________________________________________________
Student Notes
FOR
The Products Transportation page contains a level 0 and a level 1 where both levels are
associated with the same table:
INTERNAL
USE
ONLY!
Page with a level 0 and a level 1 that write to the same table
In this example, both levels write to the same table because that table contains the
EFFDT field.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


The key is selected from the PSU_TRANSPT_TBL table. The data is also written to the
PSU_TRANSPT_TBL table, as shown in this diagram:
PSU_TRNSPT_TBL
Read key from
Write data to
FOR Level 0
INTERNAL Level 1
Process flow when accessing transportation data
USE
Slide 218 ______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Usually, level 0 represents the key shared by a parent and child table. Level 1 contains
other key fields and associated data of the child table.
Slide 219 ______________________________________________________________________________________________________
Student Notes
The Products by Customer page contains a level 0 and a level 1. Each level is associated
with a different table:
FOR
INTERNAL
USE
ONLY!
Page with a level 0 and a level 1 that write to different tables
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


As the search record, the parent table builds the search page and populates level 0. Any
data that you enter writes to the child table, as illustrated in this diagram:
T1_CUST_TBL Read key from
Search Record
FOR Level 0 Write data to
INTERNAL Level 1
T1_CUST_PROD
USE Primary Record
Process flow when accessing customer product data
ONLY!
Slide 220 ______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Sometimes additional information is necessary on the page, although it may not be in the
base table. You display this information in a related field.
Slide 221 ______________________________________________________________________________________________________
Student Notes
Page Name
Products by Customer
FORNavigation
Customers, Product Information
•
INTERNAL
Notice the product code.
USE
PeopleSoft Product field without related field
• Notice the description beside the product code.
ONLY!
PeopleSoft Product field with related field
See Also
Definitions”
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Identifying Page and Page Control Properties

You view page definition properties in the same manner as any other definition’s
properties: Select File, Definition Properties.
Slide 222 ______________________________________________________________________________________________________
Student Notes
Use the Page Properties dialog box to set the page type and size:
Dialog Box Name

Page Properties
FOR Navigation
File, Definition Properties
INTERNAL
USE
ONLY!
Page Properties dialog box

Identifying Page and Page Control Properties (continued)

On a page definition, much of your effort focuses on page control properties. There are
four areas of page control properties:
• Use the Record tab to associate a page control to a field on a record definition.
• Use the Label tab to select a label and its appearance for the field.
• Use the Use tab to define how to use the control on the page.
•
FOR
Use the General tab to specify a name for the page that can be referenced by
PeopleCode.
Slide 223 ______________________________________________________________________________________________________

______________________________________________________________________
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Use the Record tab properties to determine:
• The table and field to which this page control writes.
• The size of the page control.
• Alignment of the page control.
FOR
Other display options.
Slide 224 ______________________________________________________________________________________________________
Student Notes
INTERNAL
Use the Edit Box Properties dialog box to set a variety of configuration options:
USE
Edit Box Properties Edit, Page Field Properties
Click the Record tab.
ONLY!

FOR
INTERNAL
USE
ONLY!
Edit Box Properties dialog box
See Also
Definitions”
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Use the Label tab properties to determine:
• Label type.
• Label text.
• Label alignment.
•
Label position.
FOR
Other display options.
Slide 225 ______________________________________________________________________________________________________

Dialog Box Name

USE
Edit Box Properties
Navigation
Edit, Page Field Properties
Click the Label tab
ONLY!

FOR
INTERNAL
USE
ONLY!
See Also
Definitions”
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Use the Use tab properties to:
• Make the field a display control field.
• Make the field a related field.
• Make the field display only.
• FOR
Set the display only appearance.
Set the processing mode of the field.
Slide 226 ______________________________________________________________________________________________________

Dialog Box Name

USE
Edit Box Properties
Navigation
Click the Use tab.
ONLY!

FOR
INTERNAL
USE
ONLY!
See Also
Definitions”
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Use the General tab properties to:
• Give the page control a name so that you can access it through PeopleCode.
• Make the page control an anchor for a page link.
Slide 227 ______________________________________________________________________________________________________
Student Notes
FOR
INTERNAL
Edit Box Properties Edit, Page Field Properties
Click the General tab.
USE
ONLY!

See Also
Definitions”
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Drop-down list box properties are slightly different than edit box properties.
Slide 228 ______________________________________________________________________________________________________
Student Notes
Use the Drop-Down List Box Properties dialog box to set a variety of configuration
options:
Dialog Box Name

Drop-Down List Box
Properties
FORNavigation
INTERNAL
USE
ONLY!
Drop-Down List Box Properties dialog box
See Also
Definitions”


Radio buttons have slightly different properties than edit boxes. Radio button properties
include a value from the translate table. Assign a value to:
• Choose a value to write to the database.
• Choose a label.
Slide 229 ______________________________________________________________________________________________________
Student Notes
FOR
Use the Radio Button Properties dialog box to set a variety of configuration options:
INTERNAL
Dialog Box Name
Radio Button Properties
Navigation
USE
ONLY!
Radio Button Properties dialog box

See Also
Definitions”
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Check boxes also have slightly different properties than edit boxes. Check box properties
determine the meaning of the check mark.
Slide 230 ______________________________________________________________________________________________________
Student Notes
Use the Check Box Properties dialog box to set a variety of configuration options:
Dialog Box Name

Check Box Properties
FORNavigation
INTERNAL
USE
ONLY!
Check Box Properties dialog box
Note. You have one decision to make on this field type—do you want the selected check
box to represent a Yes or a No value? On this field, when the on value is selected the
value written to the database is Y (for Yes).

See Also
Definitions”
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 30: Identifying Page and Page Control Properties

• Observe page properties.
• Observe the page field properties of edit boxes.
• Observe the page field properties of drop-down list boxes.
• FOR
Observe the page field properties of radio buttons.
Observe the page field properties of check boxes.
See PeopleTools I: Activity Guide, lesson 12, “Creating Page Definitions,” Activity 30:
INTERNAL
Identifying Page and Page Control Properties.
Slide 231 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Adding Page Controls to a Page

You place page controls on a page. This approximates what users see in a browser. There
are three options for adding page controls to a page definition. You can use:
• A toolbar button.
• A menu command.
• A hot key.
FOR
Slide 232 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Adding Page Controls to a Page (continued)

Adding page controls to a blank definition begins the page creation process. To add an
edit box page control:
1. Select Insert, Edit Box.
2. Move the cursor to the desired location inside the blank page.
3. Click on the desired location.
FOR
Slide 233 ______________________________________________________________________________________________________
Student Notes
• INTERNAL
The three types of controls are:
Aesthetic controls.
• Data entry controls.
• USE
Data processing controls.
Note. To add other page controls, select the desired control from the Insert menu.
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


After you add page controls, you must set the record, label, use, and general properties of
each field. To set the page control properties:
1. Double-click the page control.
2. Set the Record properties.
3. Select each tab, and set the appropriate properties based on the specifications.
FOR
Slide 234 ______________________________________________________________________________________________________
Student Notes
INTERNAL
Once the properties of a page control have been set, the term page field is appropriate.
A page field is a page control that you have linked to a specific field in a record
definition.
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


You can insert related fields to make the page more informational to the user. Related
fields do this by accessing descriptive data from a different record.
Slide 235 ______________________________________________________________________________________________________
Student Notes
The Student Personal Data (PSU_STUDENT_PERS) page shows this related field:
FOR
INTERNAL
The Customer field and its related field, Description
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


This diagram illustrates the two parts to creating a related field:
PSU_STUDENT_TBL.CUSTOMER PSU_CUST_TBL.DESCR
FOR
INTERNAL
Step 1
USE
Two parts of a related field
ONLY! Step 2
Slide 236 ______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


To configure the display control field:
1. Double-click the primary field.
2. Select the Use tab.
3. Select the Display Control Field check box.
FOR
Slide 237 ______________________________________________________________________________________________________
Student Notes
INTERNAL
Configure the Display Control Field on the Use tab:
USE
ONLY!
Page field use properties for a display control field
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


To configure the related field:
1. Double-click the related field.
2. Select the correct record and field on the Record tab.
4. Select the Related Field check box.
FOR
5. Select the appropriate related control field from the drop-down list box.
INTERNAL
Slide 238 ______________________________________________________________________________________________________
Student Notes
USE
Configure the related field check box on the Use tab:
ONLY!
Page field use properties for a related field controlled by the Curriculum Developer field
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Some controls, such as the frame, group box, and horizontal rule are for adding visual
elements to the page.
Slide 239 ______________________________________________________________________________________________________
Student Notes
Notice the frame and group box in this illustration:
FOR
INTERNAL
USE
A page definition with aesthetic page controls in place
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 31: Adding Page Controls to a Page

• Add page controls.
• Set edit box properties.
• Set drop-down list box properties.
•
FOR
Set check box properties.
Set radio button properties.
Clean up the page.
INTERNAL
See PeopleTools I: Activity Guide, “Creating Page Definitions,” Activity 31: Adding
Page Controls to a Page.
Slide 240 ______________________________________________________________________________________________________
Student Notes USE

______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Creating Page Definitions

It is now time to create a new page definition for the T1_COURSE component. This
section discusses how to:
• Examine the technical specifications for the page definition.
• Create a new page definition and place page controls on it.
• Place page controls at the proper levels.
•
FOR
Set page field properties.
Create related fields.
•
INTERNAL
Set up radio buttons.
Slide 241 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Creating Page Definitions (continued)

Specifications normally include a drawing of the page that you plan to construct. In this
case, you start with a look at the completed page in the browser.
Slide 242 ______________________________________________________________________________________________________
Student Notes
The Course page will look like this screen shot:
FOR
INTERNAL
USE
ONLY!
The completed Course page
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


There is a simple way to create a page using the record definition in the project
workspace: Drag the record definition from the records folder onto the blank page.
Slide 243 ______________________________________________________________________________________________________
Student Notes
Drag the record icon onto the page:
FOR
INTERNAL
USE
ONLY!
New page showing project workspace
The record will expand to show all fields:

FOR
INTERNAL
USE
New page definition after you drag the record definition to the page
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


When you drag a record definition onto a page, most page properties are set by default.
Most pages, however, require a few adjustments such as labels and positioning.
Slide 244 ______________________________________________________________________________________________________
Student Notes
Notice the position of the labels:
FOR
INTERNAL
USE
ONLY!
Page showing correct labels in appropriate positions
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


On the Course page, the search key is in the Course Code field. It writes to the high level
key of the primary table. Key values are rarely editable on a page and must be display
only.
Slide 245 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


You must create any related fields specified in the documentation. This diagram shows
the source of the related fields:
T1_COURSE_TBL PSU_INSTR_TBL
COURSE INSTRUCTOR
EFFDT EFFDT
EFF_STATUS EFF_STATUS
DESCR DESCR
FOR
COURSE_TYPE BUSINESS_UNIT
LENGTH_DAYS LAST_NAME
TRAINING_UNITS FIRST_NAME
ONSITE CURR_DEV_FLAG
INSTRUCTOR COURSE_TYPE
APP_REL FACILITY
INTERNAL
TOOLS_REL PSIMAGEVER
PHOTO
Entity relationship diagram showing the source of the Instructor field
USE
Slide 246 ______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


The instructor field has two related fields to display first and last names.
Slide 247 ______________________________________________________________________________________________________
Student Notes
Notice the two related fields:
FOR
Curriculum Developer field with two related fields
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


You must configure and group all of the radio buttons on a page.
Slide 248 ______________________________________________________________________________________________________
Student Notes
Surround the radio buttons with a group box:
FOR
INTERNAL
Radio buttons in a group box
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 32: Creating Page Definitions

• Create a new page definition and place page controls.
• Set page control properties.
• Create related fields.
• FOR
Set up radio buttons.
Set page field properties.
INTERNAL
Building Pages.
Slide 249 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Implementing Scroll Areas and Grids

Scroll areas and grids divide a page into levels, creating a one-to-many relationship. This
section discusses:
• Placing scroll areas on a page.
• Placing grids on a page.
• Scroll area and grid properties.
FOR
Slide 250 ______________________________________________________________________________________________________
Student Notes
INTERNAL
The Customer Table page has a level 0 only:
USE
ONLY!
Example of a page with only level 0
The Products by Customer page has a scroll area that divides the page into a level 0 and a
level 1:

Example of a page with level 0 and level 1

FOR
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Implementing Scroll Areas and Grids (continued)

To create a scroll area, select the scroll area tool and drag it around the fields to be
enclosed in the scroll area.
Slide 251 ______________________________________________________________________________________________________
Student Notes
Notice that the scroll area surrounds a group of fields:
FOR
INTERNAL
USE
ONLY!
Page showing a scroll area
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Like scroll areas, grids also group fields into levels of data on a page, but they differ from
scroll areas in a number of ways:
Scroll Area Attributes Grid Attributes

Fields can be freely arranged. Fields are arranged in rows.
Data cannot be sorted by field. Data can be sorted by field (column).
Data cannot be downloaded to a spreadsheet. Data can be downloaded to a spreadsheet.
FOR
Slide 252 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Scroll areas group levels of data on a page:
• You can freely arrange fields within the scroll area.
• You can show multiple instances of data on a page.
Slide 253 ______________________________________________________________________________________________________
Student Notes
FOR
The Education scroll area shows multiple rows of data.
INTERNAL
USE
ONLY!
An example of a scroll area showing two rows of data
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Grids also group levels of data on a page, but their layout is less flexible; and as the name
implies, grids are displayed as rows and columns of data.
Slide 254 ______________________________________________________________________________________________________
Student Notes
A grid shows multiple rows of data:
FOR
INTERNAL
USE
An example of a grid with multiple rows of data
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


To create a grid, you insert a grid and then drag the fields into it. You can drag the fields
in either direction to place them as necessary.
Slide 255 ______________________________________________________________________________________________________
Student Notes
Drag a field from the appropriate record into the grid:
FOR
INTERNAL
USE
ONLY!
Dragging a field into a grid
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


After they are inserted, you must configure the properties of a scroll area or the grid.
They are very similar.
Slide 256 ______________________________________________________________________________________________________
Student Notes
A scroll area has General, Label and Use properties:
FOR
INTERNAL
USE
ONLY!
Scroll Area Properties dialog box
A grid has General, Label, and Use properties:
Grid Properties dialog box
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Although the page is visually correct, it is the page order, not the page layout, which
determines tabbing sequence or flow from field to field.
Click the Order tab to see the page order.
Slide 257 ______________________________________________________________________________________________________
Student Notes
FOR
Use the Order tab to verify processing order of the page:
INTERNAL
USE
ONLY!
The Order tab
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 33: Implementing Scroll Areas

• Insert a scroll area.
• Ensure proper page order.
Implementing Scroll Areas.
FOR
Slide 258 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 34: Implementing Scroll Areas and Grids

• Examine the page in the browser.
• Examine the scroll area on the page definition.
• Create a grid.
• View the results.
FOR
Implementing Grids and Scroll Areas.
INTERNAL
Slide 259 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Finalizing Page Design and Layout

Here are a few tools that help you create clean pages from the beginning. This section
discusses:
• Page size properties.
• Page control inspector.
• Alignment tools.
•
FOR
Page preview feature.
Slide 260 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Finalizing Page Design and Layout (continued)

The only page property setting that is changed in PeopleTools I is page size. Select File,
Definition Properties, and then select a predefined or custom page size.
Slide 261 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


There is a basic HTML compiler to preview the page in a browser. Select Layout, View
in Browser, and then select the appropriate browser. You can even add browsers to this
list.
Slide 262 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


The page control inspector is a floating window that contains a list of properties of the
selected control. Select View, Show Page Control Inspector to access this feature.
Slide 263 ______________________________________________________________________________________________________
Student Notes
The page control inspector makes it easier to align page controls:
FOR
INTERNAL
USE
ONLY!
Page control inspector
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Use the alignment tools to quickly line fields up with one another along the left, right,
top, or bottom margins, or along the center or middle axis. Select Layout, Align, and then
select the type of alignment that you need.
Slide 264 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 35: Finalizing Page Design and Layout

• Modify the page size.
• Use the page preview feature.
• Use the page control inspector.
FOR
Use the alignment tools.
Adding Final Touches.
INTERNAL
Slide 265 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 36: Building the Course Materials Page

• Insert page controls at level 0.
• Insert page controls at level 1.
• Create a related field.
FOR
Verify the page order.
Building the Course Materials Page.
INTERNAL
Slide 266 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Review
• You must adhere to basic design principles involving page level structure.
• There are a variety of page controls, each with unique properties that you must
configure.
• You place page controls on a page by inserting or dragging and dropping.
•
FOR
You build pages based on record definitions.
Grids and scroll areas control data that is associated with a higher level key.
•
INTERNAL
You can fine-tune page appearance with alignment tools, an HTML compiler, or a
definition inspector.
Slide 267 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 13
Defining Components
Objectives
•
FOR
Identify component definition basics.
• Define General and Use properties.
•
INTERNAL
Define Internet options for the component.
Build a new component.
USE
Slide 269 ______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Defining Components Lesson 13
Identifying Component Definition Basics

Defining the component is the sixth development step, as shown in this diagram:
Test Plan
Test Design
FOR
Register
INTERNAL
Define
Components Fields
Define Define
Components Records
USE
Pages
Build
Tables
Data Design
ONLY!
Component definition as part of the user interface phase of application development
Slide 270 ______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 13 Defining Components
Identifying Component Definition Basics (continued)

Component definitions group page definitions. A component can consist of a single page
or a set of pages, but a component is processed as one unit.
Slide 271 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


You combine component definitions with menu definitions to create a reference point for
the component in the navigation. This combination is also the basis for security access to
the pages on the component, which this diagram shows:
FOR
Relationship between component definitions, navigation, and security
INTERNAL
Slide 272 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


You must understand search records to develop an application successfully. The two
record types in PeopleSoft applications are:
• Primary record.
• Search record.
Slide 273 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


In some cases, the primary and search records are identical.
Slide 274 ______________________________________________________________________________________________________
Student Notes
Use the following navigation path to access this search page:
Page Name
FOR
General Information (search
page)
Navigation
Customers, General Information
Customer Table Customers, General Information
•
INTERNAL
The search page retrieves information from the PS_T1_CUST_TBL table:
USE
ONLY!
Search page for Customers, General Information
• The primary page for the Customer Table page is also the T1_CUST_TBL:

FOR
INTERNAL
USE
Customer Table page
See Also
Definitions”
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


In some cases, the primary and search records are different.
Slide 275 ______________________________________________________________________________________________________
Student Notes
Page Name
Products Purchased (search
page)
FOR
Navigation
Customers, Products Purchased
Products by Customer Customers, Products Purchased
•
INTERNAL
The Products Purchased search page searches customers, which are stored in the
• USE
customer (T1_CUST_TBL) table.
The Products by Customer page writes to the customer product (T1_CUST_PROD)

table:
ONLY!
Products by Customer page
See Also
Definitions”


On this component, you use T1_CUST_TBL as the search record for two reasons:
• The search record holds the high-level key for this component.
• This table contains no data to help users find a company if they do not know the
company code.
Slide 276 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


This diagram shows what happens when you insert data into the Customer Products page:
T1_CUST_TBL
Read key from
Search Record
FOR Level 0
Level 1
Write data to
INTERNAL T1_CUST_PROD
USE
Flow of information from search record to primary record
Primary Record
ONLY!
Slide 277 ______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Another basic element of a component is the action:
• You determine the actions that users can take on the pages in the component
definition not in the page definition.
• There are action buttons at the bottom of almost every page in the application.
• The four actions are: Add, Update/Display, History, and Correction.
FOR
Slide 278 ______________________________________________________________________________________________________
Student Notes
INTERNAL
Use the following navigation path to access this definition:

T1_CUST_TBL File, Open.
USE Select Component from the Definition dialog box.

Select File, Definition Properties.
Click the Use tab.
•
ONLY!
Notice the action options in the component.
Actions
• These four buttons show the actions users can take:
The four action buttons
Note. Notice that the action buttons on the page display different text than is seen in the
component.


This table explains that the way you configure the component definition determines the
buttons that appear at the bottom of the page:
Button Component Property Function

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.
Update/Display
Include History
FOR
Update/Display
Update/Display All
Enables viewing of data at all levels and inserting
of new rows at levels below zero.
Enables viewing of current and history rows. You
can insert new rows if the effective date of new
INTERNAL
Correct History Correction
rows is later than that of the current row. You can
insert and update future rows. Used on effective-
dated records only.
Enables editing of data for all rows. Used on
USE
effective-dated records only
Slide 279 ______________________________________________________________________________________________________
Student Notes
ONLY!
Note. Remember that you grant all possible actions. You will restrict actions later
through security features.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 37: Identifying Component Definition Basics

• Examine the T1_CUST component.
• Examine the T1_CUST_PROD component.
See PeopleTools I: Activity Guide, lesson 13 “Creating Page Definitions,” Activity 37:
Identifying Component Definition Basics.
FOR
Slide 280 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Defining General and Use Properties

When you open a component definition, you see the pages that are attached to that
component on the Definition tab.
Slide 281 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Defining General and Use Properties (continued)

The Structure tab on a component definition provides information about page levels and
component records and their roles. You also place PeopleCode here.
Slide 282 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


You configure a component by using its Component Properties dialog box. There are
three available types of properties noted by their tabs:
• Use the General tab to configure descriptive information about the component.
• Use the Use tab to set up the search and action properties.
• Use the Internet tab to set up display options for the browser.
FOR
Slide 283 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


You must configure at least two areas on the Use tab.
Slide 284 ______________________________________________________________________________________________________
Student Notes
You must configure the search record and the actions for a component:
FOR
INTERNAL
USE
ONLY!
Component Properties dialog box
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Defining Internet Properties

You configure many property settings for component definitions on the Internet tab of the
Component Properties dialog box. This section discusses:
• Search page options.
• Page navigation and processing modes.
• Toolbar selections.
FOR
Slide 285 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Defining Internet Properties (continued)

You can configure how the search page appears when a user selects a content reference.
Slide 286 ______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


You configure multi-page navigation with:
• Tabs at the top of each page in a component.
• Links at the bottom of the component.
Slide 287 ______________________________________________________________________________________________________
Student Notes
FOR
Notice the folder tabs at the top of the page and the links at the bottom of the page:
INTERNAL
USE
ONLY!
Multipage navigation options
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Using this dialog box, you also configure:
• Processing mode options.
• Toolbar options.
• Pagebar options.
FOR
Slide 288 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Building New Components

Review the technical specifications for the T1_COURSE component, as shown in this
table:
Component Element Value or Setting

Pages T1_COURSE
Page labels General Information
Search record T1_COURSE_TBL
Actions
FOR Add
Update/Display
Update/Display All
INTERNAL
Default search mode
Default search action
Correction
Advanced
Update/Display
Toolbar buttons
USE Save
Return to List
Next in List
Previous in List
Add
Update/Display
Update/Display All
Correction
ONLY!
Slide 289 ______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Building New Components (continued)

After you review the specifications, you will create a component, place the page in it, and
enter the item label. To create a component:
2. Select Component from the New Definition dialog box.
3. Drag the desired page from the project workspace into the component.
FOR
4. Double-click in the Item Label field.
5. Enter the name of the page in title case in this field.
INTERNAL
Slide 290 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Next, you must set the component use properties. You will:
1. Set the search record.
2. Set the actions.
Slide 291 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Set the component Internet properties and save the component. You will:
1. Set the search page options.
2. Set the page navigation and processing modes.
3. Set the toolbar options.
Slide 292 ______________________________________________________________________________________________________
Student Notes FOR

INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 38: Building a Component Definition

• Add pages to a new component definition.
• Set component use properties.
• Set component internet properties.
FOR
See PeopleTools I: Activity Guide, lesson 13, “Defining Components,” Activity 38:
Building a Component Definition.
Slide 293 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 39: Building the T1_COURSE_MATL Component

• Examine the technical specifications.
• Add pages to a new component definition.
• Set component use properties.
FOR
Set component internet properties.
See PeopleTools I: Activity Guide, lesson 13, “Defining Components,” Activity 39:
Building the T1_COURSE_MATL Component.
INTERNAL
Slide 294 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Review
• The basic elements of a component are the pages, the labels, the properties, and the
structure.
• The search record and the actions are required use properties.
• Internet properties determine the appearance of the search page and other pages in the
•
component.
FOR
You can build a component by dragging pages from the project workspace and
setting use and internet properties.
INTERNAL
Slide 295 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 14
Registering Components
Objectives
•
FOR
Explain component registration.
• Examine menu definitions.
•
INTERNAL
Identify elements of PeopleSoft security.
Navigate the portal registry.
•
USE
Plan component registration.
Register a component.
ONLY!
Slide 297 ______________________________________________________________________________________________________
Student Notes
To display your development efforts in a browser, you register the component.
You register components with the Registration Wizard. The wizard gathers information,
then attaches the component to a menu, assigns a permission list to allow security access
rights, and places a content reference entry in the portal registry, exposing the component
in the user navigation.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Registering Components Lesson 14
Explaining Component Registration

Registering the component is the final step in the user interface phase, as this diagram
illustrates:
Test Plan
Test Design
FOR
INTERNAL
Register
Components
Define
Define
Fields
Define
USE
User Interface
Components
Define
Pages
Build
Tables
Records
Data Design
ONLY!
Registering components in the user interface phase of application development
Slide 298 ______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 14 Registering Components
Explaining Component Registration (continued)

The Registration Wizard performs three tasks:
• Attaches a component definition to a menu definition
• Assigns access rights through security.
• Assigns navigation rights through the portal registry.
FOR
Slide 299 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Examining Menu Definitions

To understand the basics of menu definitions, you need to understand how menu
definitions are used in PeopleTools 8.4:
• Menu definitions are containers for components.
• For the security or navigation setup to recognize a component definition, it must be in

a menu.
FOR
Slide 300 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Examining Menu Definitions (continued)

There are two important elements in a menu definition:
• Bar items, which compartmentalize the menu.
• Menu items, which are links to components.
Slide 301 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Examining Menu Definitions (continued)

The Registration Wizard links the component to the menu definition. However, to make
the connection manually, rather than using the wizard:
1. Open the menu definition.
2. Double-click the bar item
3. Drag the component definition to the empty spot at the bottom of the menu item list.
FOR
4. Save the menu definition.
Slide 302 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 40: Examining Menu Definitions

In this activity, you will review the activity overview and examine a menu definition.
See PeopleTools I: Activity Guide, lesson 14, “Registering the Component,” Activity 40:
Examining Menu Definitions.
Slide 303 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Identifying PeopleSoft Security Basics

You design application security around three elements:
• Permission lists
• Roles
• User IDs
FOR
Slide 304 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Identifying PeopleSoft Security Basics (continued)

This diagram shows a partial map of the security plan for the PSU Training application:
PSU1525 PSU 3000

Instructor PSU ALLPAGES
Evaluation Purchasing
Permission Lists
PSU2000 PSU1100 PSU1500

Course
FOR
Course Student
Delivery Administration Evaluation
Roles
INTERNAL Instructor
Training
Administrator
Student
Application
Developer
RCASTILLO CFULLER ENG PTTRN

User IDs
USE DBORDIER JJONES
JSMITH
ONLY!
PSU Training security plan
Slide 305 ______________________________________________________________________________________________________
Student Notes
Notice the user IDs. If CFULLER signs on to the database, any permissions associated
with the Training Administrator role will be available to her. Likewise, any permissions
associated with the Student role will be available to the user IDs, ENG, JJONES, and
JSMITH.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


A permission list contains information about component access. Use the permission list
pages to:
• Add Menu definitions to the permission list.
• Edit the components that the user accesses.
• Edit the page in the component that the user accesses.
•
FOR
Edit the actions in the component that the user accesses.
Slide 306 ______________________________________________________________________________________________________
Student Notes
INTERNAL
Use the Pages page to insert a menu definition:
USE
Permission List PSU1300 PeopleTools, Security, Permissions & Roles, Permission Lists
ONLY!
Pages page
Use the Edit Components link on the Pages page to grant specific component, page, and
action rights.
Note. You insert a menu in the grid. Unless you have previously attached a component to
a menu, you cannot grant access to that component.
See Also
PeopleTools 8.44 PeopleBook: Security Administration, “Working with Permission
Lists”


To configure access at the page definition level:
1. Insert a menu definition.
2. Click the Edit Components link.
3. Select the desired component and click the associated Edit Pages link.
4. Select the desired pages and actions.
FOR
Slide 307 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Roles generally have names that describe a job or function. To manually configure a role:
1. Select the Permission Lists page.
2. Insert the permission list that you want to access.
3. Save the role.
Slide 308 ______________________________________________________________________________________________________
Student Notes FOR

Use the Permission Lists page to assign permission lists to roles:
Page Name
INTERNAL
Permission Lists
Navigation
PeopleTools, Security, Permissions & Roles, Roles
USE
ONLY!
Permission Lists page
See Also
PeopleTools 8.44 PeopleBook: Security Administration, “Working with Roles”
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


You use user IDs to sign on. During this class, you have been signing on as user
PTOOLS1. The security access for this user is determined by:
• The roles attached to the PTOOLS1 userID.
• The permission lists attached to those roles.
Slide 309 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


You assign roles to user IDs on the Roles page.
Slide 310 ______________________________________________________________________________________________________
Student Notes
Use the Roles page to assign roles to a user ID:
Page Name
Roles FORNavigation
PeopleTools, Security, Permissions & Roles, Roles
INTERNAL
USE
ONLY!
Roles page
See Also
PeopleTools 8.44 PeopleBook: Security Administration, “Working with User Profiles”
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 41: Identifying PeopleSoft Security Basics

1. Examine roles.
2. Examine permissions.
3. Sign in as a different user.
4. Record your findings.
FOR
Identifying PeopleSoft Security Basics.
INTERNAL
Slide 311 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Navigating the Portal Registry

The structure and content pages consist of three sections:
• Use the breadcrumbs section to indicate the level at which you are working.
• Use the folders scroll area to create and modify folders.
• Use the content references scroll area to create and modify content references.
FOR
Slide 312 ______________________________________________________________________________________________________
Student Notes
Page Name
INTERNAL
Structure and Content
Navigation
PeopleTools, Portal, Structure and Content
•
USE
Use the Structure and Content page to create and alter the navigational hierarchy:
ONLY!
Breadcrumbs
Folders
Content References
Breadcrumbs, folders, and content references in the Structure and Content page.
See Also
PeopleTools 8.44 PeopleBook: Internet Technology, “Working with the Registry and
URLs”

PeopleTools 8.44 PeopleBook: Internet Technology, “Implementing Portals”
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Navigating the Portal Registry (continued)

The Registration Wizard configures the portal registry. The Registration Wizard:
• Creates a content reference and configures its properties.
• Places the content reference in an existing folder.
Slide 313 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Navigating the Portal Registry (continued)

Although the Registration Wizard creates content references for you, you can create a
content reference manually. To create a content reference manually:
1. Navigate to the Structure and Content component.
2. Create a new content reference in a folder.
3. Enter properties for the content reference.
FOR
Slide 314 ______________________________________________________________________________________________________
Student Notes
• Name. INTERNAL
Properties of a content reference include:
• Label.
•
USE
Long description.
Sequence number.
•
ONLY!
Menu and component names.
In addition, you can effective-date content references.
Note. This topic is covered in detail in the PeopleSoft Enterprise Portal Administration
course.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 42: Navigating the Portal Registry

1. Examine breadcrumbs.
2. Examine folders.
3. Examine content references.
4. Examine the menu pagelet navigation.
FOR
Navigating the Portal Registry.
INTERNAL
Slide 315 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Planning Component Registration

The most difficult part of the registration process is planning your needs before you start
the wizard. Examine your detailed technical specifications closely before running the
Registration Wizard and entering values.
Slide 316 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Planning Component Registration (continued)

Menu definitions no longer generate the user interface. You select the menu definition for
your component based on a few simple rules:
• Avoid using menu definitions delivered with PeopleSoft applications.
• Create menu definitions that make sense as containers for objects, without concern
for navigation.
•
FOR
Consider using menu bar items for organizational purposes.
Slide 317 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Associating permission lists with components is the security administrator’s job. You
might be playing this role eventually, but it’s not part of the development process.
Slide 318 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Before beginning development, you should document, in the technical specifications, the
folder where you place content references. You need to know two things about the
Registration Wizard:
• You must know the name of the folder.
• You cannot browse through the portal structure from the Registration Wizard.
FOR
Slide 319 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


The label is what the user sees in the navigation. Label characteristics include:
• Labels are limited to 30 characters.
• Label text should clearly indicate the purpose of the underlying component.
• Subordinate labels should not repeat higher-level folder information.
FOR
Slide 320 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Characteristics of the description include:
• The content reference description is a text string of up to 255 characters.
• The text appears in the interface when users point the mouse over a content reference
• Use this description to expand on the description in the label.
FOR
Slide 321 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Registering the Component

The Registration Wizard automates the manual process that you have just seen. However,
you begin the automatic process as you would the manual process. Start with a glance at
the technical specifications. This table shows the specifications for menu information:
Property Value or Status

Menu definition 0400_PTOOLS1
Bar item STUDENT
FOR
Slide 322 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Registering the Component (continued)

This table shows the specifications for navigational information:

Portal registry folder T1_COURSES
Content reference label Course Details
Content reference long description Create, view, or edit details about PSU courses
Sequence
FOR 10
Slide 323 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


This table shows the specifications for security information:

Permission List CPPT0400
Add Action Selected
Update/Display Action Selected
Update/Display All Action
Correction Action
FOR Selected
Selected
Slide 324 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


This table shows the specifications for project information:

Menu Selected
Registry entry Selected
Permission list Selected
FOR
Slide 325 ______________________________________________________________________________________________________
Student Notes
When you finish registering a component, many of the properties that you entered are
INTERNAL
saved and will appear as defaults when you register the next component.
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 43: Registering the Component

1. Open the Registration Wizard.
2. Select the menu definition.
3. Configure the content reference.
4. Assign the permission list.
5. Add project options.FOR

INTERNAL
Registering the Component.
Slide 326 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 44: Registering the T1_COURSE_MATL Component

1. Open the Registration Wizard.
2. Select the menu definition.
3. Configure the content reference.
4. Assign the permission list.
5. Add project options.FOR

See PeopleTools I: Activity Guide, lesson 14, “Registering Components,” Activity 44:
INTERNAL
Registering the T1_COURSE_MATL Component.
Slide 327 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Review
• Component registration consists of placing a component on a menu, configuring the

content reference properties, and establishing security.
• Menu definitions are component repositories, not navigational structures.
• PeopleSoft security is based on permission lists, roles, and user IDs.
•
FOR
You can enter and configure content references through the browser, by selecting
PeopleTools, Portal, Structure & Content.
• Before you run the Registration Wizard, analyze the tasks that it performs and have a
•
INTERNAL
project plan with you during the registration process.
The Registration Wizard saves development time by attaching components to menu

definitions, creating content references in the portal registry, and assigning a
USE
permission list to the component and the content reference.
Slide 328 ______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 15
Testing an Application
Objectives
•
FOR
Create and analyze test plans.
• Test applications.
• INTERNAL
Troubleshoot common issues.
Slide 330 ______________________________________________________________________________________________________
Student Notes USE

Before releasing new or modified applications, you must perform a rigorous test to ensure
online functionality and data integrity. You test your new application by:
•
ONLY!
Adding, deleting, and modifying data.
Confirming default values and prompt lists.
• Examining application data.
• Using the DBMS query tool to verify data in the database.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Testing an Application Lesson 15
Creating and Analyzing Test Plans

The fourth phase is composed of one step, as illustrated in the following diagram. If you
find problems, you move back to the appropriate step to resolve it, and walk through the
testing process again until you are ready to go to production.
FOR
Test Plan
Test Design
INTERNAL Register
Components
Define
Fields
USE Define
Components Define
Records
ONLY! Pages Tables
The testing phase of application development
Slide 331 ______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 15 Testing an Application
Creating and Analyzing Test Plans (continued)

Before you start, however, be aware of dependencies the application might have on other
tables in the database. You are especially interested in search record dependencies.
Slide 332 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


The specification calls for default values on certain fields. These default values were
determined at the record definition level. During testing, confirm the presence of the
defaults values as you add or insert rows.
Slide 334 ______________________________________________________________________________________________________
Student Notes
T1_COURSE_TBL
FOR

File, Open
INTERNAL Select Record from the Definition drop-down list box.
•
USE
Use the record definition to determine default values:
ONLY!
T1_COURSE_TBL record definition
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


You configured three types of prompts for data validation in this record definition. The
test plan should include:
• Testing translate table prompts.
• Testing yes/no prompts.
• Testing prompt table prompts.
FOR
Slide 335 ______________________________________________________________________________________________________
Student Notes
Page Name
INTERNAL
Navigation
T1_COURSE_TBL File, Open
USE Select Record from the Definition drop-down list box.
•
ONLY!
Use the record definition to examine prompts:
T1_COURSE_TBL record definition
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Tableset sharing is a form of data validation where users are limited to certain choices
based on the business rules that were set up for the prompt tables. If your component
includes tableset sharing, you must:
• Determine the rules.
• Document the expected behavior of the affected prompts.
FOR
Slide 336 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 45: Creating and Analyzing Test Plans

In this activity, you will review the activity overview and formulate a test plan.
See PeopleTools I: Activity Guide, lesson 15, “Testing an Application,” Activity 45:
Creating and Analyzing Test Plans.
Slide 337 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Testing Applications
Because the T1_COURSE component uses the same record for both search and primary,
you expect the PS_T1_COURSE_TBL table to be empty. Therefore, this test includes:
• Adding high-level keys.
• Inserting rows.
• Checking default values.
•
FOR
Verifying data validation prompts.
Testing effective-dated logic.
INTERNAL
Slide 338 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 46: Testing Applications

• Check for data dependencies.
• Add high-level keys.
• Insert rows.
•
FOR
Check default values.
Verify data validation prompts.
Test effective-dating logic.
INTERNAL
See PeopleTools I: Activity Guide, lesson 15, “Testing an Application,” Activity 46:
Testing Applications.
Slide 339 ______________________________________________________________________________________________________
Student Notes USE

______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Troubleshooting Common Issues

Here are some issues that you may find during testing. This chart describes issues that
result from mistakes in a field definition:
Problem Configuration Option

Drop-down list boxes or radio buttons don’t include In the field definition, open the properties dialog box
all required values. and select the Translate Values tab.
Check the effective date of translate value.
Field label is incorrect.
FOR
Data entered is in the wrong format (all uppercase or
mixed case).
Check the label IDs in the field, record, and page
definitions.
Check the format in the field definition. Use caution;
a change here can affect many areas of the
INTERNAL
Not enough characters are allowed in a field.
application.
Check the length in the field definition. Use caution;
a change here can affect many areas of the
application.
USE
Slide 340 ______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Troubleshooting Common Issues (continued)

This chart describes issues that result from mistakes in a record definition:

Duplicate key error messages Check the key structure. If you make changes
remember to rebuild (or alter) the table or recreate
indexes.
Search page not correct Check the key, alternate search key, and list box
FOR
Default values missing or incorrect
Prompt not available or prompting to wrong table
settings of the search record.
Check record field use properties.
Check record field edits properties.
Slide 341 ______________________________________________________________________________________________________

USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


This chart describes issues that result from mistakes in creating the SQL table:

SQL errors when accessing search page or Verify that the table exists. Determine whether
component someone modified the record definition but did not
alter the underlying table. Build or alter from record
if required.
FOR
Slide 342 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


This chart describes issues that result from mistakes in a page definition:

High-level key can be edited. Check page field properties for display-only setting.
Alignment of controls on the screen is off. Check page definition.
There is no data in a related field. Check the page field properties for control and
related field settings, plus the field settings for the
Label text is incorrect.

FOR related field. It should be pointed to a field in the
prompt table.
Check page field properties.
Slide 343 ______________________________________________________________________________________________________

USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


This chart describes issues that result from mistakes in a component definition:

Label on page tabs is incorrect. Check the component definition for the Item Label
and Folder Tab Label fields.
You want different defaults for the initial search Check Component Properties, Internet tab.
page.
FOR
Search page shows inappropriate fields.
Inappropriate actions available to user.
Incorrect or inappropriate buttons appear on bottom
Check Component Properties, Use tab.
Check Component Properties, Use tab.
Check Component Properties, Internet tab.
of display.
INTERNAL
Slide 344 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


This chart describes issues that result from mistakes in component registration:

Content reference is not visible. Examine the portal registry for content reference
security. Save the content reference to refresh
permission list associations.
An access error appears when clicking a content Examine the permission list and check page security
reference.
FOR
Search page title is cryptic text.
settings. Examine content reference in portal registry
and verify names of component and menu definition.
Open menu definition and edit menu item label.
Inappropriate text appears for content reference label Edit content reference in the portal registry.
INTERNAL
or description.
Slide 345 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 47: Testing More of the Training Application

• Check for data dependencies.
• Insert rows.
• Check default values.
FOR
Verify data validation prompts.
See PeopleTools I: Activity Guide, lesson 15, “Testing the Application,” Activity 47:
Testing More of the Training Application.
INTERNAL
Slide 346 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Review
• It is important to create a test plan that will check for data dependencies, test key
structure, verify default values and validation tables, and examine effective dating
logic.
• After formulating a test plan based on the guidelines above, you implement the plan
by entering data.
•
FOR
It is important to methodically trace any problems to the definition that is causing it,
and then walk through the remaining steps of development.
Slide 347 ______________________________________________________________________________________________________

______________________________________________________________________
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 16
Editing the Registry Structure
Objectives
•
FOR
Describe content organization in PeopleTools 8.44 navigation.
• Create new folders.
•
INTERNAL
Move folders or content references to new parent folders.
Delete folders.
USE
Slide 349 ______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Editing the Registry Structure Lesson 16
Discussing Content Organization in PeopleTools 8.44 Navigation

Navigation in enterprise applications based on PeopleTools 8.44:
• Is derived from the contents of the portal registry.
• Has changed significantly from previous PeopleTools releases, in which navigation

was derived from menu definitions.
• Allows for a single navigational taxonomy that spans multiple application databases.
FOR
Slide 350 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 16 Editing the Registry Structure

(continued)
When considering what makes up a content reference in the navigation, ask these
questions:
• Which node contains the content?
• Which portal registry are you using?
• FOR
Which folder holds the content reference?
Where does the content reference point?
Slide 351 ______________________________________________________________________________________________________

USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


(continued)
The answers to the questions depend partly on your license agreement. There are three
license agreement categories:
• PeopleSoft application.
• PeopleSoft application with portal pack.
•
FOR
PeopleSoft Enterprise Portal.
Slide 352 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


(continued)
All PeopleSoft applications provide access to application content by navigation and
Verity search. Each application suite maintains its own server processes and database, as
this diagram shows:
Home Pages Web Server Server Databases
FOR HRMS PIA HRMS Domain HRMS
INTERNAL CRM PIA CRM Domain CRM
USE
PeopleSoft application architecture
ONLY!
Slide 353 ______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


(continued)
Portal packs are aligned by product lines and include pagelets as well as a personalized
homepage with multiple tabs.
This diagram illustrates an application portal:
Home Pages Web Server Server Databases
HR
HR
HR
HR
FOR HRMS PIA HRMS Domain HRMS
INTERNAL
CRM
CRM
CRM
USE
CRM PIA CRM Domain CRM
CRM
PeopleSoft application with portal pack architecture
ONLY!
Slide 354 ______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


(continued)
PeopleSoft Enterprise Portal runs on its own database and can aggregate content and
portal packs across multiple PeopleSoft application databases, as well as any other
content that you want to deploy in the portal, as this diagram shows:
Web Server Server Databases
FOR
HRMS PIA HRMS Domain HRMS
INTERNAL
Home Page
CRM PIA CRM Domain CRM
HR
CRM
CRM
HR
HR
USE
PeopleSoft Enterprise Portal architecture
Portal PIA Portal Domain Portal
ONLY!
Slide 355 ______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


(continued)
Navigation standards in previous releases were based on menu bar item names that held
links to content. There were five standard menu bar item names:
• Use
• Inquire
•
Setup
Process FOR
• Report
INTERNAL
Slide 356 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


(continued)
In PeopleTools 8.4, navigation is organized around functional areas and business
processes. This diagram shows a simple example of how you might map a business
process:
Administer a Training Class
FOR
Self Service
On-line
Enrollment
INTERNAL
Minimum
Threshhold?
Yes
Assign
Instructor
Prepare
Classroom
Deliver
Course
Course
Evaluation
Training
USE
No
Cancel Class
Billing
ONLY!
Pages mapped to tasks in a business process
Slide 357 ______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


(continued)
The top level of folders represents the functional areas. Folders can contain other folders
or content references. This diagram shows how the navigation might look based on a
simple business process:
Self Service
FOR
Enroll in Training
Training
INTERNAL Class Administration

Classroom Assignments
USE Classroom Preparation

Course Evaluations
Collect Fees
ONLY!
Navigation for administering a training class
Slide 358 ______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


(continued)
Keep in mind these rules as you develop your navigation:
• Aim for a flat taxonomy.
• Users should be able to access a content reference with no more than three clicks
(two folders plus a content reference).
• FOR
Long descriptions for content references should be in sentence case without periods.
Do not repeat a term in a folder and in the content reference.
• The order of content references should match the steps in the business process, where
•
INTERNAL
possible.
Limit the contents of a folder to 14 folders and content references combined.
USE
Slide 359 ______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 48: Examining the Portal Registry

1. Examine the default node.
2. Examine the default portal.
3. Examine folder configuration settings.
4. Examine content reference configuration settings.
FOR
See PeopleTools I: Activity Guide, lesson 16, “Editing the Registry Structure,” Activity
48: Examining the Portal Registry.
INTERNAL
Slide 360 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Creating Folders
You must create a folder before running the registration wizard. This section discusses
how to:
• Name folders.
• Create new folders.
• Verify that folders appear in navigation.
FOR
Slide 361 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Creating Folders (continued)

Follow these guidelines when naming new folders:
• Each folder in the portal registry must have a unique name.
• A folder name can be up to 30 characters long.
• Use a naming convention to help you identify new folders.
FOR
You might want to include in the name a clue to the location of the folder.
Slide 362 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


To create a folder in the portal registry:
1. Select PeopleTools, Portal, Structure and Content.
2. Select the Add Folder link.
3. Enter the appropriate text in the Folder Administration page.
4. Click Save.
FOR
Slide 363 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Once you create the folder, you will need to verify the folder’s existence. To verify a
folder’s existence:
1. Click the Refresh button on the browser.
2. Click the folder to view its contents.
Slide 364 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 49: Creating Folders in the Portal Registry

1. Create a folder.
2. Verify that the folder appears in the taxonomy.
49: Creating Folders in the Portal Registry.
FOR
Slide 365 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Moving Folders or Content References to New Parent Folders

A folder can contain a number of content references and folders, and those folders
usually have more content references. When you move a folder, you graft it like the
branch of a tree to a new location. All subordinate content moves with it, like the twigs
and leaves of a tree.
Slide 366 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Moving Folders or Content References to New Parent Folders (continued)

To move a folder and its subordinate content to a new location in the navigation:
1. Select PeopleTools, Portal, Structure and Content.
2. Select a folder.
3. Click the Edit link to move the folder that is beside the link
4. Click the Select New Parent Folder button.
FOR
5. Navigate to the new folder and click the folder name.
Slide 367 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 50: Moving Folders or Content References

1. Move folders.
2. Verify that folders appear in the navigation.
See PeopleTools I: Activity Guide, lesson 16, “Editing the Registry Structure” Activity
50: Moving Folders or Content References.
FOR
Slide 368 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Deleting Folders
Before deleting a folder, you must assess the impact of deletion, because:
• Deleting a folder deletes everything in it.
• There is no undo option.
Slide 369 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Deleting Folders (continued)

If you no longer need a folder and you have minimized the impact, you should delete it
from the portal registry. To delete a folder:
1. Click the Delete button for the desired folder.
2. Click OK in the warning dialog box.
FOR
Slide 370 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 51: Deleting Folders in the Portal Registry

1. Delete the My Test folder from the portal registry.
2. Verify that the My Test folder was deleted.
51: Deleting Folders in the Portal Registry.
FOR
Slide 371 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 52: Working with Folders in the Portal Registry

1. Create a folder.
2. Move a content reference.
52: Working with Folders in the Portal Registry.
FOR
Slide 372 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Review
• You organize all user-accessible content in the portal registry by using functional
areas and business processes as guidelines for constructing user navigation.
• New folders are created in the Structure and Content component of the portal
registry.
•
taxonomy.
FOR
You can move existing folders, along with their content, to other areas of the
Deleting a folder or content reference from the portal registry is a quick process but
can have broad consequences.
INTERNAL
Slide 373 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 17
Creating Menu Definitions
Objectives
•
FOR
Describe the purpose of a menu.
• Locate a component on a menu.
•
INTERNAL
Edit menu item labels.
Create menu definitions.
USE
Slide 375 ______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Creating Menu Definitions Lesson 17
Describing the Purpose of a Menu

The term menu implies user navigation. As of PeopleTools 8.4, however, menu
definitions no longer generate navigation. Instead, menus:
• Are placeholders for components.
• Create logical groupings for security.
• Establish a link to the portal registry.
FOR
Slide 376 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 17 Creating Menu Definitions
Describing the Purpose of a Menu (continued)

Menu definitions consist of three elements:
• Menu name
• Bar item name
• Menu item
FOR
Slide 377 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Locating a Component on a Menu

The registration wizard places a component on a menu. If you do not remember with
which menu you associated a specific component:
1. Navigate to the component.
2. Press CTRL+J.
Slide 378 ______________________________________________________________________________________________________
Student Notes
FOR
Press CTRL+J to see definition names:
INTERNAL
USE
ONLY!
Definition names
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Locating a Component on a Menu (continued)

When you know the name of the menu and the component, you open them in the
PeopleSoft Application Designer.
Slide 379 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Editing Menu Item Labels

When you select a content reference, a search page loads. Every search page has a title.
The title should match the content reference to maintain consistency in the look of the
application.
Slide 380 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Editing Menu Item Labels (continued)

When you register a component, the search page titles do not match the content reference
labels, as is the case for the Course Details and the Course Materials components that you
created in class.
Slide 381 ______________________________________________________________________________________________________
Student Notes
FOR
This diagram shows a search page title and a menu item label:
INTERNAL
USE
ONLY!
Search page title
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Editing Menu Item Labels (continued)

To change menu item labels:
1. Open the menu definition.
2. Select the bar item under which the menu item resides.
3. Double-click the menu item.
4. Enter the new label.
FOR
5. Save the menu definition.
Slide 382 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 53: Editing Menu Item Labels

In this activity, you will review the activity overview and change menu item labels.
See PeopleTools I: Activity Guide, lesson 17, “Creating Menu Definitions, Activity 53:
Editing Menu Item Labels.
Slide 383 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Creating Menu Definitions

PeopleSoft applications have many existing menu definitions. When developing, you
must determine whether to:
• Use an existing definition.
• Create a new one.
Slide 384 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Creating Menu Definitions (continued)

You create menu definitions in the same as any other definition in PeopleSoft
Application Designer. To create a menu definition:
2. Select Menu from the New Definition dialog box.
FOR
4. Select the Standard menu type radio button.
INTERNAL
Slide 385 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


After selecting a new menu definition, you add bar items to the new menu. To add a bar
item to the menu:
1. Double-click the empty rectangle with dashed lines.
2. Enter a name that is unique to this menu.
3. Enter a label.
FOR
Slide 386 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


To save a menu definition you must include at least one bar item and at least one menu
item. The easiest solution is to place a separator bar as a menu item under the bar item
itself. Otherwise, to configure a menu item:
1. Double-click the empty rectangle with dashed lines under the new bar item.
2. Select Component radio button from the Type field.
4. Select File, Save. FOR

5. Enter data in the Save As field.
INTERNAL
Slide 387 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 54: Creating a Menu Definition

1. Create a menu definition.
2. Add a bar item.
3. Add a separator bar to the menu item.
4. Save a menu definition.
FOR
See PeopleTools I: Activity Guide, lesson 17, “Creating Menu Definitions,” Activity 54:
Creating a Menu Definition.
INTERNAL
Slide 388 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Review
• Menu definitions were used to construct user navigation in previous PeopleSoft

releases, but in PeopleTools 8.4, menu definitions act as containers for components,
providing links to security and the portal registry.
• Developers should open the menu definition and edit the item label to match the
content reference label.
•
FOR
You should create at least one menu definition to hold custom components; this will
save you from having to reregister components when you upgrade your application.
• Creating a menu definition is a four-step process.
INTERNAL
Slide 389 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 18
Analyzing the Impact of Design

Changes
Objectives
FOR
• INTERNAL
Determine relationships among definitions.
Synchronize record definitions and database tables.
• Incorporate upgrades in the development strategy.
USE
Slide 391 ______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Analyzing the Impact of Design Changes Lesson 18
Determining Relationships Among Definitions

If you determine that new configurations are necessary, try to keep specialized
configurations to a minimum. This way you can:
• Implement the application more quickly.
• Upgrade smoothly.
Slide 392 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 18 Analyzing the Impact of Design Changes
Determining Relationships Among Definitions (continued)

You design definitions before you develop applications. This diagram shows the
relationship among application definitions:
Field
Field Record Page
Field
Field FOR Table
INTERNAL
Relationship among application definitions
Slide 393 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Determining Relationships Among Definitions (continued)

To determine the definitions that are affected by a change to an existing definition, you
can:
• Use the PeopleSoft Application Designer Find Definition References tool.
• Use the PeopleTools Cross Reference page.
Slide 394 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 55: Determining Relationships Among Definitions

1. Find definition references.
2. Using the Record Cross Reference page.
See PeopleTools I: Activity Guide, lesson 18, “Analyzing the Impact of Design
Changes,” Activity 55: Determining Relationships Among Definitions.
FOR
Slide 395 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Synchronizing Record Definitions and Database Tables

Data is stored in SQL tables, which are based on record definitions. Changes to field
definitions or record definitions often make the underlying table no longer synchronized
with the record definition. To remedy this problem without losing application data, use
the Alter option of the Build operation.
Slide 396 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Synchronizing Record Definitions and Database Tables (continued)

If you change either a field definition or a record definition, you might have to alter the
associated SQL table to synchronize it, depending on the changes.
Slide 397 ______________________________________________________________________________________________________
Student Notes
Use this table to determine what actions you must perform when you change a record
definition:
Properties
FOR
Table Structure Changes
(Create or Alter Table)
Index Changes
(Create Index)
Definition Changes
(Do Nothing)
Field
INTERNAL
Field name
Length
Type
Delete/Add field from record
NA Format
Long name
Short name
Translate table values
Use USE
definition
NA Key (new)
Alternate search key
Search key (if already a
key)
Key direction List box item
ONLY! (ascending or
descending)
Duplicate order key
Defaults (value and page
control)
Auto update
Field audits
Edits Value Required (Long Character, NA Prompt table edit
Date, Time, DateTime, Image) Translate table edit
Yes/No edit
Value required (Numeric,
Character)
Reasonable date check
PeopleCode NA NA PeopleCode
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


If you make a change that requires an update to an index only:
1. Open the record definition.
2. Select Build, Current Definition.
3. Select Create Indexes.
4. Select a build execute option.
FOR
5. Click the Build button.
Slide 398 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


If you change the table structure, you must either build or alter the table. The alter table
process is similar to the create table process, except that you do not lose the data that
application data tables contain.
Slide 399 ______________________________________________________________________________________________________
Student Notes
FOR
It is important to remember that if you alter a table, you must rebuild any views that
reference the altered table. You must also recompile any COBOL programs that reference
the altered table.
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


The Alter tab of the Build Settings dialog box provides options for handling existing data.
You can:
• Drop columns even if they hold data.
• Skip records if they contain data.
• Truncate data.
•
FOR
Set the specific type of alter options that you would like.
Slide 400 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 56: Synchronizing Record Definitions and Database Tables

1. Determine the impact of a definition change and changing the field definition.
2. Change build settings for the T1_COURSE_TBL table and alter the table.
3. Examine the log and script.
4. Examine the page definition.
FOR
5. Examine the SQL table.
6. Test the application.
INTERNAL
See PeopleTools I: Activity Guide, lesson 18, “Analyzing the Impact of Design
Changes,” Activity 56: Synchronizing Record Definitions and Database Tables.
Slide 401 ______________________________________________________________________________________________________
Student Notes USE

______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Incorporating Upgrades in the Development Strategy

Every implementation is different, depending on customer requirements, but there are
three main categories:
• The applications are unmodified
• The applications have minor modifications
• The applications are highly modified
FOR
Slide 402 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Incorporating Upgrades in the Development Strategy (continued)

An upgrade is a replacement of existing definitions with new ones. If you have not
altered definitions, upgrading the application is a relatively smooth operation. The
definition upgrades take place without much required interaction.
Slide 403 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


During the upgrade process, if internal version information of a definition indicates that it
has been modified, information about the upgraded definition and the existing modified
one is captured and placed in a comparison report, as illustrated in this diagram:
Field A Field A
Field B
Field C
Field D
FOR Field B
Field C
Field D
INTERNAL
Existing Modified
Record Definition
Comparison
Report
New Version of
Record Definition
USE
Comparison between modified and upgraded definitions
Slide 404 ______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


To comply with the upgrade:
1. Examine the comparison report to determine modifications made to the original

definition.
2. Find the documentation pertaining to your modifications.
3. Accept the upgraded definition, replacing the original.
definition. FOR
4. Using the development documentation, reapply the modifications to the upgraded
Slide 405 ______________________________________________________________________________________________________

______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


To ensure smooth transitions between releases of PeopleSoft applications, follow two
rules:
• When possible, create a new definition instead of modifying an existing one.
• When you modify an existing definition, document changes fully in the Comments
field of the definition properties.
FOR
Slide 406 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Review
• You can use cross-reference tools to examine how definitions are interrelated.
• Changing definitions can have pronounced effects on other definitions.
• Modifying field and record properties can cause the record definition to be
unsynchronized with the database table.
•
FOR
When planning application development, you should consider the impact of
modifications on future upgrades.
Slide 407 ______________________________________________________________________________________________________

______________________________________________________________________
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 19
Building Applications
Objectives
•
FOR
Discuss application design
• Create data structures
•
INTERNAL
Create user interfaces
Test applications
USE
Slide 409 ______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Building Applications Lesson 19
Designing an Application
You design the application in the planning phase as the diagram illustrates:
Test Plan
Test Design
FOR
Register
INTERNAL Components
Define
Components
Define
Fields
Define
Records
USE
Pages
Build
Tables
Data Design
Planning phase ONLY!

Slide 410 ______________________________________________________________________________________________________
Student Notes
All interested parties should be involved in this phase to avoid costly and time-
consuming mistakes. In the application design phase you produce:
• Functional specifications
• Technical specifications
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 19 Building Applications
Activity 57: Designing an Application

• Plan the data structures.
• Plan the user interfaces.
• Plan the testing.
FOR
See PeopleTools I: Activity Guide, lesson 19, “Building Applications,” Activity 57:
Designing an Application.
Slide 411 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Creating Data Structures

With technical specifications prepared, you can proceed to the data design phase as this
diagram illustrates:
Test Plan
Test Design
FOR
INTERNAL Register
Components
Define
Define
Fields
Define
USE
Components
Records
Pages Tables
ONLY!
Data design phase
Slide 412 ______________________________________________________________________________________________________
Student Notes
In this phase, you create the underlying structure of the application. The data design
phase comprises three application development steps:
• Step 2: Define fields.
• Step 3: Create record definitions.
• Step 4: Build SQL tables.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Creating Data Structures (continued)

In step 2, you identify and create new field definitions. You set such field properties as:
• Type
• Length
• Label
•
Format
Translate values FOR

Slide 413 ______________________________________________________________________________________________________

______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


In step 3, you create a record definition. You set such record properties as:
• Default values
• Field level audits
• Key structure
•
PeopleCode
Required fields
Table edits
FOR
INTERNAL
Slide 414 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


In step 4, you create the SQL tables. You need to configure settings such as:
• Build options
• Execute options
• Script options
• Logging options
FOR
Slide 415 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 58: Creating Data Structures

1. Define fields.
2. Create record definitions.
3. Build SQL tables.
FOR
Creating Data Structures.
Slide 416 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Creating User Interfaces

With the table structures in place, you can proceed to the user interface phase as this
diagram illustrates:
Test Plan
Test Design
FOR
INTERNAL
Register
Components
Define
Define
Fields
Define
USE
Components
Records
Pages Tables
ONLY!
User interface phase
Slide 417 ______________________________________________________________________________________________________
Student Notes
The user interface phase comprises three application development steps.
• Step 5: Create page definitions.
• Step 6: Define components.
• Step 7: Register components.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Creating User Interfaces (continued)

In step 5, you create page definitions. You set such page properties as:
• Record name
• Field name
• Display options
•
Label options
FOR
Related field options
Page order
•
INTERNAL
Page size
Alignment
USE
Slide 418 ______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


In step 6, you create a component definition. You set such component properties as:
• Search record
• Actions
• Toolbar options
•
Internet options
PeopleCode FOR
Slide 419 ______________________________________________________________________________________________________

______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


In step 7, you register a component. The Registration Wizard:
• Places the component on a menu.
• Sets up navigation through the portal registry.
• Sets up security rights on one permission list.
FOR
Slide 420 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 59: Creating User Interfaces

1. Create page definitions.
2. Create component definitions.
3. Register components.
FOR
Creating User Interfaces.
Slide 421 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Testing Applications
The final phase is also the last application development step as this diagram illustrates:
Test Plan
Test Design
FOR
Register
INTERNAL Components
Define
Components
Define
Fields
Define
Records
USE
Pages
Build
Tables
Data Design
Testing phase ONLY!

Slide 422 ______________________________________________________________________________________________________
Student Notes
Perform a rigorous test on the component by:
• Adding rows of data.
• Verifying defaults and prompts.
• Inserting rows of data.
• Deleting rows of data.
• Modifying rows of data.
• Testing all of the supported actions.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 60: Testing the Application

1. Test the course enrollment application.
2. Test the course database application.
Testing the Application.
FOR
Slide 423 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Review
• The application design phase produces functional and technical specifications.
• In the data design phase, you create any fields that you need, organize the fields into
record definitions, and then create the database tables.
• In the user interface phase, you develop pages, create components, grant security
• FOR
access, and implement navigation.
You should not release any application without a rigorous and thorough test phase.
Slide 424 ______________________________________________________________________________________________________

______________________________________________________________________
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 20
Searching Applications by Using

the Verity Search Engine
Objectives
FOR
• INTERNAL
Describe and perform a Verity search.
Perform a Verity search.
• Generate a Verity search collection.
•
USE
Add keywords to a search collection.
Slide 426 ______________________________________________________________________________________________________
Student Notes
ONLY!
All PeopleSoft 8 applications come with the Verity search engine. In the original release
of PeopleSoft 8, this search capability powered PeopleBooks documentation only.
In PeopleTools 8.4, the capabilities of Verity have been expanded to help users navigate
the applications.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Searching Applications by Using the Verity Search Engine Lesson 20
Describing and Performing a Verity Search

You saw on the first day of this class that users can enter text to search for content. The
search engine is supplied by Verity, one of the largest providers of search engines.
Slide 427 ______________________________________________________________________________________________________
Student Notes
Security filtering is built in and implemented behind the scenes in a Verity search. The
FOR
permission lists assigned to each content reference determine security access.
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 20 Searching Applications by Using the Verity Search Engine
Describing and Performing a Verity Search (continued)

In PeopleTools 8.4, users can access the Verity search engine to search within
applications. When a user searches for text Verity examines an index based on the
contents of the portal registry. The contents of the following fields are included in the
index:
• Label
• Long Description
•
Author
Product
FOR
•
•
INTERNAL
Node Name
Attributes (keywords)
Slide 428 ______________________________________________________________________________________________________
Student Notes USE

ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


All of these fields are available in the portal registry on the Content Ref Administration
page.
Slide 429 ______________________________________________________________________________________________________
Student Notes
Use the Content Ref Administration page to enter information that the Verity search
engine will use:
Page Name
Content Ref Administration
FOR
Navigation
INTERNAL Click the Courses link.

Click the Edit link for General Information.
USE
ONLY!

FOR
INTERNAL
USE
ONLY!
Content Ref Administration page
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


The Verity search engine does not search all the text in the portal registry each time a
user enters a search request. Rather, a search index is generated from the text and stored
on the application server. In the Verity search engine, these indexes are called collections.
PeopleSoft applications support four types of search collections:
• Registry
• Record
•
Web
File system
FOR
INTERNAL
Slide 430 ______________________________________________________________________________________________________
Student Notes
USE
PeopleSoft Enterprise Portal contains processes for building all these collections. For
standalone enterprise applications, only the registry collection is supported.
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


To perform a Verity search:
1. Enter a value in the Search field.
2. Click the search button.
3. Examine the results.
Slide 431 ______________________________________________________________________________________________________
Student Notes FOR

The search field is at the top of the menu pagelet. The search button is to the right of the
INTERNAL
search field.
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 61: Performing a Verity Search

In this activity, you will review the activity overview and execute a Verity search.
See PeopleTools I: Activity Guide, lesson 20, “Searching Applications by Using the
Verity Search Engine,” Activity 61: Performing a Verity Search.
Slide 432 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Generating a Registry Search Collection

If you add content to the portal registry by registering components, you must generate a
new registry collection before searching text on the new content reference. To generate a
search collection:
1. Select PeopleTools, Portal, Build Registry Search Index.
2. Click the Search button.
4. Click the Run button.
5. Select the process.

FOR
3. Click a Run Control ID link from the Search Results.
INTERNAL
Slide 433 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 62: Generating a Registry Search Collection

1. Generate a search collection.
2. Search for content.
See PeopleTools I: Activity Guide, lesson 20,“ Searching Applications by Using the
Verity Search Engine,” Activity 62: Generating a Registry Search Collection.
FOR
Slide 434 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Adding Keywords to a Search Collection

A search collection made up of text from labels and descriptions is helpful, but
occasionally users will want to find content based on words that are not in either field.
This is where keywords are helpful.
Slide 435 ______________________________________________________________________________________________________
Student Notes
FOR
Use the Content Ref Administration page to add keywords:
Page Name
Content Ref Administration
Navigation
INTERNAL Click the Courses link.

Click the Edit link for General Information.
USE
ONLY!
Content Ref Administration page
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Adding Keywords to a Search Collection (continued)

You can enter one or more keywords for a content reference in the Content Reference
Attributes region of the Content Ref Administration page. Follow these guidelines:
• Enter terms that are not in the Label or Description field.
• Enter terms that may be unique to the business process.
Slide 436 ______________________________________________________________________________________________________
Student Notes
FOR
Here is an example of keywords entered for a content reference in a PeopleSoft human
resources application:
INTERNAL
USE
ONLY!
Keywords entered in the Content Reference Attributes page
See Also
PeopleTools 8.44 PeopleBook: Internet Technology, “Administering Portals”
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Adding Keywords to a Search Collection (continued)

To add keywords for a content reference:
1. Enter KEYWORD in the Attribute field of the Content Reference Attributes region of
the Content Ref Administration page.
2. Enter Keyword in the Label field.
3. Enter search words or phrases separated by commas in the Attribute value field.
FOR
4. (Optional) Select the Translate check box.
INTERNAL
6. Build the registry index when you finish entering all keywords.
Slide 437 ______________________________________________________________________________________________________
Student Notes
USE
Select the Translate check box to make attribute values translatable into other languages.
It is a good practice to make keywords translatable.
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 63: Implementing a Verity Search Collection

1. Enter keywords.
2. Rebuild the search collection.
3. Search for specific content in the training application.
See PeopleTools I: Activity Guide, lesson 20, “Describing the Verity Search Engine,”
FOR
Activity 63: Implementing a Verity Search Collection.
Slide 438 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Review
• The Verity search engine is a standard feature of all PeopleSoft 8 applications; users
enter text searches that are filtered for security access rights before links to content
are returned.
• You generate a registry search collection through a process that you should run
regularly.
•
FOR
Keywords are unique, searchable values that enable you to expand the scope of a
Verity search for specific content references.
Slide 439 ______________________________________________________________________________________________________

______________________________________________________________________
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 21
Performing Data Audits
Objectives
•
FOR
Discuss advantages and disadvantages of implementing audits.
• Implement field-level audits.
• INTERNAL
Implement record-level audits.
Slide 441 ______________________________________________________________________________________________________
Student Notes USE

PeopleSoft has two approaches to auditing data: by field and by record definition. In
either case, the system writes data to tables created to contain audit data.
ONLY!
Field-level audits record when you insert, update, or delete a field value. The system
writes a row of audit data to the PSAUDIT table for each field marked for audit. You
may write multiple rows of audit data for a single transaction.
Record-level audits record any inserts, updates, or deletions for specified fields in a row
of data. PeopleSoft does not provide a table to store record-level audit data.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Performing Data Audits Lesson 21
Discussing Advantages and Disadvantages of Implementing Audits

Database administrators perform audits to track the tasks that users perform in PeopleSoft
enterprise applications. You might have hundreds or thousands of people signing in and
altering data in the database. Alterations fall into three categories:
• Adding new rows of data.
• Changing existing rows of data.
•
FOR
Deleting rows of data.
Slide 442 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 21 Performing Data Audits

(continued)
There are advantages of auditing. You can record:
• The values that changed.
• When changes were made.
• Who made the changes.
FOR
Slide 443 ______________________________________________________________________________________________________
Student Notes
INTERNAL
This is a valuable tool, especially with sensitive data. You might set up auditing on tables
that relate to company payroll, for example.
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


(continued)
There are disadvantages of auditing.
• Auditing every action on every table can significantly reduce overall performance.
• For any field or record that you audit, a separate database transaction has to take
place in addition to the user action, which is detrimental to performance.
•
FOR
Audit information is stored in separate tables, which can become quite large and
consume database server space.
Slide 444 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


(continued)
The simplest audit to set up and monitor is the field-level audit.
• All audit information from field-level audits, regardless of where the field is located,
is stored in a central PSAUDIT table.
• You can set up auditing on a field in seconds.
FOR
Slide 445 ______________________________________________________________________________________________________
Student Notes
INTERNAL
Before this class began, we configured some field level audits. Every time you made
changes in Student Personal Information, your actions wrote to an audit table.
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Implementing Field Level Audits

A field level audit is a record field property. To configure a field level audit:
1. Open the desired record.
2. Double click the field you would like to audit.
3. In the Audit section, select Field Add, Field Change, or Field Delete.
FOR
Slide 446 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Implementing Field Level Audits (continued)

All field-level audit data is stored in the PSAUDIT table. You can view this table using
Query or using SQL commands. The PSAUDIT table contains the following fields:
• AUDIT_OPRID
• AUDIT_STAMP
• AUDIT_ACTN
•
RECNAME
FIELDNAME
FOR
•
• INTERNAL
OLDVALUE
NEWVALUE
• KEY1, KEY2, …
USE
Slide 447 ______________________________________________________________________________________________________
Student Notes
•
ONLY!
This section discusses how to view data in the PSAUDIT table:
View the contents of PSAUDIT using your database query tool and a SELECT
statement:
SELECT * FROM PSAUDIT
• Limit your query to a specific record definition by specifying it in a WHERE clause:

WHERE RECNAME = ‘PSU_STUDENT_TBL’
• Modify the WHERE clause to limit your query to a specific field on a specific record
definition:
WHERE RECNAME = ‘PSU_STUDENT_TBL’
AND FIELDNAME = ‘STUDENT_NAME’
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 64: Performing a Field-Level Audit

• Observe field-level settings
• View the contents of PSAUDIT.
See PeopleTools I: Activity Guide, lesson 21, “Performing Data Audits,” Activity 64:
Performing a Field-Level Audit.
FOR
Slide 448 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Implementing Record Level Audits

You can capture similar audit information at the record level. The initial setup is a little
more elaborate, but an audit table in your database is dedicated to auditing fields for a
specific record. To set up a record level audit:
1. Clone the record you want to audit.
2. Save the record as AUDIT_<original record name>.
FOR
3. Insert the audit fields as the first three fields.
4. Delete any fields that you do not want to track.
5. Remove all key structure.
INTERNAL
6. Build the table.
7. Link the base record to the audit record and select the desired audit options.
USE
Slide 449 ______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Implementing Record Level Audits (continued)

To clone and save the record:
1. Open the record to audit.
2. Select File, Save As.
3. Enter AUDIT_<original record name> in the Save As field.
Slide 450 ______________________________________________________________________________________________________
Student Notes FOR

The field name is limited to 15 characters.
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Insert these three fields, in this order, as the first three fields in the record definition:
• AUDIT_OPRID.
• AUDIT_STAMP.
• AUDIT_ACTN.
FOR
Slide 451 ______________________________________________________________________________________________________
Student Notes
INTERNAL
Note. For AUDIT_STAMP, select the Auto-Update check box in the Record Field
Properties dialog box otherwise the audit record doesn’t receive a date and time stamp.
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Delete fields that you do not want to audit:
• You should audit all fields that are keys in the original record to help determine the
unique row that included the action.
• To audit all fields in the record, skip this step.
• You cannot audit Long Character or Image fields.
FOR
Slide 452 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


Audit tables do not include keys or indexes.
1. Clear all key attributes.
2. Clear all duplicate order key attributes.
3. Clear all search key attributes.
Slide 453 ______________________________________________________________________________________________________
Student Notes FOR

INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


The next step is to build the table.
Slide 454 ______________________________________________________________________________________________________
Student Notes
This is the most often forgotten step. Remember to build the table.
FOR
______________________________________________________________________
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


To link the base record to the audit record:
1. Open the record definition that you are auditing.
2. Select File, Definition Properties.
4. Select the correct audit record definition from the Record Name drop-down list box.
FOR
5. Select the desired audit actions.
Slide 455 ______________________________________________________________________________________________________
Student Notes
INTERNAL
With record-level audits, you can track any combination of four actions.
•
Add
Change
USE
• Selective
• Delete ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


The audit table records:
• Only the old values for non-key fields.
• Both the new and old values if you change a key value.
Slide 456 ______________________________________________________________________________________________________
Student Notes
FOR
See PeopleTools 8.44 PeopleBook: PeopleSoft Application Designer, “Creating Record
Definitions”
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 65: Implementing Record Level Audits

1. Clone and save the record.
2. Insert the audit fields.
3. Delete unnecessary fields.
4. Remove all key structure, default values, and set auto update.
5. Build the table. FOR

6. Link the base record to the audit record and select the desired audit options.
INTERNAL
7. Test the auditing process.
See PeopleTools I: Activity Guide, lesson 21, “Performing Data Audits,” Activity 65:
Implementing Record Level Audits.
USE
Slide 457 ______________________________________________________________________________________________________
Student Notes
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Review
• You should use data audits that track user actions on selected fields or records
sparingly because they add overhead to tracked entries and increase database
resource requirements.
• To implement field-level auditing, you select the actions to track in the record
definition’s record field properties.
•
FOR
To implement record-level auditing, you build a special audit record definition and
then link it to the record you want to audit.
Slide 458 ______________________________________________________________________________________________________

______________________________________________________________________
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 22
Importing and Exporting Projects
Objectives
•
FOR
Describe how projects transport definitions between databases.
• Export projects.
• INTERNAL
Import projects and build their tables.
Slide 460 ______________________________________________________________________________________________________
Student Notes USE

Projects allow quick access to the definitions that you are using. Projects are also
portable.
ONLY!
You can export the definitions that are in a project to an extensible markup language
(XML) file and then import them into another database. This is an invaluable tool for
developers who typically work in a development environment apart from production
databases.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Importing and Exporting Projects Lesson 22
Describing How Projects Transport Definitions Between Databases

A project is a collection of definitions. Use projects to:
• Organize definitions into related groups as you develop applications.
• Move definitions from one application database to another.
Slide 461 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 22 Importing and Exporting Projects

(continued)
Copying a project to a database is the most direct method. If you have connectivity to the
database to which you want to transfer the project, all definitions are loaded into the
target database’s tables, as shown in this diagram:
System Catalog
PeopleTools
FOR
Project Project
System Catalog
PeopleTools
Source
INTERNAL
Application Data
Development
Workstation
Application Data
Target
Database Database
USE
Transferring project data from one database to another
Slide 462 ______________________________________________________________________________________________________
Student Notes ONLY!

______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


(continued)
Copying to a file creates a series of XML files in a folder. After the project is in file form,
you can import the project from the target side, as shown in this diagram:
System Catalog
PeopleTools
Application Data
FOR
Project Project
INTERNAL
Development
Workstation
Source Project
Database Files
PeopleTools
USE
System Catalog
Project Project
Target
Database
ONLY!
Application Data
Development
Workstation
Copying to file
Slide 463 ______________________________________________________________________________________________________
Student Notes
Projects do not hold application data. If you have record definitions in your project, you
must build them in the new database to create the application data tables.
You can migrate application data with Data Mover script files.
This topic is covered in detail in the instructor-led course Data Administration Tools.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


(continued)
PeopleSoft distributes project files by means of download. Three levels of imports are
available:
• Fixes.
• Updates.
• Upgrades.
FOR
Slide 464 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Exporting Projects
Exporting a project is a simple procedure. To export a project to a file:
1. Open the project in Application Designer.
2. Select Tools, Copy Project, To File.
3. Select the definitions to copy.
4. Enter the output directory.
FOR
5. Click the Copy button.
Slide 465 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Exporting Projects (continued)

The copy process creates two files:
• An XML file.
• An .ini file.
Slide 466 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 66: Exporting Projects

1. Export a project.
2. Examine the project files.
See PeopleTools I: Activity Guide, lesson 22, “Importing and Exporting Projects,”
Activity 66: Exporting Projects
FOR
Slide 467 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Importing Projects
Importing a project is a nearly identical procedure to exporting a project. To import a
project from a file:
1. From PeopleSoft Application Designer, select Tools, Copy Project, From File.
2. Browse to select the project folder.
3. Select the definitions you want to copy.
4. Click Open.
FOR
5. Select Tools, Validate Project.
INTERNAL
Slide 468 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Importing Projects (continued)

When you import a project with record definitions, you have to ensure that the SQL
tables they represent exist. You might have to:
• Build tables if they do not exist.
• Check changes to the definition to determine whether you should alter the underlying
tables.
FOR
Slide 469 ______________________________________________________________________________________________________
Student Notes
When you select Build, there is an option to build an entire project. This applies the build
INTERNAL
options you choose to all the record definitions in the current project. You can select an
option on the Build tab to skip existing records.
______________________________________________________________________
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Activity 67: Importing Projects

In this activity, you will review the activity overview and import the T1_IMPORT
project.
See PeopleTools I: Activity Guide, lesson 22 “Importing and Exporting Projects,”

Activity 67: Importing Projects
Slide 470 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Review
• Projects are an excellent way to organize definitions during development or to

transport definitions between databases.
• When you export the current project to a file, you have an .ini file and an XML file
that contains all of the definition data.
•
FOR
When you import a project, check the project integrity and consider whether the
underlying tables have to be built or altered.
Slide 471 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 23
Final Course Activity
Objective
FOR
By the end of this lesson, you will be able to implement the eight steps that create an
application to evaluate training courses.
Slide 473 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Final Course Activity Lesson 23
Activity 68: Creating a Course Evaluation Application

1. Design the application.
2. Create the data structures.
3. Create the user interface.
4. Test the application.
FOR
See PeopleTools I: Activity Guide, lesson 23 “Final Course Activity,” Activity 68:
Creating a Course Evaluation Application
INTERNAL
Slide 474 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 24
Course Review
Completed Objectives
•
FOR
In this course, you learned how to:
Navigate a PeopleSoft application.
• Describe the elements of the PeopleSoft Internet Architecture (PIA).
•
INTERNAL
Describe PeopleSoft data organization and validation.
Implement the eight step process of application development.
•
USE
Describe additional application development considerations.
Perform searches and audits of application data.
•
ONLY!
Organize definitions into projects.
Slide 476 ______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Course Review Lesson 24
Navigating a PeopleSoft Application

One method you use to navigate a PeopleSoft application is the menu pagelet. To find
information you:
• Select a folder
• Select a content reference
• Enter values in the search fields
FOR
Slide 477 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Lesson 24 Course Review
Navigating a PeopleSoft Application (continued)

Another method you use to navigate a PeopleSoft application is the search engine. To
find information you:
• Enter a value in the search field
• Click the Search button
• Select the appropriate content reference
FOR
Slide 478 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Describing the Elements of the PeopleSoft Internet Architecture

PeopleSoft Internet Architecture consists of:
• A database server
• An application server
• A web server
FOR
A browser or other user input device
Slide 479 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Describing the Elements of the PeopleSoft Internet Architecture

(continued)
This illustration shows communication protocols between the different elements of
PeopleSoft Internet Architecture:
Application Database
Browser Web Server
Server Server
HTML
Web
Services
FOR PeopleSoft
Services
SQL
System
Catalog
People
Tools
HTML 4
Compatible
Browser INTERNAL
Java
Services
Jolt Tuxedo/Jolt
Application
Data
PeopleSoft Internet Architecture USE

Slide 480 ______________________________________________________________________________________________________
Student Notes ONLY!

______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Describing PeopleSoft Data Organization and Validation

A PeopleSoft database has three types of tables:
System
Catalog
People
Tools
Application
Data FOR
INTERNAL
Types of tables
Slide 481 ______________________________________________________________________________________________________
Student Notes
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Describing PeopleSoft Data Organization and Validation (continued)

A PeopleSoft application uses application-level validations such as:
• Prompt table edits
• Translate table edits
• Yes/No table edits
FOR
Slide 482 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Implement the Eight Step Process of Application Development

This diagram illustrates the eight step process:
Test Plan
Test Design
FOR
Register
INTERNAL
Define
Components Fields
Define
Components Define
Records
USE
Pages
Build
Tables
Data Design
ONLY!
Eight steps of application development
Slide 483 ______________________________________________________________________________________________________
Student Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Implement the Eight Step Process of Application Development (continued)

When you plan, you construct the:
• Functional specifications
• Technical specifications
Slide 484 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


In the data design phase you:
• Create the field definitions
• Create the record definitions
• Build the SQL table
FOR
Slide 485 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


In the user interface phase you:
• Create the page definitions
• Create the component definitions
• Register the component
FOR
Slide 486 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________


The testing phase includes:
• Adding high-level keys at level 0.
• Inserting, updating, and deleting data at level 1.
• Viewing and correcting historical data.
FOR
Verifying prompts and defaults.
Slide 487 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Describing Additional Application Development Considerations

In addition to using the eight steps of application development, you should finish the
application by:
• Changing the search page title
• Creating menus for organizational purposes.
Slide 488 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Performing Searches and Audits of Application Data

Your PeopleSoft application uses a Verity search engine to locate data:
• You can customize your searches by adding keywords to content references and
folders.
• You must generate a new registry collection to use the new keywords.
Slide 489 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Performing Searches and Audits of Application Data

You can monitor your data by:
• Creating field level audits.
• Creating record-level audits.
Slide 490 ______________________________________________________________________________________________________
Student Notes
FOR
______________________________________________________________________
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Organizing Definitions into Projects

You can create project to:
• Transport definitions between databases.
• Upgrade definitions.
• Export definitions to a file.
FOR
Slide 491 ______________________________________________________________________________________________________
Student Notes
INTERNAL
______________________________________________________________________
______________________________________________________________________
USE
______________________________________________________________________
______________________________________________________________________
ONLY!
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________

Appendix A
Curriculum Map
FOR
INTERNAL
USE
ONLY!

PeopleTools Curriculum Map Appendix A
Curriculum Map
Development
400 410 420

KEY
PeopleTools I PeopleTools II PeopleCode
5 days 5 days 5 days
Classroom Classroom Classroom
Upgrade Course
405
411
PeopleTools Overview
Application Engine
2 days
4 days
Classroom
Classroom
FOR
1533
Integrating Processes 426
and Reports Workflow
1 day 4 days
Live WebCast Classroom
1022
Integration Tools
4 days
INTERNAL
Classroom
Administration
415
Process Scheduler
Administration and Report
Distribution
2 days
USE
Classroom
478
Data Management Tools
and Upgrade
5 days
Classroom
ONLY!
466
PeopleSoft Security
3 days
Classroom
471
PeopleSoft Server
Administration
4 days
Classroom
Enterprise Portal
1011
Enterprise Portal
Administration (8.4)
3 days
Classroom 1011
Enterprise Portal
OR Administration (8.8)
5 days
Classroom
1377
Concepts in Enterprise
Portal Development (8.4)
1 day
Live WebCast
Reporting 430
SQR
5 days
Classroom
435
PS/nVision Using Queries
4 days
Classroom
455
Query/Crystal Power
Combo
4 days
Classroom with
OnDemand
1152
Query Reporting
2 days
Classroom with
OnDemand
PeopleTools Curriculum Map

People Soft Tools 1

Uploaded by

Document Information

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

People Soft Tools 1

Uploaded by

Copyright:

Available Formats

PeopleTools I

Copyright 2004 PeopleSoft, Inc.

All rights reserved.

Preface PeopleTools I.....................................................................................................................ix

Lesson 1 Course Overview ...............................................................................................................1

Lesson 2 Technology Overview........................................................................................................7

Lesson 4 Explaining PeopleSoft Architecture ..............................................................................53

Lesson 5 Organizing Data ..............................................................................................................75

PeopleSoft Proprietary and Confidential iii

Activity 9: Using Effective Dating..........................................................................103

Lesson 7 Developing Applications by Using the Eight Steps.....................................................113

Designing the Application.............................................................................................127

Defining Fields ...............................................................................................................141

Lesson 10 Creating Record Definitions.........................................................................................163

iv PeopleSoft Proprietary and Confidential

Building SQL Tables .....................................................................................................197

Lesson 12 Creating Page Definitions .............................................................................................215

Lesson 13 Defining Components....................................................................................................279

Lesson 14 Registering Components...............................................................................................307

PeopleSoft Proprietary and Confidential v

Activity 44: Registering the T1_COURSE_MATL Component ..............................338

Lesson 15 Testing an Application ..................................................................................................341

Lesson 16 Editing the Registry Structure .....................................................................................359

Activity 48: FOR

Activity 50: INTERNAL

Creating Menu Definitions ...........................................................................................385

Lesson 18 Analyzing the Impact of Design Changes....................................................................401

Lesson 19 Building Applications....................................................................................................419

vi PeopleSoft Proprietary and Confidential

Searching Applications by Using the Verity Search Engine......................................435

Lesson 21 Performing Data Audits................................................................................................451

Course Review ...............................................................................................................483

Appendix A Curriculum Map ...........................................................................................................499

PeopleSoft Proprietary and Confidential vii

viii PeopleSoft Proprietary and Confidential

Typographical Conventions and Visual Cues

Typographical Conventions INTERNAL

Italics ONLY! literally in the function call.

PeopleSoft Proprietary and Confidential ix

Note. Example of a note.

Example of cross-reference to a PeopleBook

x PeopleSoft Proprietary and Confidential

• Navigate a PeopleSoft application.

Describe PeopleSoft data organization and validation.

Describe additional application development considerations.

Organize definitions into projects.

• Demonstrate competence in PeopleSoft application development methodology.

PeopleSoft Proprietary and Confidential 1

Agenda: Day One

• Navigating PeopleSoft Applications.

• Describing the PeopleSoft Internet Architecture.

Student Notes INTERNAL

2 PeopleSoft Proprietary and Confidential

Agenda: Day Two

• Designing the Application.

• Creating Field Definitions.

• Creating Record Definitions.

PeopleSoft Proprietary and Confidential 3

Agenda: Day Three

• Creating Page Definitions.

• Creating Component Definitions.

• Registering the Component.

4 PeopleSoft Proprietary and Confidential

Agenda: Day Four