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.

Apps

Feature	Action Required
Guided Campaigns App for Eloqua	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.

User Experience

Feature	Impact
Eloqua's Redwood Experience	Small scale

Data

Feature	Impact
SFTP Imports/Exports - SSH cipher updates	Small scale
Data Import – Incorrectly formatted file errors	Small scale

Integrations

Feature	Impact
Oracle Sales App Enhancements	Small scale
Eloqua's Salesforce App Updates	Small scale

Marketing-Level

Feature	Impact
Block Redirect Link Requests with Invalid Authentication Hashes	Small scale

Developer Changelog

Feature	Impact
Bulk API Updates	Small scale
API Updates	Small scale