Remove /add-systems config wizard page

[adamsachs]

Ticket ENG-3404

Description Of Changes

Removes the unused config wizard page at /add-systems along with its AWS scanner and Okta scanner sub-steps. The wizard's only entry point was navigation that pointed to itself; single-system creation remains available via /add-systems/manual and the inline AddNewSystemModal, and bulk vendor add remains at /add-systems/multiple.

Screenshot showing page no longer present:

Code Changes

• Deleted pages/add-systems/index.tsx
• Deleted features/config-wizard/ (AddSystem, AuthenticateAwsForm, AuthenticateOktaForm, AuthenticateScanner, ConfigWizardWalkthrough, ScanResults, ScannerLoading, OrganizationInfoForm, slices, helpers, types)
• Deleted Cypress specs config-wizard.cy.ts and config-wizard-plus.cy.ts
• Removed ADD_SYSTEMS_ROUTE constant, the "Add systems" sidebar nav entry, and the "Add systems" home module card
• Removed configWizardSlice registration from app/store.ts
• Dropped the now-dead parent breadcrumb link on /add-systems/manual and /add-systems/multiple
• Repointed the empty-datamap GetStarted button at /add-systems/multiple
• Updated jest specs (nav-config.test.ts, tile-config.test.ts) to match the new nav/tile shape
• Updated cypress specs (routes.cy.ts, systems.cy.ts, bulk-vendor-add.cy.ts, root-user-access.cy.ts) to drop wizard-dependent setup steps

Steps to Confirm

1. Visit /add-systems — should 404
2. Visit /add-systems/manual — single-system creation form still loads, breadcrumb shows "Add systems / New system" with "Add systems" no longer a link
3. Visit /add-systems/multiple — bulk vendor add still loads, breadcrumb shows "Add systems / Choose vendors" with "Add systems" no longer a link
4. On /systems, click the "Add system" / "Add new system" button — still routes to /add-systems/manual (or shows the Compass-enabled dropdown with manual + multiple options)
5. Home dashboard no longer shows an "Add systems" module card
6. "Data inventory" sidebar group no longer contains "Add systems"
7. Empty-datamap Get Started modal still has a working "Add Systems" button (now goes to /add-systems/multiple)

Pre-Merge Checklist

• Issue requirements met
• All CI pipelines succeeded
• CHANGELOG.md updated
  • Add a db-migration This indicates that a change includes a database migration label to the entry if your change includes a DB migration
  • Add a high-risk This issue suggests changes that have a high-probability of breaking existing code label to the entry if your change includes a high-risk change (i.e. potential for performance impact or unexpected regression) that should be flagged
  • Updates unreleased work already in Changelog, no new entry necessary
• UX feedback:
  • All UX related changes have been reviewed by a designer
  • No UX review needed
• Followup issues:
  • Followup issues created
  • No followup issues
• Database migrations:
  • Ensure that your downrev is up to date with the latest revision on main
  • Ensure that your downgrade() migration is correct and works
    • If a downgrade migration is not possible for this change, please call this out in the PR description!
  • No migrations
• Documentation:
  • Documentation complete, PR opened in fidesdocs
  • Documentation issue created in fidesdocs
  • If there are any new client scopes created as part of the pull request, remember to update public-facing documentation that references our scope registry
  • No documentation updates required

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
fides-plus-nightly	Ready	Preview, Comment	May 25, 2026 2:44pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
fides-privacy-center	Ignored		May 25, 2026 2:44pm

[github-actions]

Title	Lines	Statements	Branches	Functions
admin-ui		8.59% (4049/47125)	7.62% (2094/27480)	5.86% (813/13867)
fides-js		79.17% (1977/2497)	66.25% (1249/1885)	73.31% (349/476)
privacy-center		86.59% (517/597)	82.33% (247/300)	81.08% (90/111)

[lucanovera]

Hi @adamsachs !
Just reviewed this PR and it's approved on my end. I've already moved all your changes to the chore/remove-add-systems-wizard-page branch in fidesplus, but you'll need to create the PR again or I won't be able to approve.
I've added two additional changes (feel free to disagree/revert):

1. I didn't like leaving that 404 page if you go to /add-systems, given /add-systems/manual is a real url. I prefer if all paths work kind of like a breadcrumb. My quick fix was to add a client-side redirect from /add-systems to /systems.

The more proper solution is to rewrite the add urls to be /systems/add-manual and /systems/add-multiple but that requires changing many files, unit and cypress tests. We can leave that to a followup.

2. While testing the empty datamap I was getting some 500 errors. I had Claude look into in and push this one line fix:

You're hitting the datamap export endpoint (export_datamap). It walks every field of every dataset in your local DB via get_all_level_fields. For dict-form fields it does a hard field["fields"] lookup, but a leaf field with no nested sub-fields omits the "fields" key entirely → KeyError: 'fields' → unhandled 500. The sibling branch for Pydantic objects (field.fields) doesn't crash because the attribute defaults to None; the dict branch just wasn't written defensively.

This is a pre-existing core-fides bug, not from the branch ports (those only touched clients/). It's data-dependent — triggered by whatever dataset is in your seeded/local DB.

The fix is a one-liner that makes the dict branch match the safe semantics of the object branch.
              if field["fields"]: -> if field.get("fields"):

[adamsachs]

Hi @adamsachs ! Just reviewed this PR and it's approved on my end. I've already moved all your changes to the chore/remove-add-systems-wizard-page branch in fidesplus, but you'll need to create the PR again or I won't be able to approve. I've added two additional changes (feel free to disagree/revert):

1. I didn't like leaving that 404 page if you go to /add-systems, given /add-systems/manual is a real url. I prefer if all paths work kind of like a breadcrumb. My quick fix was to add a client-side redirect from /add-systems to /systems.

The more proper solution is to rewrite the add urls to be /systems/add-manual and /systems/add-multiple but that requires changing many files, unit and cypress tests. We can leave that to a followup.

2. While testing the empty datamap I was getting some 500 errors. I had Claude look into in and push this one line fix:

You're hitting the datamap export endpoint (export_datamap). It walks every field of every dataset in your local DB via get_all_level_fields. For dict-form fields it does a hard field["fields"] lookup, but a leaf field with no nested sub-fields omits the "fields" key entirely → KeyError: 'fields' → unhandled 500. The sibling branch for Pydantic objects (field.fields) doesn't crash because the attribute defaults to None; the dict branch just wasn't written defensively.

This is a pre-existing core-fides bug, not from the branch ports (those only touched clients/). It's data-dependent — triggered by whatever dataset is in your seeded/local DB.

The fix is a one-liner that makes the dict branch match the safe semantics of the object branch.
              if field["fields"]: -> if field.get("fields"):

thank you so much for this @lucanovera ! opened up over in https://github.com/ethyca/fidesplus/pull/3708 if you don't mind approving 🙏