Go to primary content
Oracle® Retail Home Oracle Retail Home Administration Guide
Release 3.0.2
F16712-02
  Go To Table Of Contents
Contents

Previous
Previous
 
Next
Next
 

4 Customer Modules Management

The Retail Home Customer Modules Management page gives customer administrators the ability to activate or deactivate provisioned applications and modules.

Figure 4-1 Retail Home Customer Modules Management Page

Surrounding text describes Figure 4-1 .

Applications and modules that are deactivated will not be accessible to users. Scheduled batch processes may also be halted when those processes are tied to deactivated applications and modules.

The management of customer modules in Retail Home requires domains to be configured first since information about customer-provisioned applications and modules reside in the domains' Module Definition Framework (MDF) data.

For more information about domain configuration, refer to the section "Domain Configuration."

Launching the Customer Modules Management Page

The Customer Modules Management page can be launched from the Retail Home Settings menu's Application Administration section.

Figure 4-2 Customer Modules Management Link within Retail Home's Settings Menu

Surrounding text describes Figure 4-2 .

The Customer Modules Page displays the customer-provisioned modules in a hierarchical table structure.

Only modules provisioned to the customer are displayed.

Figure 4-3 Retail Home Customer Modules Management Page

Surrounding text describes Figure 4-3 .

The columns include:

  • Module Code - A unique identifier for an application or module.

  • Module Name - The descriptive name of the application or module.

  • Type - The type of module which can be one of the following:

    • Application - A Retail Application

    • Module - A feature within the Retail Application or another module.

    • Group - A grouping of applications or modules.

  • Offer - The offer code used to provision the application to the customer.

  • Active - A flag indicating if the application or module is active or not.

Activating and Deactivating Customer Modules

Customer administrators can activate or deactivate customer-provisioned applications or modules by interacting with the toggles for each row's Active column.

Figure 4-4 Customer Modules Management Page's Toggle Components for Active Statuses

Surrounding text describes Figure 4-4 .

Only "Application" or "Module" typed rows can be toggled.

Toggling the active state of an application or module also toggles the state of child modules.

When a parent application or module is deactivated, its child modules will be deactivated and their toggle components will be disabled. Activating the parent, activates the child modules and enables their toggles.

Saving or Discarding Customer Module Changes

Changes to the activation states are not persistent until the user clicks on the page's Save button.

Figure 4-5 Customer Modules Management page's Cancel and Save Buttons

Surrounding text describes Figure 4-5 .

Once the changes are saved:

  • Deactivated applications and modules will cause applications and features to be inaccessible to users. Scheduled batch processes may also be halted when those processes are tied to deactivated applications and modules.

  • The association of applications to domains is recalculated. Refer to the section "Domain Configuration" for more information about domains in Retail Home.

The page's Cancel button discards all changes made to the applications and modules.

Resetting Activation Status to Default

The Reset to Defaults button reverts the activation status of all provisioned applications and modules to default.

Figure 4-6 Customer Modules Management Page's Reset to Defaults Button

Surrounding text describes Figure 4-6 .

Reset values are not saved until the user clicks on the page's Save button.