TCF Experience option for selecting a restriction configuration

[gilluminate]

Closes LJ-623

Description Of Changes

This PR adds support for selecting TCF (Transparency & Consent Framework) Publisher Override configurations when configuring Privacy Experiences. It includes UI changes to allow users to select and manage TCF configurations within the privacy experience settings.

Code Changes

• Added TCF configuration selection dropdown in Privacy Experience form
• Added handling for clearing TCF configuration (sets to null when cleared)
• Added new Cypress test for TCF configuration editing functionality

Steps to Confirm

1. When running locally, make sure you have latest from fidesplus repo main branch and that TCF is enabled.
2. Navigate to the consent settings page in the Admin UI (/settings/consent)
3. Enable the Override vendor purposes option.
4. Create a new configuration
   • Click the "Create configuration +" button
   • Give your config a name and save it. (you should see the table appear below)
   • Add another
5. Navigate to a TCF privacy experience configuration
6. Verify the TCF Configuration dropdown is visible and populated with available configurations
7. Select a different TCF configuration and save - verify it updates successfully
8. Clear the TCF configuration and save - verify it clears successfully
9. Verify the dropdown is disabled if either:
   • Override vendor purposes setting is disabled in consent settings
   • No TCF configurations exist

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
• 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 Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
fides-plus-nightly	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 14, 2025 9:16pm
fides-privacy-center	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 14, 2025 9:16pm

[gilluminate]

I accidentally added this to the wrong release this morning, so just moving it to the correct spot here

[gilluminate]

Updates just for you @jpople ;)

[jpople]

Tested locally, everything working as expected for me.

[cypress]

fides    Run #12816

Run Properties:   Passed #12816  •  1716101ff6: TCF Experience option for selecting a restriction configuration (#6033)

Project	fides
Branch Review	main
Run status	Passed #12816
Run duration	00m 52s
Commit	1716101ff6: TCF Experience option for selecting a restriction configuration (#6033)
Committer	Jason Gill
View all properties for this run ↗︎

---

Test results
Failures	0
Flaky	0
Pending	0
Skipped	0
Passing	5
View all changes introduced in this branch ↗︎