Motivation

For those customers upgrading from previous versions that have already existing private pages, and also for those willing to use them, we need to add a configuration and define the way in which private pages will be reactivated.

• Enabling check should be at site, instance and system levels

• Enabling should be automatic when there are already existing private pages. It should be enabled just for those sites including private pages.

Note.- We've decided to reduce the activation to disabling the release feature flag (RFF). That is, new customers willing to use private pages will have to turn off the switch that hides private pages. Customers upgrading that have already private pages, will have the switch disabled. The switch should be disabled just for those sites including private pages.

Requirements

• RFF must be independent by site / instance, that is:

  • it can be ON for some sites, but not for all of them  (pending until RFF UI is improved) 

  • it can be ON for an instance, but not the rest  (pending until RFF UI is improved) 

  • it can be ON for an instance, but be switched OFF in any site of that instance  (pending until RFF UI is improved) 

• When the RFF is OFF, users will have the possibility of creating/selecting/viewing private pages as it was before  was merged

• When the RFF is ON, users won't be able to create/select/view private pages anywhere in the portal

• When the customer is upgrading, then the check will be automatically switched to "OFF" in all sites where there are already existing private pages   > for customers upgrading, the switch will be always OFF (the original requirement depends on the RFF UI improvements)

• When the RFF is OFF and private pages are created, and then it is switched ON so private pages are hidden, existing private pages won't be deleted, just hidden

Test Scenarios