1. Administration Guide
  2. Customer Module Management
  3. Saving or Discarding Customer Module Changes

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

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.