Feature Summary

Features Delivered Disabled: Customer Action Required for Use

This table provides a summary of the features that require customer action before they can be used by end users. These features are delivered in a disabled state, and you can choose if and when to enable them.

Examples of such features include:

  • New or expanded BI subject areas that need to be incorporated into reports
  • Integration required to utilize new web services
  • Features that must be assigned to user roles before they can be accessed

These features are non-disruptive since they remain inactive until you take action. You can selectively enable them, allowing you to set your own testing and rollout schedule.

Redwood Experience

Feature Action Required
Generate a List of Inspection Characteristics Based On Inspection Details using Generative AI Setup Required
Perform Quality Inspections using the Redwood Experience Setup Required
Manage Inspection Plans using the Redwood Experience Setup Required
Manage Inspection Levels using the Redwood Experience Setup Required

SCM Common Components

Feature Action Required
Create Guided Journeys for Redwood Pages Visual Builder

Product Hub

Feature Action Required
Autocreate UOM Conversions When Adding a Packaging String to an Item Opt In
Calculate Runtime Transaction UOM Conversions with Generated Item Data Opt In
Query Item Revisions Using the New Item Revision LOV REST Service and Additional Attributes Using the Existing Items LOV REST Service REST APIs
Enrich Your Product Information From an External Healthcare Catalog Opt In plus Setup

Redwood Experience

Feature Action Required
Analyze Structure Details in Level Structure View Setup Required
Enhance Manufacturer Management Setup Required

Product Lifecycle Management Common

Feature Action Required
Track Affected Object Redlines and Other Updates on Changes Opt In plus Setup

Redwood Experience

Feature Action Required
Search and Analyze Workflows Setup Required

Features Delivered Enabled: Ready for Use by End Users

This table provides a summary of the features included in the document that are ready to be used by end users.

The impact of these features can be categorized as follows:

  • Larger Scale UI or Process-Based: These features have a higher potential impact on users due to their complex designs. Focus your acceptance testing on these features.
  • Small Scale UI or Process-Based: These features have minimal impact on users and typically involve minor changes to fields, validations, or programs.
  • Report: These features have minimal impact on users and include new or modified, Oracle-delivered, ready-to-run reports.

Product Hub

Feature Impact
Update Unit of Measure for an Item Larger scale
Selected Product Hub Bug Fixes in This Update Small scale

Product Development & Product Hub Common

Feature Impact
Selected Product Development & Product Hub Bug Fixes in This Update Small scale