PeopleSoft Fluid User Interface Ed 1 — Lesson 1: Fluid Architecture, Components, Pages, and Navigation

Technical Scope

• Fluid rendering model, responsive principles, component types, and runtime behavior
• Fluid pages, subpages, group boxes, layout controls, styles, and component properties
• component registration, content references, navigation collections, and portal integration
• browser inspection, layout defects, component access, and navigation verification

Instructor Demonstration

The instructor traces Fluid rendering model, responsive principles, component types, and runtime behavior, then connects it to Fluid pages, subpages, group boxes, layout controls, styles, and component properties. The demonstration captures the exact configuration, transaction, command, query, log, or screen evidence needed to prove intended behavior and the applicable control boundary.

Applied Workshop

Learners complete a controlled exercise that applies Fluid pages, subpages, group boxes, layout controls, styles, and component properties and component registration, content references, navigation collections, and portal integration. The exercise introduces a realistic exception related to browser inspection, layout defects, component access, and navigation verification and requires a reversible correction supported by before-and-after evidence.

1. Confirm scope, identities, data, dependencies, controls, and expected result.
2. Perform the product-specific configuration or analysis and record exact steps.
3. Validate functional behavior, security, data integrity, and operational observability.
4. Introduce the defined failure condition, diagnose the cause, and apply a safe correction.
5. Document rollback, acceptance evidence, unresolved risk, and ownership.

Validation Standard

Acceptance requires accurate handling of component registration, content references, navigation collections, and portal integration, traceable proof for Fluid rendering model, responsive principles, component types, and runtime behavior, and a repeatable recovery path for browser inspection, layout defects, component access, and navigation verification. Results must be understandable to both implementers and operational support teams.

Failure Analysis

Learners compare symptoms, logs, state, dependencies, and recent changes when browser inspection, layout defects, component access, and navigation verification occurs. The final diagnosis must separate the immediate fix from the preventive control.

Practical Outcome

The completed output is a tested fluid architecture, components, pages, and navigation implementation or analysis, with validation evidence, troubleshooting notes, rollback guidance, and a concise operational handover.