Enabling Redwood Capabilities
What this domain tests
This domain tests the Redwood user experience in the Payables and Expenses flow: what Redwood changes, how it is enabled, which capabilities it adds, and what must be tested before rollout.
Core rules
- Redwood is Oracle's design system and user experience, not a separate accounting module. It changes navigation, page layout, search, accessibility, and interaction patterns while the underlying business rules remain.
- Redwood pages are enabled through profile options or offering-level opt-ins, depending on the page. Confirm the current control for the specific page rather than assuming a single global switch.
- Redwood capabilities include responsive layouts, activity centers, inline actions, guided processes, consistent search, and accessible components.
- Supported Payables and Expenses pages may include invoice work areas, payment pages, and expense entry or approval. Not every classic page has a Redwood equivalent at the same time.
- Personalizations, extensions, and custom roles must be retested. A Redwood rollout can expose hard-coded classic navigation or unsupported customizations.
- Redwood does not change subledger accounting, matching, tolerances, or payment formatting. Those remain configuration and process rules.
Worked example
A team enables Redwood for a pilot business unit. Invoice entry and approval work, but a custom region on the classic invoice page does not appear. The team confirms the page is not yet Redwood-supported, keeps the classic page for that task, and tests the standard Redwood invoice actions before expanding the rollout.
Traps
- Treating Redwood as a new ledger or module.
- Assuming one enablement switch covers every page.
- Forgetting to retest personalizations and extensions.
- Expecting Redwood to change approval or accounting behavior.