DSS Upgrade Checklist


  • Make sure to test the following after upgrading a DSS site:
  • Calendars
  • A-Z index pages
  • Media (flash, video players, any other embedded media)
  • Navigations
  • Links in body copy
  • Print-friendly page functionality
  • PDF generation:
    • If integrated into the site, ensure pages can be saved and generated as PDFs.
  • Forms:
    • Can they be filled out?
    • Submitted without error?
    • Receipt of appropriate emails with correct content
  • Custom apps, including calculators, Cartella, and third-party applications
  • Site rendering:
    • Test least one of each page type, but ideally more.
    • Review site for navigation accuracy. Ensure that relevant navigations appear. 
    • Check site tree redirect components (often called virtual links).
    • Evaluate speed and responsiveness.
  • External Content, if applicable. This includes static HTML and third-party items.
  • Search
  • Structured URLs:
    • Feature must be turn on in CMS 8.0.
    • Make sure Publish As works.
    • Ensure the live site works and that all CSS renders, even on multiple levels of sub-pages
    • File a report to Ingeniux support if broken links or xIDs remain after following these steps.
  • Ingeniux Redirects:
    • Check a variety of the redirects defined in your CMS to ensure they still work as expected.
  • ACLs:
    • For sites that use Windows-based or basic authentication for live-site content protection, this functionality should be migrated to Run-Time Authentication (RTA). Contact Ingeniux support.
  • Run-Time Authentication (RTA):
    • While not logged in, attempt to navigate to a protected page and confirm that you are redirected to the login page.
    • Test invalid credentials: both invalid usernames and invalid passwords
    • Test a variety of users who have access to different items.
    • Ensure that users can log out.
  • Alert Module:
    • Submit or enable an alert, and note how long it takes to appear. 
  • Caching:
    • If DSS caching is activated, confirm that the the cache expires at publish.