Why PeopleSoft is NOT API-First and What That Means for Integrations

PeopleSoft's architecture couples business logic directly to UI Components. Learn why this UI-first design makes integrations difficult, how Component Interfaces simulate user keying, and why SWS is a pragmatic read-only solution.

Introducing psLens — PeopleSoft Operations & Security Intelligence in Your Browser

Meet psLens: a read-only, browser-based console to look up any PeopleSoft object, audit security, and monitor Process Scheduler and Integration Broker — no App Designer or SQL required. Watch the intro video.

Lock Down IB Now - Active Threats to PeopleSoft and Oracle E-Business Suite

AI Agents in PeopleSoft in Weeks, Not Months

How to use SWS (Simple Web Services) as the data layer for an MCP server that connects AI agents to PeopleSoft, without turning it into a custom development project.

Export Project Item List to Markdown

A SQL to pull a list of project items for a given project.

Proxy-Credential User Switching in Signon PeopleCode

A pattern for letting a trusted backend service mint a PS_TOKEN for a specific end user without ever seeing that user's password. Uses only documented PeopleSoft APIs — and should only be granted to extremely privileged service accounts.

Component Interface Quality Audits

The following SQL queries can be used to audit Component Interfaces for common quality issues related to menu registration, item property names, and collection names.

The 10-Step Process for Developing PeopleSoft Component Interfaces

A battle-tested 10-step workflow for PeopleSoft Component Interface development — from evaluating the requirement through production-ready code.

Component Interface Error - Unknown key of uninstantiated object some-record-name.some-field-name (91,16)

A weird invalid CI state that is not surfaced with standard CI audits and checks.