LJ-458-FE-Consent-reporting-page-initial-UI

[lucanovera]

Description Of Changes

Implement consent reporting table and consent record lookup modal.

Code Changes

• Add table to consent reporting page
• Replace double date input with ant's range picker
• Include dayjs library
• Add new endpoints to consent reporting slice
• Add modal to lookup current privacy preferences

Screenshots

Steps to Confirm

1. Login to admin ui
2. Go to Consent > Consent Reporting (if the option isn't there, enable Consent Reporting in Settings > About Fides)
3. Check consent records are being displayed in a table
4. Check modifying the date range updates the results in the table
5. Check download button opens a modal and button to download report works
6. In a new tab, use demo page to open a consent modal and save new preferences (http://localhost:3001/fides-js-demo.html?geolocation=us-ca or http://localhost:3001/fides-js-demo.html?geolocation=eea)
7. Back in consent reporting, click the Refresh button
8. Check the new consent record appeared in the table and a success toast is shown
9. Look at the table for a record that isn't TCF, copy the User device ID
10. Open the dropdown (three dots in the top right corner of the table) and select 'Consent preference lookup'
11. Paste the device id in the search bar and hit search
12. Check the results are shown in the table below

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 (include link)
  • 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-privacy-center	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 7, 2025 8:09pm

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
fides-plus-nightly	⬜️ Ignored (Inspect)	Visit Preview		Mar 7, 2025 8:09pm

[gilluminate]

Testing looks good, but when I have used the pagination and click refresh, I was expecting that to take me back to the first page. Maybe that's by design that it doesn't, but especially in the case of looking for new entries I found it a little disorienting that it didn't.

[gilluminate]

Not for this PR, but I would love to see us update the filenames in this directory to take a more standard approach (eg. date-range.d.ts)

[gilluminate]

Looking good! Great work

[gilluminate]

Isn't this getting cherry-picked to 2.56.2?

[lucanovera]

I'm asking adam about it, if I can make that patch release, I'll move the changelog. Thanks for the attention to details!

[cypress]

fides    Run #12642

Run Properties:   Passed #12642  •  7f21d2ede2: LJ-458-FE-Consent-reporting-page-initial-UI (#5839)

Project	fides
Branch Review	main
Run status	Passed #12642
Run duration	00m 49s
Commit	7f21d2ede2: LJ-458-FE-Consent-reporting-page-initial-UI (#5839)
Committer	Lucano Vera
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 ↗︎