Oracle WebCenter Portal 11g: Creating Portals Using ADF — Lesson 2: Pages, Navigation, Task Flows, and Data Presentation

Technical Scope

• page creation, layout components, fragments, regions, and responsive considerations
• unbounded and bounded task flows, parameters, navigation cases, and return values
• navigation models, menus, breadcrumbs, links, and role-aware visibility
• ADF data controls, bindings, tables, forms, validation, and functional tests

Instructor Demonstration

The instructor will configure and verify page creation, layout components, fragments, regions, and responsive considerations in the context of a role-aware employee portal assembled from reusable ADF components and WebCenter services with a controlled deployment path. The demonstration captures commands, configuration, transactions, output, logs, plans, or screenshots that prove both the intended behavior and the control boundary.

Applied Workshop

Learners complete a controlled exercise covering unbounded and bounded task flows, parameters, navigation cases, and return values and navigation models, menus, breadcrumbs, links, and role-aware visibility, then introduce a realistic exception involving ADF data controls, bindings, tables, forms, validation, and functional tests. They record assumptions, exact steps, expected and observed results, a reversible correction, and the evidence required for operational acceptance.

1. Confirm scope, identities, data, dependencies, controls, and expected result.
2. Perform the product-specific configuration, development, analysis, or business-process task.
3. Capture reproducible technical or transaction evidence and compare it with the expected value.
4. Explain the operational, security, performance, data-quality, or business trade-off.

Validation Standard

Acceptance for Pages, Navigation, Task Flows, and Data Presentation requires the result to be reproducible, traceable to approved inputs, consistent with the relevant Oracle or platform behavior, and supported by checks for security, data integrity, reliability, performance, and recoverability.

• The intended target, scope, and ownership are verified.
• Expected-value and negative-path checks pass.
• Security, reliability, performance, data quality, and support impacts are reviewed.
• Unexpected behavior is resolved before acceptance.

Failure Analysis

When the result differs from expectation, learners isolate the smallest proven cause across page creation, layout components, fragments, regions, and responsive considerations, unbounded and bounded task flows, parameters, navigation cases, and return values, navigation models, menus, breadcrumbs, links, and role-aware visibility; they avoid speculative production changes, preserve evidence, apply the lowest-risk correction, rerun the test, and document prevention.

Practical Outcome

Complete and defend a validated result for Pages, Navigation, Task Flows, and Data Presentation with a reusable implementation record or runbook.