Require integration name when adding from system form

[Kelsey-Ethyca]

Ticket ENG-3699

Description Of Changes

Previously, when a user added an integration from a system's Integrations tab (/systems/configure/[id] → Integrations), the form did not collect a name. The name field was rendered as a hidden Form.Item and was explicitly omitted from the create payloads. As a result, those integrations were saved without a name and showed up as "(No name)" on the standalone Integrations list.

This change makes the Name field visible and required in the system-form integration form, matching the standalone "Add Integration" flow. It also pre-fills the field with the connection key when editing an existing nameless integration, so users with pre-existing "(No name)" integrations can keep their current key as the name (or rename it) without being blocked from saving / testing / authorizing.

Code Changes

• clients/admin-ui/src/features/datastore-connections/system_portal_config/forms/ConnectorParametersForm.tsx:
  • Replaced the hidden name Form.Item with a visible field using rules={[{ required: true, message: "Name is required" }]} (matches the styling/validation of the standalone form).
  • In initialFormValues, fall back to connectionConfig.key when connectionConfig.name is null/empty so existing nameless integrations get a sensible default in the field.
• clients/admin-ui/src/features/datastore-connections/system_portal_config/forms/ConnectorParameters.tsx:
  • Dropped the Omit<..., "name"> typing on both create payloads (createSaasConnector and patchConnectionConfig) and added name: values.name so the user-entered name is sent to the backend.

Steps to Confirm

1. Navigate to Systems → pick any system → Integrations tab → choose an integration type to add.
2. Confirm a Name field is now visible at the top of the form, marked required.
3. Try to save without filling it in — confirm the form blocks submission with "Name is required".
4. Fill in a name, save, and navigate to the Integrations page. Confirm the new integration appears with the name you provided (not "(No name)").
5. For an existing integration that previously had no name (e.g., one created before this change), open it from the system form. Confirm the Name field is pre-populated with the integration's key. Save the form (no other changes) and confirm it now displays its key as the name on the Integrations page.
6. Smoke-test the standalone "Add Integration" flow on /integrations to confirm it still works as before.

Pre-Merge Checklist

• Issue requirements met
• All CI pipelines succeeded
• CHANGELOG.md updated
  • Add a db-migration label to the entry if your change includes a DB migration
  • Add a high-risk label to the entry if your change includes a high-risk change
  • 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

[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 3, 2026 2:46pm

1 Skipped Deployment

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

[github-actions]

Title	Lines	Statements	Branches	Functions
admin-ui		6.28% (2830/44999)	5.53% (1427/25759)	4.42% (588/13285)
fides-js		79.39% (2011/2533)	65.99% (1240/1879)	73.09% (345/472)
privacy-center		85.97% (331/385)	81.36% (179/220)	78.87% (56/71)