Retire a homepage
Use the homepage migration status table to retire homepages. When you retire a homepage, you remove visibility and editing options from all but the admin.
Before you begin
Role required: admin or dashboard_admin.
- Disable the creation of new homepages: Set the system property com.glideapp.home.deprecate_homepages to true.Important:When set to true, this property disables the creation of new homepages and sets the default start page or landing page to Dashboards. Menu items and URLs that open homepages will continue to point to those homepages. Otherwise, homepages are unavailable and should be migrated using this tool.
- Populate the homepage migration status table.
Note:
When you retire a homepage, users can no longer select the associated portal pages and only the admin has read and write permissions on the pages.
To configure the time limit to respond to a retirement request, edit the system property sn_home_page_depr.approval_due_date.
Procedure
-
From the Actions on selected rows menu, select
Retire.
- If the homepage is a Global homepage, meaning one with no specified owner, it is retired and the task state is set to Closed complete immediately.
- If there is no response from the owner of a personal homepage within the time limit, the homepage is retired and the task state is set to Closed complete.
- If the owner rejects the retirement request, the homepage is converted to a dashboard.
Result
- Entries in the State column for the converted homepages are changed to Closed complete.
- Entries in the Decision column for retired homepages are changed to Retired.
- Entries in the Decision column for homepages the owner rejects for retirement are changed to Converted.
- Personal homepages of users who are inactive or locked out no longer appear on the Personal homepages tab of the Homepage deprecation dashboard.
- Read and write permissions for retired homepages are limited to admin.