1 Feature Summary

This chapter describes the feature enhancements in this release.

Noteworthy Enhancements

This guide outlines the information you need to know about new or improved functionality in the Oracle CrowdTwist Loyalty and Engagement update and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, tips or considerations that you should keep in mind, and the resources available to help you.

Column Definitions

  • Feature: Provides a description of the feature being delivered.

  • Module Impacted: Identifies the module associated with the feature, if any.

  • Scale: Identifies the size of the feature. Options are:

    • Small: These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.

    • Large: These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.

  • Delivered: Is the new feature available for use immediately after upgrade or must the feature be enabled or configured? If no, the feature is non-disruptive to end users and action is required (detailed steps below) to make the feature ready to use.

  • Customer Action Required: You must take action before these features can be used. These features are delivered disabled and you choose if and when to enable them.

Table 1-1 Noteworthy Enhancements

Feature Scale Delivered Customer Action Required?
Commerce

Small

Enabled

No

Commerce

Customize Channels for Your Loyalty Program

Members with write permissions to Commerce can now manage the Channel IDs and Channel Names available within their program. This functionality lets you create and manage channels that correspond to your business. Channel management is available in the Control Center under Settings > Commerce > Channels:

This image shows sample channel names and identification numbers.

Channels added or renamed are reflected throughout your program (APIs, Control Center) and in reporting.