PeopleSoft Fluid User Interface Ed 1 — Lesson 2: Tiles, Homepages, Activity Guides, and Branding

Technical Scope

• tiles, dynamic content, tile images, badges, permissions, and personalization
• homepages, folders, sequencing, defaults, user preferences, and role-based delivery
• activity guides, guided processes, step status, context, and transactional handoff
• branding, theme variables, logos, style sheets, and controlled visual customization

Instructor Demonstration

The instructor configures and validates tiles, dynamic content, tile images, badges, permissions, and personalization, then connects it to homepages, folders, sequencing, defaults, user preferences, and role-based delivery. 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 build and verify an implementation covering homepages, folders, sequencing, defaults, user preferences, and role-based delivery and activity guides, guided processes, step status, context, and transactional handoff. The exercise introduces a realistic exception related to branding, theme variables, logos, style sheets, and controlled visual customization 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 activity guides, guided processes, step status, context, and transactional handoff, traceable proof for tiles, dynamic content, tile images, badges, permissions, and personalization, and a repeatable recovery path for branding, theme variables, logos, style sheets, and controlled visual customization. Results must be understandable to both implementers and operational support teams.

Failure Analysis

Learners compare symptoms, logs, state, dependencies, and recent changes when branding, theme variables, logos, style sheets, and controlled visual customization occurs. The final diagnosis must separate the immediate fix from the preventive control.

Practical Outcome

The completed output is a tested tiles, homepages, activity guides, and branding implementation or analysis, with validation evidence, troubleshooting notes, rollback guidance, and a concise operational handover.