Documentation Center

Migrating custom Dashboard screens

If you added custom screens to the Dashboard, you must recreate these screens in the new user interface, because the Dashboard no longer exists as of SDL Tridion 2013 SP1.

About this task

In the past, you added a Dashboard screen to the Content Manager Explorer Dashboard or to the Experience Manager Dashboard by creating the screen as an ASCX control and configuring it in the configuration file of your custom Editor. Because the Dashboard no longer exists, you must remove your ASCX control from the configuration file(s).

In the new SDL Tridion user interfaces, you can recreate the screen in several ways:
  • You can recreate the Dashboard screen as a Custom Page.
  • If the Dashboard screen occupies a small amount of screen real estate, you can recreate the Dashboard screen in an extensible area of the Home screen in the slide-out navigation.
  • If the Dashboard screen occupies a large amount of screen real estate, you can recreate the Dashboard screen as a standalone Web page, and specify a link to that page in the extensible area of the Home screen.

Procedure

  1. On the Content Manager server, navigate to the location of the configuration file of a custom Editor to which you added one or more custom Dashboard screens.
  2. Open this configuration file for editing.
  3. Find an <ext:extension> section that has a child element <ext:pageurl> with its value set to a custom .ascx resource that represents a custom Dashboard screen.
  4. Note down the name and location of the .ascx file.
  5. Remove the <ext:extension> section.
  6. Repeat these steps for all <ext:extension> sections that refer to custom Dashboard screens.
  7. Also check for <ext:extension> sections that have a child element <ext:type> set to the value Separator, and remove these sections as well.
  8. Repeat all these steps for any other custom Editors you might have for which you have configured custom Dashboard screens.
    You have now collected one or more .ascx files (ASP.NET Web User Controls).
  9. Use the contents of your .ascx file(s) when you recreate each of them as a Custom Page, Home screen area or standalone Web page.