Fixes #28735 Context Center Dashboard new UI

[Rohit0301]

Describe your changes:

Screen.Recording.2026-06-03.at.10.27.45.PM.mov

Fixes 28735

I worked on ... because ...

Type of change:

• Bug fix
• Improvement
• New feature
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation

High-level design:

N/A — small change.

Tests:

Use cases covered

Unit tests

Backend integration tests

Ingestion integration tests

Playwright (UI) tests

Manual testing performed

UI screen recording / screenshots:

Not applicable.

Checklist:

• I have read the CONTRIBUTING document.
• My PR title is Fixes <issue-number>: <short explanation>
• My PR is linked to a GitHub issue via Fixes #<issue-number> above.
• I have commented on my code, particularly in hard-to-understand areas.
• For JSON Schema changes: I updated the migration scripts or explained why it is not needed.
• For UI changes: I attached a screen recording and/or screenshots above.
• I have added tests (unit / integration / Playwright as applicable) and listed them above.

---

Summary by Gitar

• UI Components:
  • Added ContextKnowledgePillarCard, AiActivitySection, and NeedsAttentionSection to the ContextCenterDashboardPage for a revamped UI.
• Data Fetching Updates:
  • Integrated listFolders and getListContextMemories to power new dashboard stats.
  • Updated listContextFiles to support custom sorting/filtering and restricted data fetch limits using RECENT_DASHBOARD_ARTICLES_LIMIT and RECENT_DASHBOARD_DOCUMENTS_LIMIT.
• Localization:
  • Updated 19 language JSON files with new labels for AI activity, pillar stats, and status messaging.

_{This will update automatically on new commits.}

[github-actions]

Jest test Coverage

UI tests summary

Lines	Statements	Branches	Functions
	63.31% (67160/106076)	44.24% (36938/83478)	46.63% (11113/23831)

[github-actions]

🟡 Playwright Results — all passed (10 flaky)

✅ 4262 passed · ❌ 0 failed · 🟡 10 flaky · ⏭️ 88 skipped

Shard	Passed	Failed	Flaky	Skipped
✅ Shard 1	301	0	0	4
🟡 Shard 2	801	0	2	9
🟡 Shard 3	803	0	3	8
🟡 Shard 4	846	0	1	12
🟡 Shard 5	720	0	1	47
🟡 Shard 6	791	0	3	8

🟡 10 flaky test(s) (passed on retry)

• Features/DataQuality/ColumnLevelTests.spec.ts › Column Value Mean To Be Between (shard 2, 1 retry)
• Features/Glossary/GlossaryWorkflow.spec.ts › should start term as Draft when glossary has reviewers (shard 2, 1 retry)
• Features/RTL.spec.ts › Verify Following widget functionality (shard 3, 1 retry)
• Features/Tasks/TaskNavigation.spec.ts › navigating to /table/TASK-XXXXX should show 404 (invalid URL pattern) (shard 3, 1 retry)
• Flow/ExploreAggregationCountsMatching.spec.ts › should verify left panel counts and tab search results for normal search (shard 3, 1 retry)
• Pages/CustomProperties.spec.ts › Enum (shard 4, 1 retry)
• Pages/ExplorePageRightPanel_KnowledgeCenter.spec.ts › Should remove user owner for knowledgeCenter (shard 5, 1 retry)
• Pages/Lineage/LineageFilters.spec.ts › Verify lineage service type filter selection (shard 6, 1 retry)
• Pages/Lineage/LineageFilters.spec.ts › Verify lineage schema filter selection (shard 6, 1 retry)
• Pages/ServiceEntity.spec.ts › Tier Add, Update and Remove (shard 6, 1 retry)

📦 Download artifacts

How to debug locally

# Download playwright-test-results-<shard> artifact and unzip
npx playwright show-trace path/to/trace.zip    # view trace

[chirag-madlani]

Paging should always be there, can you confirm if response.data.data is correct?
Usually we have response.data & response.paging

[Rohit0301]

fixed

[Rohit0301]

this is correct response.data.data

[gitar-bot]

Code Review ✅ Approved 6 resolved / 6 findings

Implements the Context Center Dashboard revamp with new UI components and updated data fetching logic. Resolved issues regarding data count capping, type safety for API parameters, and redundant mapping operations.

✅ 6 resolved

✅ Bug: Article/document stats show capped count instead of total

📄 openmetadata-ui/src/main/resources/ui/src/pages/ContextCenterPage/ContextCenterDashboardPage/ContextCenterDashboardPage.tsx:327 📄 openmetadata-ui/src/main/resources/ui/src/pages/ContextCenterPage/ContextCenterDashboardPage/ContextCenterDashboardPage.tsx:344
The stat prop for both the articles and documents pillar cards uses articles.length and documents.length respectively. Since RECENT_DASHBOARD_ARTICLES_LIMIT and RECENT_DASHBOARD_DOCUMENTS_LIMIT are both 3, the displayed count will always be at most "3" regardless of how many articles/documents actually exist.

The API (getListKnowledgePages) returns response.paging.total which gives the true total count. The same applies to listContextFiles. You should store and display the total from the paging response rather than the length of the fetched slice.

✅ Quality: Use typed interface instead of object for listContextFiles params

📄 openmetadata-ui/src/main/resources/ui/src/rest/assetAPI.ts:54
The params parameter in listContextFiles is typed as object, which provides no type safety and allows passing arbitrary properties. Since the API accepts specific sort parameters, a typed interface would be more appropriate and consistent with the codebase patterns (e.g., ListAssetsByFqnParams already exists in the same file).

✅ Quality: Redundant .map((page) => page) is a no-op

📄 openmetadata-ui/src/main/resources/ui/src/pages/ContextCenterPage/ContextCenterDashboardPage/ContextCenterDashboardPage.tsx:149
The expression response.data.map((page: KnowledgePage) => page) creates a new array where each element maps to itself, which is functionally identical to just using the array directly (or spreading it if immutability is the concern).

✅ Quality: Hardcoded strings "0 this week", "0 processing", "0 cites today"

📄 openmetadata-ui/src/main/resources/ui/src/pages/ContextCenterPage/ContextCenterDashboardPage/ContextCenterDashboardPage.tsx:332 📄 openmetadata-ui/src/main/resources/ui/src/pages/ContextCenterPage/ContextCenterDashboardPage/ContextCenterDashboardPage.tsx:349 📄 openmetadata-ui/src/main/resources/ui/src/pages/ContextCenterPage/ContextCenterDashboardPage/ContextCenterDashboardPage.tsx:365
The trend prop values passed to ContextKnowledgePillarCard are hardcoded English strings ("0 this week", "0 processing", "0 cites today") rather than using the useTranslation hook. This violates the i18n requirement and will not be translated for other locales.

✅ Edge Case: Removed null guard on listContextFiles data can crash .map

📄 openmetadata-ui/src/main/resources/ui/src/rest/assetAPI.ts:54-61 📄 openmetadata-ui/src/main/resources/ui/src/pages/ContextCenterPage/ContextCenterDashboardPage/ContextCenterDashboardPage.tsx:166-167
The old listContextFiles returned data: response.data.data ?? [], defensively defaulting to an empty array when the API omitted data. The refactored version returns response.data (a PagingResponse<ContextFile[]>) directly without any guard. Although the type declares data as required, at runtime an empty/204 or malformed response could leave data undefined, and the caller's response.data.map(contextFileToUploadedDocumentItem) (and response.data.length) at ContextCenterDashboardPage.tsx:166-167 would throw Cannot read properties of undefined. Consider defaulting data to [] either in the API helper or at the call site.

...and 1 more resolved from earlier reviews

Options

Display: compact → Showing less information.

Comment with these commands to change:

Compact

gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}

[sonarqubecloud]

Quality Gate passed for 'open-metadata-ui'

Issues
1438 New issues
0 Accepted issues

Measures
25 Security Hotspots
0.0% Coverage on New Code
3.5% Duplication on New Code

See analysis details on SonarQube Cloud