10 Customer Module Management

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

Figure 10-1 Retail Home Customer Modules Management Page

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 applications to be configured first since information about modules resides in the applications' Module Definition Framework (MDF) data.

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 10-2 Customer Modules Management Link within Retail Home's Settings Menu

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

Only modules provisioned to the customer are displayed.

Figure 10-3 Retail Home Customer Modules Management Page

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 10-4 Customer Modules Management Page's Toggle Components for Active Statuses

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 10-5 Customer Modules Management page's Cancel and Save Buttons

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 page's "Cancel" button discards all changes made to the applications and modules.

Example Usage with POM:

POM Batches can be enabled/disabled using Retail Home CMM. The changes, once saved, are applied to the corresponding Platform Service deployment on the target app. The user then logs into the POM application, navigates to the "Batch Administration" page and clicks the "Sync with MDF" button. This initiates Platform Service calls between CMM & POM to sync the module status.

Resetting Activation Status to Default

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

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

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