Your SlideShare is downloading. ×
Peoplesoft Basic App designer
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Peoplesoft Basic App designer

7,432
views

Published on


1 Comment
2 Likes
Statistics
Notes
  • http://www.dbmanagement.info/Tutorials/Peoplesoft.htm
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
7,432
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
233
Comments
1
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. IntroductionMbtechnosolutions- App Designer Fundamental - I By. Md. Sayeed Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 2. Lesson Objectives After completing this lesson, you should be able to do the following: • List the features of Application Designer • Discuss the theoretical and physical aspects of a relational database and App Designer Definitions • Describe the integrated Platform for various PeopleSoft tasks • Understand the goals of the courseI-2 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 3. Goals of the Course After completing this course, you should be able to do the following: • Identify the major structural components of App Designer • Understand field, Record, Page, Component and Menu • Registration wizard and its features • Creating ‘Hello World’ Project by using 8 steps • Accessibility Pages in PIAI-3 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 4. App Designer’s(Integrated Tool) Important definitions/technologies People code Component Application Component Package Interface App Engine File LayoutI-5 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 5. App Designer Definitions (ALL) 1. Activity 7. Business 15. Image 2. Analytic Model Interlink 16. Menu 3. Analytic Type 8. Business 17. Message 4. App Engine Process 18. Mobile Page Program 9. Component 19. Page 5. Application 10. Component 20. Project Package Interface 21. Record 6. Approval Rule 11. Field 22. SQL Set 12. File Layout 23. Style sheet 13. File Reference 14. HTMLI-6 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 6. FieldI-7 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 7. FieldFields are the lowest level units in PeopleSoft. Fields are Individual objects defined in PeopleSoft . One or moreFields grouped to form a record definition. A field can be shared across all record definitions Types of Field Field Type Field Length Field Labels Field Formats Field Properties General Translate values I-8 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 8. I-9 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 9. Field Type Character (Char): Used for codes in PeopleSoft Long Character (Long): Used to store comments in PeopleSoft Number(Nbr) :to hold positive integers and decimal numbers Signed Number (Sign): holds negative integers and decimals Date (Date) :hold dates in (MM/DD/YYYY) format Time(Time) : holds time in (HH:MI:SS.99999) format Datetime (DtTm) :holds both date and time Image (Img): to store pictures in PeopleSoft (Jpeg, Bitmap format) Image Reference(Iref): to change an image dynamically at runtime using PeopleCode. Attachment:Maps to a BLOB database type to hold the contents of a file attachment.I-10 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 10. Field PropertiesI-11 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 11. Field Properties General Properties Field Definition: We can specify purpose of this field Owner ID: Application Module like HR, Base Benefit Last Update by: Auto insertion (cannot be changed) Date/Time: System takes current date and time By User: System take Logged-in username as updated by user Translate Values The Translate Values tab is available only for character fields.The Translate table is a prompt table, which is similar to an all-purpose datadictionary, to store values for fields that don’t need individual prompt tables of theirown. A Universal table(PSXLATITEM) can be used across all PeopleSoftEnvironment to populate Pre-defined drop down values I-12 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 12. Translate Value windowI-13 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 13. Translate Value FieldsField Value: Use to enter the translate value for the field. The system automaticallysorts values in ascending order as you enter them.Effective date: Enter the date on which you want this value to take effect.The default value is today’s date.Long Name: Enter up to 30 charactersShort Name : Enter up to 10 characters, and if this field left blank, Peoplesoft willtake first 10 Character from Long Name (Automatically) I-14 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 14. Querying PSXLATITEM TABLEI-15 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 15. RecordA Record is a collection of Fields. A Record definition can be an SQLtable, an SQL View, a Sub record.. Record Types SQL SQL View Dynamic View Derived/Work Sub Record Query View Temporary Table Record Properties General Use Record Field Properties Use Edit I-16 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 16. Purpose of record Type1 An SQL: (Structured Query Language table) A physical SQL table in the database.2 An View: (Structured Query Language view) Select to define a record definition that corresponds to a SQL view, which is not a physical SQL table in the database3 Dynamic View: Select to define a record definition that can be used like a view in pages and PeopleCode, but is not actually stored as a SQL view. Dynamic views can provide superior performance in some situations, such as search records I-17 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 17. Purpose of record Type…24 Derived/Work: Select to define the record definition as a temporary workspace to use during online page processing.5 Sub Record: subrecord—a group of fieldsthat are commonly used in multiple record definitions. We can change a group of fields in one place, as opposed to changing each record definition in every record6 Query View: To define the record definition as a view that is constructed using the PeopleSoft Query tool. Before we create the view, PeopleSoft Application Designer prompts you to save the definition. I-18 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 18. Purpose of record Type…37 Temporary Table: To define the record definition as a temporary table. Temporary tables are used for running PeopleSoft Application Engine batch processes. Non Standard SQL: To override the standard convention of prefixing PS_ to the record name. I-19 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 19. PeopleTools table to store Record definition AttributesPSRECDEFN: Record definitions are stored in a this table. This table stores allattributes of a Record definition. Like Record type, Audit Record name, Parentrecord name, index count, field count. SQL table and SQL View are data basedobjects and stored with PS_ prefix in databasePSREFIELD: This table stores the fields that the record definition contains. Eachfield with its own edit properties. It may translate value edit, prompt table edit. OrYes or no editPSPROGCOUNT: contains the Number of PeopleCode events for the record field. I-20 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 20. Record…3PSINDEXDEFN: This table contains a row for each index for the record definition.And populated only if the record definition is an SQL table or an SQL viewPSKEYDEFN:This table contains all record field that composethe index are stored with key sequence I-21 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 21. Naming Convention for Records_TBL: Identifies an edit or prompt table that contains data that is used for validation,_VW: Identifies a record definition that is physically implemented by defining a SQL view. _DVW: Identifies a dynamic view. _WRK: Identifies derived work records._SBR: Identifies subrecords._QVW Identifies a query view. I-22 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 22. Naming Convention for Records _WL: Identifies the record as a worklist record definition _R: Identifies work record definitions for Structured Query Report reports. AUDIT_: Identifies record definitions that store audit information for other record definitions in the database WEBLIB_: Identifies record definitions that store internet scripts. Internet scripts are generally located in FieldFormula PeopleCode events.FUNCLIB_: Identifies record definitions that contain written PeopleCode functions, as opposed to built-in functions.I-23 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 23. Naming Convention for Record DERIVED_ Identifies shared record definitions (across an application module or group)that have fields for PeopleCode events.I-24 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 24. Page • Page serves as user interface to the Application • Page is collection of record fields with certain purpose • Page vary from simple page, pages with scroll bar, subpages and secondary pagesI-25 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 25. Component  A component compromises either a single page or a set of pages that are meant to be served  purpose of functionality and processed as one. We can manage through Component Definition  Grouping of pages  Search Record (to retrieve data)  Tab Navigations  Links at the bottom of a page  Toolbar at the bottom of a pageI-26 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 26. Search(component’s feature)I-27 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 27. ToolbarI-28 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 28. Catalog table for componentI-29 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 29. PSPNLGROUPI-30 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 30. Menu Menus work as gateway to the application. Menus store Components (collection of pages) Menu items are hold a component and provide access to an application panel. End user has to be given access to a menu item to access it. Standard Pop-Ups Used to create Application Panel Used to create context-menu to page fields(user can access by right click) Pre-Define Menu item Useful to bring help when the File , Edit, View, Go, Language and Help user needs it. We can specify menu group, sequence of that Menu I-31 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 31. PSMENUDEFN This catelog table stores the menu attributes. It containsI-32 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 32. PSMENUITEMThis catalog table stores the individual items in standard or pop-ups menu. It containsI-33 Copyright © 2013, mbtechnosolutions. All rights reserved.
  • 33. Registration ProcessI-34 Copyright © 2013, mbtechnosolutions. All rights reserved.