Cloud Readiness / Oracle Loyalty Cloud
What's New
  1. Update 19C
  1. Revision History
  2. Overview
  3. Feature Summary
    1. Loyalty Cloud
        1. Standard Import/Export Uptake - Loyalty Phase 1 - Transaction
        2. PUID Uptake for Loyalty Objects
        3. All Loyalty Enhancements for 19C

Update 19C

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date Feature Notes
21 JUN 2019   Created initial document.

Overview

Oracle Loyalty Cloud offers an enterprise class, comprehensive, cross-channel loyalty solution that allows organizations to manage the complete loyalty program lifecycle.

Using Oracle Loyalty Cloud you can track, reward and recognize customer behavior, including repeat purchase of products and services, referrals to friends and family, desirable social behavior, and doing business with the partners of the loyalty program. Companies can encourage desirable member behavior and foster long-term customer loyalty by creating reward programs and promotions.

Loyalty Programs can use Oracle Loyalty Cloud to acquire and retain high value customers and also to move other customers into high value segments by offering them incentives for buying more or for becoming influential brand advocates.

All the key loyalty program, membership and transaction functionality are also available via REST APIs for consistent customer experience across all channels.

This guide outlines the information you need to know about new or improved functionality in this 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, any tips or considerations that you should keep in mind, and the resources available to help you.

CUSTOMERS UPGRADING FROM RELEASE 12

If you're upgrading from Release 12 to Release 13, then you should review all of the release readiness content for Release 13 (updates 17B - 17D, 18A - 18C, as well as updates 19A - 19C) to learn about all of the features available in Release 13.

GIVE US FEEDBACK

We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.

Feature Summary

Column Definitions:

Report = New or modified, Oracle-delivered, ready to run reports.

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

UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.


Customer Action Required = You MUST take action before these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.

Ready for Use by End Users
(Feature Delivered Enabled)

Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features.

Customer Must Take Action before Use by End Users
(Feature Delivered Disabled)

Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing.

Feature

Report

UI or
Process-Based:
Small Scale

UI or
Process-Based:
Larger Scale*

Customer Action Required

Loyalty Cloud

Standard Import/Export Uptake - Loyalty Phase 1 - Transaction

PUID Uptake for Loyalty Objects

All Loyalty Enhancements for 19C

Loyalty Cloud

Standard Import/Export Uptake - Loyalty Phase 1 - Transaction

The Standard Import/Export Framework Uptake is an upgraded version of the Classic Import/Export Framework that has been used to perform data migration from external systems to Oracle Loyalty Cloud. The previous framework had restrictions to incorporate custom logic during data migration. The latest Standard Import/Export Uptake would be based on REST API Framework migration would bring in consistency in terms of data consolidation. The same custom logic can be used for REST API and Standard Import. This particular feature uptake is for creating the Simplified Import/Export Framework for the Transaction Object.

The Standard (Simplified) Import/Export Uptake is a part of general release available for all customers of Oracle Loyalty Cloud and would be available Out-Of-The-Box.

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Role Information

The role that can be used to access this feature is LOYALTY_PROGRAM_ADMINISTRATOR.

PUID Uptake for Loyalty Objects

The PUID Uptake (Business Key Update) for Loyalty Objects is used to create unique identifiers for accessing the Objects, Child Objects and attributes used in Loyalty Cloud. This provides a user-friendly and comprehensible identification of objects specific to Loyalty Cloud platform. Public Identifiers are alternate keys that can be exposed in the UI to the product user and used in all channels (UI, Services, Import) to reference objects. PUIDs are either specified by the user (or external interface) during object creation or generated by a central internal routine of Oracle Loyalty Cloud.

This feature is provided out-of-the-box for all the Oracle Loyalty Cloud Users and will be accessible to all customers. Explicit Configuration is required only if a different PUID format is desired other than the default one provided by Loyalty Cloud. The steps are as follows:

  1. Regression Testing on the Object Area.
  2. Verification of the format of the PUID Value.
  3. Verification of the updatability of the PUID Attribute.
  4. Verification of the uniqueness of the PUID Attribute.
  5. Verification of the PUID Attribute as displayed in the REST Payload.

Steps to Enable

You don't need to do anything to enable this feature.

Role Information

The role that can be used to access this feature is LOYALTY_PROGRAM_ADMINISTRATOR.

All Loyalty Enhancements for 19C

The Loyalty Cloud Enhancements are small additions or updates to the existing features of the Oracle Loyalty Cloud that are not complete functionalities as such but add-ons to supplement the functioning of an existing functionality. For 19C, following are the enhancements included:

1. Support for DELETE Operation on Transaction REST

It is extremely important that Transactions that have been added into the Oracle Loyalty Cloud and are not processed yet must be allowed to be purged or removed from the system. In Release 19B, support for DELETE Operation through Import procedure had been provided. However, it is also important to perform the operation through external interfaces through REST APIs. This is because external customer systems interface with Oracle Loyalty Cloud through REST API and it is not regularly feasible to perform the delete by logging into the Loyalty Cloud Interface. This enhancement provides the DELETE functionality by deleting Transactions in "In Progress" status using the Transaction REST API.

2. Event Driven Rewards Enhancement.

The functionality of Event Driven Rewards is to provide additional benefits to the members of the Loyalty Program for certain events such as anniversary, birth-date or any custom event chosen by Program Manager. This is an effective but sure way of enhancing the engagement of Loyalty Members within a Loyalty Program by triggering the Emotional Loyalty aspect of a consumer. However, it is important that such rewards are provided to all the customers at the right events at scale. This enhancement is used to enhance the Event Driven Rewards Batch Job from Scalability point-of-view to execute the rewards for multiple members for multiple events.

3. Purge Member and Transaction ESS Job.

Apart from the functionality to delete or purge the Members and Transactions through Import Procedure and Interface through REST API, it is also important to provide a batch process to perform this operation in Bulk. For example Loyalty Program Manager decides to purge last 5 years transactions for members. This operation through Import or Interface would generally require a lot of time. Providing an ESS Job that will perform batch operation in bulk in an immediate or scheduled manner with the right parameters will help save time and also automate the procedure avoiding reworks.

The Loyalty Enhancements for 19C are a part of general release available for all customers of Oracle Loyalty Cloud and would be available Out-Of-The-Box.

Steps to Enable

Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center > your apps service area of interest > REST API). If you are new to Oracle's REST services you may want to begin with the Quick Start section.

Role Information

The role that can be used to access this feature is LOYALTY_PROGRAM_ADMINISTRATOR.