[Permissions] Add Where-Used and Permissions Overview navigation actions#8947
Conversation
Add navigation actions to open the Permissions Overview page (with optional filters) from multiple pages: - Permission Sets list: Where-Used (filtered) + Permissions Overview - Permission Set card: Where-Used (filtered) - Table Information: View Table Permissions (filtered to table) - Page Inspection: View Table Permissions link (filtered to table) System Application changes: - New Permissions Overview codeunit (9865) with integration events - Where-Used action on Permission Set card - View Table Permissions action on Table Information page - Permission Sets dependency added to Table Information module BaseApp changes: - Permissions Overview page: setter procedures + ApplyInitialFilters - Permission Sets list page: Where-Used + Permissions Overview actions - New Permissions Overview Handler codeunit (9886) event subscriber - Page Inspection: View table permissions drilldown link Work Item: AB#626501 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot PR ReviewIteration 2 · Outcome: completed Knowledge source: https://github.com/microsoft/BCQuality@822cae1b2771ac25f665f73369f69093bd4fd630 Orchestrator pre-filter (13 file(s) excluded)
Findings produced by the Copilot CLI agent against BCQuality at |
|
gggdttt
left a comment
gggdttt
left a comment
There was a problem hiding this comment.
Can we add some tests for this new action? It should be testable right?
…-permissions-overview-v2
|
@copilot Pull latest main into the PR. |
…nushar/626501-permissions-overview-v2
Merged the latest |
Summary
Implements AB#626501 - Broader usage of the Permissions Overview page.
Adds navigation actions to open the Permissions Overview page (with optional filters) from:
System Application changes
BaseApp changes
Design
Uses integration events so BaseApp can subscribe and handle the actual page navigation, since the Permissions Overview page lives in BaseApp and System Application cannot reference it directly.