Component Interfaces
Categories:
- Target Database: —
- Context Type: —
- Alert Severity: —
- Triggered Time: —
- Firing Context:
—
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}
Component Interface search results for USER%
Wildcard % search supported. Each result card shows the underlying component and CI description.
Detail Page
URL: /componentinterfaces/{CINAME}?db={database}
Component Interface detail page for USER_PROFILE
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 with key flag, record/field binding, and standard/custom indicator
Every CI property (PSBCITEM): its record/field binding, key indicator, and whether it’s a standard or custom-named property.
CI Methods
Standard and user-defined methods on the CI
Standard methods (Get, Find, Create, Save, Cancel) plus any user-defined methods. Each method links into the matching PeopleCode.
Invalid Properties Check
Items that no longer match a valid record field on the underlying component
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
Required fields on the underlying component that the CI does not expose
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 instantiate this CI
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
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.