Objects

• 1: Projects
• 2: Project Import
• 3: Fields
• 4: Records
• 5: SQL Objects
• 6: Pages
• 7: Components
• 8: Component Interfaces
• 9: Menus
• 10: Content References
• 11: Message Catalogs
• 12: Application Packages
• 13: URL Definitions
• 14: HTML Definitions
• 15: Style Sheets
• 16: Queries
• 17: Query Trees
• 18: Nodes
• 19: Services
• 20: Service Operations
• 21: Messages
• 22: Queues
• 23: App Engines
• 24: Process Definitions
• 25: Process Jobs
• 26: Recurrences
• 27: Server Definitions

Objects

psLens lets you search and explore the core PeopleSoft metadata objects that define how the application is built. Every object type has the same two-step flow: a search page where you find what you’re looking for, and a detail page that consolidates everything psLens knows about that object across the database.

Useful when you need to look up an object without firing up App Designer.

Search and Navigation

How Search Works

All metadata pages share the same search behavior:

1. Type at least a partial name in the search box.
2. Results appear automatically after a short pause (no need to press Enter).
3. Results are paginated — scroll down to load more.
4. Click any result card to open the detail view.

Search auto-matches as starts with — typing PS finds PSCLASSDEFN, PSMENUITEM, and so on. For more control, include % yourself: %SECURITY (ends with), %PERS% (contains), or just % to list every row. The per-object pages below note when a specific search box uses different behavior (for example, SQL Object search runs against the SQL text body, not just the name).

Cross-Object Navigation

The detail page for each object type follows a consistent layout: main properties on the left, and a right-side Related Data sidebar with toggles that fetch additional information on demand. Toggling a panel ON fires a request, and the result loads inline. Each toggle runs a single query against the underlying tables (PSPRSMDEFN ancestors, PSPCMPROG references, etc.) and renders the result in place. The pattern is the same across every object type.

Where it makes sense, every linked reference (a record name, a field name, a component, a project) is clickable and navigates to that object’s own detail page, so you can chase a question across the application metadata in a few clicks.

Exporting Object Definitions

Every PeopleSoft object detail page in psLens supports exporting its full definition as a Markdown file. Look for the Export as Markdown card on the detail page. This is useful for documentation, code reviews, or sharing object details outside of psLens — and the structured Markdown format is ideal as input to AI tools like ChatGPT or Claude.

Deep Links to PIA

Every detail page surfaces a link out to the corresponding App Designer or PIA navigation in PeopleSoft, so you can jump from a psLens view straight into the live environment when you need to make a change.

1 - Projects

What It Is

Projects are PeopleSoft’s primary mechanism for grouping metadata objects together for migration between environments (e.g., from Development to Testing to Production). Every project definition is stored in PSPROJECTDEFN, and the items contained within a project are registered in PSPROJECTITEM.

psLens allows you to search and inspect project definitions directly, showing you the exact list of objects included in a project and letting you compare project items across different database environments.

Search Page

URL: /projects?db={database}

The Project Search page lets you locate projects by name (using a prefix match).

• Basic Search: Type a partial name (e.g., HR or PT) to search. Search matches as starts with. You can use the % wildcard for more complex queries: %UPGRADE% finds any project containing “UPGRADE”, or % alone lists all projects.
• Advanced Filters:
  • Operator ID: Filter projects last updated by a specific operator (user).
  • Customized Only: Filter to show only projects marked as customized.
  • Date Range: Filter projects based on their last updated date.

Detail Page

URL: /projects/{PROJECTNAME}?db={database}

The Project Detail page shows:

• Project Properties: Shows metadata about the project itself, such as the description, version, object owner, release, release label, update flags, and the user who last updated it.

• Project Items: Displays a paginated list of all objects contained within the project, grouped and sorted by object type (e.g., Records, Fields, Pages, Components, PeopleCode).

  

  Migration & Health Flags: psLens automatically flags non-standard project items in red (as shown above). This highlights things that can cause issues with migrations, such as upgrade flags and actions (e.g., Delete actions or items with Take set to No). This gives you a quick check on the state of your project before migrating.

• Compare to Database: If you have multiple databases configured in psLens, you can select another database from the card on the page to run a project comparison.

• Export as Markdown: Export the entire project definition and its items list to a markdown file, which is ideal for change logs, migration documentation, or code reviews.

2 - Project Import

What It Is

Project Import lets you upload an XML export file of a PeopleSoft project (the .xml files exported from App Designer via Tools -> Copy Project -> To File).

This lets you inspect the contents of a project file (including embedded PeopleCode, SQL, and HTML definitions) and compare it against any of the configured databases before actually migrating or importing the project into the environment.

Uploading a Project XML

URL: /project-import

To import a project:

1. Go to the Project Import page.
2. Click the file upload box or drag-and-drop your PeopleSoft project XML file (up to 25MB).
3. The server will parse the XML and add the project to your local imports history list.

Project XML View

Once imported, you are presented with the Project XML View:

• Metadata Summary: Shows the source database where the project was exported, export date, export Operator ID, and file stats.
• Flat Items List: A single flat table listing every object in the project, categorized by type (Record, Field, Component, etc.).
• Source Code View: Items that contain code (PeopleCode, SQL, or HTML) are marked with an icon. Clicking on these items will expand them inline to show the source code directly in your browser.

Database Comparison

You can compare the imported XML project against any of your active databases:

1. Select the target database from the dropdown in the comparison card.
2. Click Compare.
3. psLens runs a comparison check for each object:
   • PeopleCode: Performed via content hashing (ignoring line endings and trailing whitespace) to determine if the code is identical or different, since timestamps are often unreliable across migrations.
   • Other Objects: Performed via the LASTUPDDTTM timestamp on the target database table.

Compare Statuses

• Same: The object in the XML file is identical to the one in the target database.
• Different: The code contents differ between the XML and the database.
• DB Newer: The object in the database has a newer timestamp than the one in the XML.
• DB Older: The object in the database has an older timestamp than the one in the XML.
• Not in DB: The object does not exist in the target database.
• No DB Lookup: The object type is not supported for automatic database comparison.

3 - Fields

What It Is

Fields are the atomic units of a PeopleSoft application. Every column on every page and every row in every table is built on top of a field definition. psLens reads field definitions from PSDBFIELD (and field labels from PSDBFLDLABL) and stitches them together with the rest of the metadata so you can see, in one place, everywhere a given field is used.

Search Page

URL: /fields?db={database}

Type a partial field name to find matching definitions. Search auto-matches as starts with — EMPLID finds EMPLID, EMPLID_TBL, EMPLID_PNL, etc. Include % yourself for more control: %NAME (ends with), %DESCR% (contains), or just % to list every row. Each result card shows the field type and length, the long-name description, and the last-updated timestamp so you can spot recently modified objects at a glance. The Advanced Filters panel lets you narrow by field type, last-updated date, or owner. Recently viewed fields are surfaced just above the results.

Detail Page

URL: /fields/{FIELDNAME}?db={database}

The main pane shows the Field Properties card (type, length, format, description, object owner, last-updated metadata) and a Field Labels card with every long/short name pair defined in PSDBFLDLABL, including which one is the default label. The Export button in the top right downloads the full definition as Markdown. The Related Data sidebar holds six toggles that fetch additional context on demand.

Related Data Panels

Toggle any panel on to load it inline beneath the main content. Each panel returns the count of objects found and a sortable list with deep-links into the corresponding psLens detail pages, so you can chase a field reference into the record, page, or PeopleCode program that uses it without losing your place.

Records

Lists every record where the field appears, with record type, the position number within the record, key-field indicator, and whether the field is configured with an Edit Table prompt. Sourced from PSRECFIELD / PSRECFIELDDB.

Included in Projects

Shows every App Designer project (PSPROJECTITEM) that contains this field as a project item. Useful for tracing which customization or release introduced or modified the field.

PeopleCode References

Lists PeopleCode programs that mention the field: record PeopleCode, component PeopleCode, application package methods, and more. Each result links to the parent object’s detail page so you can drill into the program.

Pages

Lists pages (PSPNLFIELD) where a control on the page is bound to this field, with the record context. Useful for impact analysis when changing a field’s type or length.

Component Interfaces

Lists Component Interfaces that expose this field as a CI property. The integration surface area for the field. Sourced from PSBCITEM.

Queries

Lists PeopleSoft Queries (PSQRYFIELD) that reference this field in a SELECT, WHERE, or ORDER BY. Useful for security and audit work: “who has reports built on this column?”

What This Consolidates

In App Designer, assembling this same picture requires:

• Open the field in App Designer for properties and labels
• Right-click → Find Object References for record usage
• Run a separate Find In search across all PeopleCode for code references
• Manually run SQL against PSPNLFIELD and PSBCITEM to find page and CI usage
• Open Query Manager and run cross-database searches for query references
• Open each containing App Designer project one at a time to confirm migration history

psLens collapses all of that into a single page with one toggle per question.

4 - Records

What It Is

Records are PeopleSoft’s table/view definitions — every database table, SQL view, derived/work record, and dynamic view is registered in PSRECDEFN. psLens reads the record definition plus its field list from PSRECFIELD and stitches it together with everywhere the record is referenced in pages, components, PeopleCode, queries, projects, and trees. The Records page has 11 related-data panels (more than any other object type) covering pages, components, PeopleCode, queries, trees, prompt-table back-references, AE statements, project membership, and a live row sample.

Search Page

URL: /records?db={database}

Search auto-matches as starts with — typing JOB finds JOB, JOB_DATA, JOBCODE, etc. For more control, include % yourself: %DATA (ends with), %PERS% (contains), or just % to list every row. Each card shows record type, field count, the descriptive long name, and last-updated metadata. The Advanced Filters panel lets you filter by record type (Table, View, Derived/Work, Subrecord, Dynamic View, Query View, Temp Table), object owner, and last-updated date.

Detail Page

URL: /records/{RECNAME}?db={database}

The main pane shows Record Properties (type, owner, audit options, system table flag, description, audit timestamps) and a full Record Fields table with each field’s type, length, key indicators, default value, and Edit Table prompt — every detail you’d otherwise open App Designer to confirm. The Export button downloads the full record definition as Markdown. The Related Data sidebar holds 11 toggles — the broadest set of any object type — covering every place this record is referenced.

Related Data Panels

Pages Using This Record

Lists pages with controls bound to this record (PSPNLFIELD join on RECNAME). Useful for impact analysis when changing the record schema.

Components Using This Record

Lists every component containing a page bound to this record — gives you the user-facing transactions affected by the record.

PeopleCode Events

Lists record-level PeopleCode events (FieldChange, RowInit, SaveEdit, etc.) attached to fields of this record. Sourced from PSPCMPROG.

Included in Projects

Lists App Designer projects (PSPROJECTITEM) that include this record — useful for migration history and change tracking.

Used in App Engines

Lists Application Engine programs whose SQL or PeopleCode steps reference this record. Sourced from PSAESTMTDEFN text scans.

Component Interfaces Using This Record

Lists Component Interfaces whose underlying component contains a page bound to this record — the integration surface area.

Record Data

Pulls a live sample of rows from the record using the psoftQL API — first ~10 rows with every column. Lets you see what the data actually looks like without opening App Designer’s Run-In-Query or a separate SQL client.

PeopleCode References

Broader than “Events” — finds any PeopleCode anywhere in the database that mentions this record by name (component, page, app package, app engine, message, signon, FieldFormula, etc.).

Queries Using This Record

Lists PeopleSoft Queries (PSQRYRECORD) that include this record in a FROM clause. Critical for audit work — “who is reporting from this table?”

Query Trees Using This Record

Lists Query Tree nodes (PSTREENODE) where this record appears — determines which query authors can build queries against it.

Used as Prompt Table

Lists fields on other records that point to this record as their Edit Table / Prompt Table — shows the lookup relationships that hang off this record.

What This Consolidates

A complete impact assessment for a record change in App Designer requires:

• Open the record in App Designer for properties, fields, and PeopleCode events
• Right-click → Find Object References to find pages using it
• Walk every found page to find its component
• Run a separate Find In across PeopleCode for code references
• Query PSAESTMTDEFN, PSQRYRECORD, PSTREENODE manually to find AE, query, and tree usage
• Run SQL against PSDBFIELD joined to PSRECFIELD to find prompt-table usages
• Open every owning project to see migration history
• Open the database with SQL Developer / Toad to sample actual data

psLens shows all of that on one page, including a live row sample from the record.

5 - SQL Objects

What It Is

SQL Objects are the PeopleSoft application’s standalone SQL artifacts — view definitions and other named SQL fragments stored in PSSQLDEFN / PSSQLTEXTDEFN. Unlike a record’s automatically-generated DDL, these are SQL bodies the developer hand-wrote and PeopleSoft keeps versioned with the rest of the metadata. psLens pulls the source SQL plus the related record (when the SQL object is a view tied to a record definition) so you don’t switch into App Designer to read the SQL.

Search Page

URL: /sqlobjects?db={database}

Search auto-matches as starts with. Typing PT finds every SQL object whose ID begins with PT. Include % yourself for ends-with (%VW) or contains (%AUDIT%) patterns, or use % alone to list every row. Each result shows the object name, type, and last-updated info, useful when you’re tracing where a view body is defined or hunting for a delivered SQL fragment.

Detail Page

URL: /sqlobjects/{NAME}?db={database}

The main pane shows the object’s properties and the full Source SQL body, syntax-highlighted and copyable, so you can see what the view SELECTs without an App Designer round-trip. The sidebar has two related-data toggles.

Related Data Panels

Source Record

When the SQL object is the body of a view-type record, this panel links into the parent record’s detail page so you can see the field list and the rest of the record metadata in one click.

Included in Projects

Lists projects that contain this SQL object as a project item. Useful for tracing migration history of view DDL changes.

What This Consolidates

To see the same thing in App Designer:

• Open Application Designer
• Select File → Open → SQL and load the object
• Read the SQL in the App Designer editor
• Right-click to find which record it backs (if any)
• Open every owning project separately to see migration history

psLens shows the source SQL inline in the browser, with one-click navigation into the related record. Same view DDL, viewable without App Designer.

6 - Pages

What It Is

Pages are the visual screens users interact with in PeopleSoft: the panel definitions from PSPNLDEFN and the per-control bindings from PSPNLFIELD. psLens shows the full control list (every field, label, group box, and subpage on the page), the underlying records each control reads from, and the rest of the metadata graph hanging off the page: which components include it, which PeopleCode is attached, which projects contain it.

Search Page

URL: /pages?db={database}

Wildcard % search supported. Each result card shows the page type (Standard Page, Subpage, Secondary Page, or Search Record) so you can spot reusable subpages versus standalone screens at a glance. The Advanced Filters panel lets you exclude subpages or limit to standard pages only.

Detail Page

URL: /pages/{PAGENAME}?db={database}

The main pane shows Page Properties (type, size, style, audit metadata) and the full Page Fields/Controls table with each control’s record/field binding, label, occurs level, and field type. The sidebar has 6 related-data toggles.

Related Data Panels

Page Fields/Controls

The control inventory: every field control on the page with its PSPNLFIELD row attributes. Each record/field reference deep-links into the matching psLens detail page.

Records Used on Page

The de-duplicated list of records this page reads from. Clicking a record opens its detail page so you can confirm the schema, sample data, or check what else uses it.

Subpages Included

Lists every subpage embedded inside this page. Useful when a control’s data seems to come from somewhere “magic” (it’s almost always a subpage doing the work).

Components Using Page

Lists the components that include this page. Answers “which transactions show this screen to a user?”

PeopleCode

Page Activate PeopleCode. The only event type that lives directly on a page object.

Included in Projects

App Designer projects containing this page as a project item.

What This Consolidates

Without psLens, building this view from App Designer requires:

• Open the page in App Designer to see properties and controls
• For each control, double-click to see its record/field binding
• Run a separate query against PSPNLGROUP to find containing components
• Open each component to confirm the page’s position in the navigation
• Check Activate PeopleCode tab in the page editor for code
• Walk every owning project for migration history

psLens collapses that into one view with everything one click away.

7 - Components

What It Is

Components (called panel groups in older PeopleTools versions) are the user-facing transactions of a PeopleSoft application: a search page plus an ordered set of detail pages that share a single save action. psLens reads PSPNLGROUP / PSPNLGRPDEFN and links the component up to its menus, portal navigation paths, exposing component interfaces, the underlying record hierarchy, and the full PeopleCode event tree.

Search Page

URL: /components?db={database}

Wildcard % search supported. Each result card shows the component market and use type (Classic, Fluid, Both). The Advanced Filters panel filters by market or component type.

Detail Page

URL: /components/{COMPONENT}?db={database}

The main pane shows Component Properties (market, search record, add search record, item description, add/update modes, search PeopleCode flags) and the Component Item List with every page in the component, its labeling, and the hide/display-only flags. The sidebar has 7 related-data toggles.

Related Data Panels

Pages in Component

The page list with each page deep-linked into its own detail page.

Menus Using Component

Every classic menu (PSMENUITEM) that contains a navigation entry for this component. Important for security work since menu/component pairs drive Permission List authorizations.

Portal Navigation Paths

The full set of portal registry paths (PSPRSMDEFN ancestor walk) that lead a user to this component. Useful for “where is this transaction in the menu?” questions.

Component Interfaces

The CIs (PSBCDEFN) that wrap this component as an integration surface. If you have CIs here, programmatic access exists.

Record Level Hierarchy

The scroll/record hierarchy across the pages. Shows the parent-child relationships of records as the component sees them at runtime.

PeopleCode

Component-level PeopleCode events (SearchInit, SearchSave, PreBuild, PostBuild, SavePreChange, SavePostChange, Workflow, etc.) and Component Record/Component Record Field PeopleCode.

Included in Projects

App Designer projects containing this component as a project item.

What This Consolidates

In App Designer / PIA, building this view requires:

• Open the component in App Designer for properties and item list
• Walk each page tab to confirm record bindings
• Run Find In Menus to find classic menu links
• Use the Portal Registry browser to find every CREF tied to the component
• Search for CIs whose component property matches this name
• Open PeopleCode for each event type one tab at a time
• Open each owning project for migration history

psLens collapses all of that into one page.

8 - Component Interfaces

What It Is

Component Interfaces (CIs) are PeopleSoft’s programmatic façade over a component. They expose component properties as get/set properties and component events as callable methods, so integration code can drive the same business logic the UI uses. psLens reads PSBCDEFN for the CI header, PSBCITEM for the property/key list, and PSBCMETHODS for the methods. It also runs two consistency checks against the underlying component to catch the most common breakage: properties that no longer map to a valid record field, and required fields the CI doesn’t expose.

Search Page

URL: /componentinterfaces?db={database}

Wildcard % search supported. Each result card shows the underlying component and CI description.

Detail Page

URL: /componentinterfaces/{CINAME}?db={database}

The main pane shows Component Interface Properties (underlying component, market, security access, owner) plus the items list. The sidebar has 6 related-data toggles, including two consistency-check panels unique to CIs.

Related Data Panels

Items

Every CI property (PSBCITEM): its record/field binding, key indicator, and whether it’s a standard or custom-named property.

CI Methods

Standard methods (Get, Find, Create, Save, Cancel) plus any user-defined methods. Each method links into the matching PeopleCode.

Invalid Properties Check

A consistency check. Flags CI items that no longer match a valid record field on the underlying component — the most common failure mode after a record schema change.

Missing Fields

A consistency check. Flags fields on the underlying component that are required (key fields, search keys, required-input fields) but are not exposed as CI properties. Helps spot where a CI cannot drive a transaction to completion.

PeopleCode References

PeopleCode programs anywhere in the database that mention this CI by name. Useful for finding the App Engine, Service Operation handler, or other CI program that drives this interface.

Included in Projects

App Designer projects that include this CI.

What This Consolidates

To do the same work in App Designer:

• Open the CI to see the property list and methods
• Open the underlying component separately to confirm record/field bindings
• Manually compare CI items against record fields to find drift
• Run Find In PeopleCode to find code that calls this CI
• Open each owning project for migration history

The Invalid Properties panel finds CI items whose record/field binding no longer exists on the underlying component. Missing Fields finds required component fields the CI doesn’t expose — a CI cannot drive a transaction to completion without them. Both are the diff between the CI snapshot and the live component, a check App Designer makes you do by hand.

9 - Menus

What It Is

Menus are PeopleSoft’s classic navigation containers. Each menu (PSMENUDEFN) holds a set of bars, each bar a set of items (PSMENUITEM), and each item points to a component the user can launch. Even in a Fluid-dominant world, classic menus matter for security: Permission List authorizations are granted on menu/component pairs, so understanding which menu owns a component is fundamental to access analysis.

Search Page

URL: /menus?db={database}

Wildcard % search supported. Each card shows the menu type (Standard or Pop-up) and the descriptive long name.

Detail Page

URL: /menus/{MENUNAME}?db={database}

The main pane shows Menu Properties (type, owner, audit metadata). The sidebar has 2 related-data toggles.

Related Data Panels

Menu Items

Every bar and item in the menu, with the component (and market) each item launches. Each component is deep-linked into its own psLens detail page, letting you walk straight from a menu entry into the transaction it triggers.

Included in Projects

App Designer projects that include this menu.

What This Consolidates

In App Designer:

• Open the menu to see bars and items
• Double-click each item to confirm the target component
• Right-click items individually to drill into the component

In psLens, the menu detail page shows the full item list with the component each item launches. Clicking the component name jumps you into a view that already has the menu reference loaded.

10 - Content References

What It Is

Content References (CREFs) are entries in the PeopleSoft Portal Registry — the data structure that drives the menu tree, breadcrumbs, and navigation collections users see in PIA. Each CREF is identified by a portal/object name pair stored in PSPRSMDEFN and can be either a folder (a navigation container) or a content reference (a launchable target, usually a component, but also iScripts, external URLs, and homepage pagelets). psLens shows the CREF’s URI target, the full ancestor walk back to the portal root, every system and custom attribute, and the permission lists that have been granted access.

Search Page

URL: /crefs?db={database}

Search by CREF name or label, with optional filters for portal (EMPLOYEE, CUSTOMER, MOBILE, etc.) and type (CREF vs Folder). Each result card shows the portal, the parent folder path, and the target object name.

Detail Page

URL: /crefs/{PORTAL}/{OBJECTNAME}?db={database}

The main pane shows Properties (portal, parent folder, type, security author, label, description) and the URI / Target card with the destination URL. For component CREFs this is the menu/component path; for iScripts, the iScript URL; for external CREFs, the literal URL. The sidebar has 4 related-data toggles.

Related Data Panels

Navigation Path

The full ancestor chain from the portal root down to this CREF. Every folder in the navigation path is clickable so you can hop up the tree to a parent folder.

Custom Attributes

Per-CREF custom attribute name/value pairs from PSPRSMATTRVAL. Used by Fluid navigation collections, search categories, badges, and other portal features.

System Attributes

System attributes from PSPRSMSYSATTRVL with friendly labels (e.g., PORTAL_LABEL, PORTAL_OBJTYPE_DESC, PTPP_* personalization keys). These configure how the CREF behaves at runtime.

Permissions

Permission lists (PSPRSMPERM) that have been granted access to this CREF — the security side of “who can see this in the menu?”.

What This Consolidates

In PIA, building the same picture means:

• Open PeopleTools → Portal → Structure & Content and walk down the folder tree
• Click into the CREF to see properties
• Tab to Content Ref Administration for attribute values
• Tab to Permission List for security grants
• Click “Edit” on the parent folder repeatedly to climb the breadcrumb tree

psLens shows the entire portal entry (target, attributes, navigation path, security) on one page. Cuts the PIA tab-walk for the security question “who can see this menu item?” — psLens shows the ancestor permission chain in one view.

11 - Message Catalogs

What It Is

The Message Catalog is PeopleSoft’s centralized store of user-facing text. Every MsgGet() call, error dialog, warning, and translated label resolves to a message set + message number pair stored in PSMSGCATDEFN. psLens lets you browse messages by set number, jump directly to a specific set/number, or search by message text. Each message gets a dedicated detail page with its severity, text, explanation, and a usage analysis that finds where it is referenced in PeopleCode and SQL.

Search Page

URL: /messagecatalogs?db={database}

The search page has three entry points: enter a Set Number to see every message in the set, enter free text to Search Message Text, or punch in a specific Set/Number pair to jump straight to that message. The page also surfaces the highest set numbers in use (handy for picking the next free set when creating customizations) and the most recently modified messages.

Detail Page

URL: /messagecatalogs/{SET}/{NUMBER}?db={database}

The detail page has no sidebar toggles; everything loads inline. The main pane shows Message Properties (set, number, severity, last-updated), the full Message Text (with %1, %2 substitution markers preserved), and the Description / Explanation body text developers see when investigating a message.

Usage Analysis

The Usage Analysis card automatically scans every PeopleCode program and SQL object in the database for textual references to this set/number pair: MsgGet(18, 1, ...), MsgGetText(18, 1, ...), SQLExec("...18, 1..."), and so on. Each hit links to the parent object’s detail page. Lets you find every MsgGet / MsgGetText / SQLExec call site for the set/number pair before editing the text.

What This Consolidates

In PIA:

• Open PeopleTools → Utilities → Administration → Message Catalog and search by set
• Walk pages of messages to find the one you want
• Read the message text and explanation
• For usage analysis: run a separate Find In across all PeopleCode

In psLens, the Set/Number jump-to-message is one form submit, and usage analysis runs automatically. The recently-modified list also lets you spot customizations made to delivered messages, a common audit question.

12 - Application Packages

What It Is

Application Packages are PeopleSoft’s object-oriented PeopleCode container — packages hold sub-packages and classes, classes hold methods and properties. They are the standard way to write reusable PeopleCode in PeopleSoft applications. psLens walks the package tree (PSPACKAGEDEFN, PSPACKAGEITEM, PSPCMPROG) and shows the full class hierarchy plus a reverse index of where the package is used: by service operation handlers, by other PeopleCode, and in which projects.

Search Page

URL: /apppackages?db={database}

Wildcard % search supported. Each result card shows the package name and the top-level class names inside it.

Detail Page

URL: /apppackages/{PACKAGENAME}?db={database}

The main pane shows Package Properties (owner, last-updated, source path) and the full Package Structure, a recursive tree of sub-packages and classes with methods, properties, and visibility markers. The sidebar has 3 related-data toggles.

Related Data Panels

Package Structure

The recursive package tree showing every sub-package, class, method, and property. The equivalent of expanding every node in App Designer’s package browser at once. Methods link into their PeopleCode source.

Projects Containing This Package

App Designer projects that include this package as a project item.

Service Operations Using This Package

Integration Broker service operations whose handler is implemented in this package. Lists the IB endpoints that route through this code.

PeopleCode References

PeopleCode programs anywhere in the database that import or instantiate classes from this package — the impact view before refactoring.

What This Consolidates

In App Designer:

• Open the package and expand sub-packages by hand to see the class tree
• Open each class to see methods and properties
• Run Find In PeopleCode to find import statements referencing the package
• Open Integration Broker service operations one at a time to find handler classes
• Open each owning project for migration history

psLens shows the package tree fully expanded, every reference call site, and the IB handler usage on one page. Useful when picking up unfamiliar code: package structure, callers, and IB handler usage in one view.

13 - URL Definitions

What It Is

URL definitions are PeopleSoft’s centralized store of named URL strings. Instead of hard-coding https://example.com/... inside PeopleCode, developers define a URL object (PSURLDEFN) and reference it by name with GetURL("MY_URL"). This keeps environment-specific endpoints (file servers, integration partners, image hosts) out of the code. psLens lets you browse the catalog so you can see every URL the application uses in one place.

Search Page

URL: /urls?db={database}

Wildcard % search supported. Each card shows the URL name plus the resolved URL value so you can scan the catalog at a glance.

Detail Page

URL: /urls/{URLNAME}?db={database}

The main pane shows URL Properties (the URL itself, description, comments, audit metadata). The sidebar has one related-data toggle.

Related Data Panels

Included in Projects

App Designer projects that include this URL. Useful for understanding which feature or customization introduced the URL.

What This Consolidates

In App Designer the URL catalog is buried under File → Open → URL Definition. psLens makes it browsable from a normal search page with the resolved URL inline, so you can quickly find every URL that points at the file server when investigating an attachments issue.

14 - HTML Definitions

What It Is

HTML definitions are PeopleSoft’s catalog of HTML fragments, JavaScript snippets, and template bodies stored in PSCONTDEFN. Anything a page or report needs to embed — a JavaScript helper, an email body template, a custom Fluid grid layout — is normally stored as a named HTML object and pulled into PeopleCode with GetHTMLText(). psLens shows the full content of the definition so you can read what the application is actually injecting at runtime.

Search Page

URL: /htmldefs?db={database}

Wildcard % search supported. Each card shows the HTML object’s name and last-updated metadata.

Detail Page

URL: /htmldefs/{NAME}?db={database}

The main pane shows HTML Definition Properties (description, audit metadata) and the full HTML Content body, syntax-highlighted. The sidebar has one related-data toggle.

Related Data Panels

Included in Projects

App Designer projects that include this HTML object.

What This Consolidates

In App Designer the HTML catalog requires opening File → Open → HTML and loading each object one at a time. psLens makes the catalog searchable and shows the content inline. Useful when tracing a script tag in rendered page source back to its HTML object.

15 - Style Sheets

What It Is

Style sheet definitions are PeopleSoft’s stored CSS objects (PSSTYLEDEFN) — the cascading style sheets that drive Classic and Fluid UI rendering. Tools, themes, branding overrides, and per-page substyle sheets all live here. psLens shows the full CSS body so you can read what rules a specific style sheet contributes without extracting it through App Designer or scraping rendered HTML.

Search Page

URL: /styledefs?db={database}

Wildcard % search supported. Each card shows the style sheet name and last-updated metadata.

Detail Page

URL: /styledefs/{NAME}?db={database}

The main pane shows Style Sheet Definition Properties (description, audit metadata) and the full CSS Content body, syntax-highlighted. The sidebar has one related-data toggle.

Related Data Panels

Included in Projects

App Designer projects that include this style sheet.

What This Consolidates

In App Designer the style sheet catalog requires File → Open → Style Sheet and loading each object individually. psLens lets you search the catalog and read CSS inline. Useful for tracing a custom class override on top of a delivered PT_* style sheet.

16 - Queries

What It Is

Queries are PeopleSoft’s end-user reporting tool — saved SQL queries that users run from the PSQUERY interface, with optional prompts, output formats, and scheduled distribution. Each query is stored in PSQRYDEFN and broken out across PSQRYRECORD, PSQRYFIELD, and other tables for the records and fields it touches. psLens consolidates the query header, the records used, the field list, project membership, and (via the related-data toggles) the query tree placement and security access.

Search Page

URL: /queries?db={database}

Search auto-matches as starts with. Typing PT_ finds every query whose name begins with PT_. Include % yourself for ends-with (%_VW) or contains (%AUDIT%) patterns, or use % alone to list every row. Each card shows the query type (Public, Private, Archive, User), owner, and last-updated metadata. The Advanced Filters panel lets you filter by query type or owner.

Detail Page

URL: /queries/{QRYNAME}?db={database}

The main pane shows Query Properties (type, owner, description, last-run metadata, version), Records Used (every record in the FROM list), and Fields (the SELECT and ORDER BY columns). The sidebar has 3 related-data toggles.

Related Data Panels

Records Used

The list of records used by the query (PSQRYRECORD). Each record name deep-links into its own detail page so you can audit what the query reads.

Fields

The SELECT field list (PSQRYFIELD) with record and field references, each link-resolved.

Included in Projects

App Designer projects containing this query as a project item.

What This Consolidates

In Query Manager / Query Viewer:

• Search by name and open the query in Query Manager
• Walk the Records tab to see the joined records
• Walk the Fields tab to see SELECT and ORDER BY columns
• Tab to Properties for owner and last-run info
• Use a separate database query to find query tree placement and permission list access

psLens consolidates the structural view (records, fields, properties) on one page and adds project membership, useful for both audit work (which queries access sensitive tables?) and impact analysis (will deleting this record break any reports?).

17 - Query Trees

What It Is

Query Access Trees are the security backbone of PeopleSoft Query — hierarchical groupings of records (PSTREEDEFN / PSTREENODE) that determine which records a Query author can build queries against. A permission list grants access to one or more access groups within a tree, and the Query Manager UI only lists records that fall under the granted nodes. psLens shows the tree’s full record hierarchy and the permission lists that authorize it, combining what you’d otherwise need to assemble from Tree Manager and Permission List security separately.

Search Page

URL: /querytrees?db={database}

Search auto-matches as starts with. Typing EOQF finds every tree whose name begins with EOQF. Include % yourself for ends-with or contains patterns, or use % alone to list every query tree in the database.

Detail Page

URL: /querytrees/{TREE_NAME}?db={database}

The main pane shows Tree Properties (status, version, audit metadata) and the full Tree Hierarchy, a recursive view of every node in the tree with the record name it grants access to. The sidebar has one related-data toggle.

Related Data Panels

Tree Hierarchy

The recursive node-by-node breakdown of the tree. Each record link jumps into the record’s detail page so you can see what data the tree grants query access to.

Permission Lists

Permission lists that have been granted access to nodes in this tree. Pair with each permission list’s role membership in the Security pages to get the user-level answer for which users can build queries against these records.

What This Consolidates

In PIA / Tree Manager:

• Open PeopleTools → Tree Manager and navigate to the tree
• Click through the tree nodes one branch at a time to see records
• Open the Query Profile for each permission list separately to see which trees and nodes it authorizes
• Cross-reference manually to answer “who has Query access to record X”

psLens shows the record hierarchy and the permission lists granting access on one page — the source data for any PS/Query security audit. Pairs with the Queries page’s tree placement panel for the inverse question.

18 - Nodes

What It Is

Nodes are the network endpoints of the PeopleSoft Integration Broker. Each external system, partner database, or other PeopleSoft environment that sends or receives messages is represented as a node (PSMSGNODEDEFN). The node carries connection settings (connector type, target URL, authentication mode) and is the unit referenced by every routing rule. psLens shows the node configuration, every routing that involves this node, the service operations granted to its default user, and an inventory of URI text configured against it.

Search Page

URL: /nodes?db={database}

Wildcard % search supported. Each card shows the node type (Local, External, Hub), the node’s active flag, the default user ID, and the descriptive name. Enough at a glance to spot inactive nodes or nodes pointing at unexpected user accounts.

Detail Page

URL: /nodes/{NODENAME}?db={database}

The main pane shows Node Properties: node type, connector ID, default user, authentication option, password-set indicator, contact, and audit metadata. The password-set indicator is the security view: a node with authentication required but no password set is a flag worth investigating (see the Nodes with No Password report). The sidebar has 4 related-data toggles.

Related Data Panels

Routings

Every routing rule (PSIBRTNGDEFN) where this node appears as sender or receiver, with the service operation, direction, and status. Lists the message traffic that flows through this node.

User’s Service Operations

The service operations the node’s default user has been granted permission to invoke. Important for security audits, since a node’s default user can be granted service operations that the human OPRID would never get.

URI Text

The URI text entries configured against the node (PSIBNODEURITEXT). The per-node URL fragments used in REST-style integrations.

Included in Projects

App Designer projects that include the node definition.

What This Consolidates

In PIA:

• Open PeopleTools → Integration Broker → Integration Setup → Nodes to see properties
• Click each tab (Connectors, Portal, WS Security, Routings, Properties) one at a time
• Search Service Operations → Permissions separately to find which operations the node user can call
• Browse Routing Definitions separately to find traffic that involves the node

psLens lets you confirm a node’s security posture and traffic footprint on one page. Useful when reviewing integration configurations or investigating a failing endpoint.

19 - Services

What It Is

A Service is the high-level container in the Integration Broker hierarchy: a logical grouping of related Service Operations (PSSERVICEDEFN). For example, a STUDENT_ENROLLMENT service might contain GET_ENROLLMENT, ADD_ENROLLMENT, and DROP_ENROLLMENT operations. The service itself carries metadata (description, owner, WSDL namespace) and acts as the access point for browsing operations together.

Search Page

URL: /services?db={database}

Wildcard % search supported. Each card shows the service name, alias, and description.

Detail Page

URL: /services/{SERVICE}?db={database}

The main pane shows Service Properties (name, alias, namespace, owner, description, audit metadata). The sidebar has one related-data toggle.

Related Data Panels

Service Operations

Every service operation belonging to the service, each link-resolved into its own detail page. The starting point for understanding what messages the service can exchange.

What This Consolidates

In PIA the service is found under PeopleTools → Integration Broker → Integration Setup → Services, and the operations list is one tab on that page. psLens replicates that single-screen view in the browser, with clickable navigation into each operation. Useful as a jumping-off point when investigating a service’s full message footprint.

20 - Service Operations

What It Is

A Service Operation is the actual message-exchange contract — the unit that defines what message type is sent, in which direction (async or sync), through which routings, and handled by which PeopleCode. Each operation belongs to a service and is stored in PSOPERATION with related metadata in PSOPRDESC, PSOPRROUTING, PSOPRHANDLER, and the security tables. psLens consolidates the full operation — versions, routings, handlers, caller nodes, security access from three angles, and live IB transaction history — into one page.

Search Page

URL: /serviceoperations?db={database}

Wildcard % search supported. Each card shows the operation type (Async, Sync, One Way), default version, and active flag.

Detail Page

URL: /serviceoperations/{OPERATION}?db={database}

The main pane shows Operation Properties plus four always-visible cards: Versions (every operation version with default flag and message type), Routings (every routing definition with sender/receiver nodes and direction), Handlers (handler PeopleCode and class implementations), and HTTP Request Template (the template body for HTTP-style transactions). The sidebar has 5 related-data toggles, including three security access lenses and a live IB transaction history feed.

Related Data Panels

Permission Lists with Access

Permission lists with Full Access or Web Library Access to this operation. The security baseline for which permission lists let a user invoke this operation.

Roles with Access

The roles that contain any of the granting permission lists — saves you from having to walk Permission List → Role mapping manually.

Users with Access

The users whose role membership ultimately grants them access to call this operation, with an optional toggle to include or exclude locked accounts. The end-of-chain answer for who can call this endpoint.

Caller Nodes

Inverts the lens to the integration side: lists nodes whose default user has been granted access to invoke this operation — useful for confirming which external systems can call the endpoint.

IB Transaction History

Recent runtime invocations from PSIBLOGHDR — timestamps, status, transaction ID. The link from “what is configured” to “what is actually happening.” Lets you confirm an operation is being called (or spot that it never is).

What This Consolidates

In PIA, the equivalent investigation requires:

• Open PeopleTools → Integration Broker → Integration Setup → Service Operations for properties and version
• Switch to the Handlers and Routings tabs separately
• Open Security → Permissions & Roles → Permission Lists and search Web Services tab per permission list
• Cross-reference Role membership in Roles
• Walk User Profile Roles tab to find users
• Open Service Operation Monitor → Asynchronous Services to find recent activity

psLens combines configuration, three layers of security access, and live transaction history on one page — the questions a security review asks about every IB endpoint.

21 - Messages

What It Is

A Message definition is the payload schema that a Service Operation carries. It defines the structure of the XML or JSON document exchanged between systems. Messages can be rowset-based (mapped to PeopleSoft records), nonrowset-based (free-form XML/JSON), container, or document. psLens reads PSMSGDEFN and the version-specific details from PSMSGSCHEMA, then surfaces the service operations that reference each message and the projects that own them.

Search Page

URL: /msgdefns?db={database}

Wildcard % search supported. Each card shows the message type and version.

Detail Page

URL: /msgdefns/{MESSAGE}?db={database}

The main pane shows Message Properties (alias, owner, description, audit metadata) and a per-version card listing each message version with its type (Nonrowset-Based, Rowset-Based, Container, Document) and the schema details. The sidebar has 2 related-data toggles.

Related Data Panels

Service Operations Using This Message

Service operations that reference this message as a request or response payload.

Projects Containing This Message

App Designer projects containing this message as a project item.

What This Consolidates

In PIA you’d open PeopleTools → Integration Broker → Integration Setup → Messages, switch to the appropriate version, and then separately walk the service operation registry to find references. psLens shows the message and the operations that use it side by side, so you can confirm callers before changing the schema.

22 - Queues

What It Is

A Queue is an Integration Broker ordering construct. Async service operations attached to the same queue process serially in the order they arrived, while operations on different queues can run in parallel. Queues are also the unit where IB pauses (“Pause” status) when an administrator stops message processing for maintenance. Each queue is stored in PSQUEUEDEFN with a status (Run, Pause) and a partitioning configuration.

Search Page

URL: /queues?db={database}

Wildcard % search supported. Each card shows the queue’s run/pause status, the fast way to spot a paused queue causing a stalled integration.

Detail Page

URL: /queues/{QUEUE}?db={database}

The main pane shows Queue Properties (status, partitioning method, archive flag, owner, description) and a Service Operations Using This Queue card. Queues are simple objects — there are no sidebar toggles.

Service Operations Using This Queue

The list of service operations bound to this queue. Together with the IB Monitor, this shows what stops processing when the queue is paused.

What This Consolidates

In PIA, queue configuration lives under PeopleTools → Integration Broker → Integration Setup → Queues, and the link to dependent service operations requires walking each operation separately. psLens shows the queue status and its dependent operations on one page.

23 - App Engines

What It Is

Application Engines (AE) are PeopleSoft’s batch processing framework. Unlike traditional COBOL or SQR programs, Application Engine programs are defined in PeopleSoft metadata tables (such as PSAEAPPLDEFN, PSAESECTDEFN, PSAESTEPDEFN, and PSAESTMTDEFN) and executed by the psae batch executable. They are commonly used for data processing, background calculations, integrations, and ETL processes.

psLens allows you to search and browse the structure of Application Engine programs, inspect their sections, steps, and actions, and view the associated SQL and PeopleCode source code without opening App Designer.

Search Page

URL: /appengines?db={database}

• Search: Search for Application Engines by program name (prefix match). Type PSAE to find all AEs starting with PSAE. Use % as a wildcard if needed (e.g., %PRCS% to find programs containing PRCS).
• Metadata Card: Each search result card shows the program description, owner ID, and last modified operator/timestamp.

Detail Page

URL: /appengines/{APPLID}?db={database}

The Detail Page exposes the internal structure of the Application Engine program:

• Program Properties: Shows description, owner ID, program type (Standard, Upgrade, Import, Daemon), active status, disable restart setting, and modification details.
• Sections & Steps Tree: Lists all sections (e.g., MAIN) and steps defined in the program.
• Actions View: For each step, psLens shows the actions it executes (SQL, PeopleCode, Call Section, Log Message, XSLT, Do Select, Do Until, Do While, Do When).
• Source Code Viewer: Steps that run SQL or PeopleCode actions can be expanded to view the actual code inline.
• Export as Markdown: Reconstructs the entire Application Engine structure, including all sections, steps, actions, and embedded code, into a single structured Markdown file.

24 - Process Definitions

What It Is

Process Definitions define the batch programs, reports, and scripts that can be executed via the PeopleSoft Process Scheduler. They map a logical process name to an underlying program type (SQR, Application Engine, COBOL, Crystal, XML Publisher, etc.) and define how it executes, its parameters, and where its outputs are delivered.

psLens allows you to browse these definitions, check execution statistics (run counts, average durations, success rates), and review their configuration.

Search Page

URL: /processdefinitions?db={database}

• Search: Search by process name (prefix match) or select advanced filters.
• Filters: Filter process definitions by process type (e.g., Application Engine, SQR Report), component, and last modified info.

Detail Page

URL: /processdefinitions/{PRCSTYPE}/{PRCSNAME}?db={database}

The Detail Page displays:

• Configuration & Properties: Displays execution details like the command-line parameters, target server name, API awareness, run control component, and priority.
• Output Settings: Shows output type (Web, File, Printer) and output format (PDF, CSV, HTML, etc.).
• Execution Statistics: psLens analyzes historical process request data to present statistics on:
  • Total runs and average duration.
  • Status breakdown (Success vs Error / Cancelled).
  • Top operators who run the process.
  • Top servers where the process executes.
• Export as Markdown: Export the process definition details as a markdown document.

25 - Process Jobs

What It Is

Process Jobs (also called Job Definitions) are groups of one or more process definitions (or other jobs) bundled together to run as a single scheduled unit. A job executes its constituent processes in a defined sequence or in parallel, depending on the job definition.

psLens allows you to browse job definitions, inspect the list of items inside each job, and check their execution sequence.

Search Page

URL: /processjobs?db={database}

• Search: Search for job definitions by job name (prefix match).
• Metadata Card: Results display the job description, owner, and modification timestamps.

Detail Page

URL: /processjobs/{JOBNAME}?db={database}

The Detail Page displays:

• Job Properties: Basic settings, such as description, run control validation, and server settings.
• Job Items & Sequence: A table showing all processes and sub-jobs nested within this job, including:
  • Run order/sequence number.
  • Process Type and Process Name.
  • Description.
  • Run mode (e.g., Serial, Parallel).
• Export as Markdown: Export the job definition and its sequence table to a markdown document.

26 - Recurrences

What It Is

Recurrences define repeating schedule patterns used by the PeopleSoft Process Scheduler. Whenever a process or job is scheduled to run on a repeating schedule (e.g., daily, weekly, hourly), it is linked to a recurrence definition.

psLens allows you to search and view recurrence patterns to understand when a scheduled task is slated to run next and how frequently it triggers.

Search Page

URL: /recurrences?db={database}

• Search: Search recurrence definitions by name (prefix match).
• Metadata Card: Shows the description, owner, and modification timestamps.

Detail Page

URL: /recurrences/{RECURNAME}?db={database}

The Detail Page displays:

• Recurrence Pattern Details: Shows recurrence settings such as:
  • Frequency (Daily, Weekly, Monthly, Hourly).
  • Run times (e.g., Daily at 12:00 AM, or every 5 minutes).
  • Selection of specific days of the week or month.
  • Start and end dates/times.
• Next Run Prediction: Displays when the recurrence is next due to execute.
• Export as Markdown: Export the recurrence schedule parameters as a markdown file.

27 - Server Definitions

What It Is

Server Definitions represent the Process Scheduler Servers that are defined inside PeopleSoft. These servers execute the batch processes (like Application Engines, SQRs, etc.) and manage scheduling recurrences and daemon processes.

psLens allows you to search and browse server definitions to see how a server is configured, check its live heartbeat status, see active running processes, review what process classes and categories it is authorized to run, check operational schedules, and view its notification routing.

Search Page

URL: /servers?db={database}

• Search: Search for server definitions by name (prefix match, e.g., PRCS%).
• Metadata Card: Shows the description, operating system, daemon status, and modification timestamps.

Detail Page

URL: /servers/{SERVERNAME}?db={database}

The Detail Page displays:

• Server Status: Shows real-time heartbeat and diagnostics from PSSERVERSTAT including:
  • Current status (Running, Down, Suspended, Overloaded, etc.) with relative “time ago” timestamps.
  • CPU and Memory utilization.
  • Free disk space and thresholds.
  • AE/OE Server counts.
• Active Running Processes: Live grid of active processes (Initiated, Processing, Running) currently executing on the server from PSPRCSRQST.
• Server Definition Properties: Displays configuration metrics like version, sleep time, heartbeat frequency, max concurrent API aware/unaware tasks, distribution node details, CPU/Memory threshold configs, and load balancing/redistribution option choices.
• Server Daemon Details: Shows daemon configuration:
  • Enabled state, daemon group, sleep time, recycle counts.
  • Active daemon process instance (with direct link to its Process Monitor view).
• Process Categories: Authorized process categories with priority and max concurrent execution counts.
• Process Types: Specific process types the server is configured to run, categorized by operating system, priority, and concurrent limits.
• Server Operation Times: Scheduled operation windows when the server is active (24/7 or day/time ranges).
• Status Notifications: List of users and roles notified upon server status changes (e.g., when the server goes down or encounters an error), displaying active status flags as checkboxes.
• Export as Markdown: Export the entire server definition structure and live status/child tables as a markdown file.