Michael Dieringer 750466c7f3 Add UI knowledge: notification recall Id and Page Management document routing ... Two ui articles with compiled good/bad samples: - notification-recall-needs-known-id: a notification that the code also recalls needs a fixed Id (single instance; recall before re-send) or per-record tracking through codeunit "Notification Lifecycle Mgt." (SendNotification[WithAdditionalContext] / RecallNotificationsForRecord, HandleDelayedInsert semantics). Never-recalled notifications are exempt. - list-page-document-routing-uses-page-management: open documents from a mixed-type list with PageManagement.PageRun(Rec) instead of a hand-written case "Document Type" / Page.Run; register new tables through OnConditionalCardPageIDNotFound. Single-type opens and tables Page Management does not route are exempt. Wired into al-ui-review (entry gate now covers notification send/recall outside pages, tokens, high-signal mappings) and registered both pairs in the ui review-fixtures override. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>		2026-10-03 12:47:57 +02:00
..
review	Add UI knowledge: notification recall Id and Page Management document routing	2026-10-03 12:47:57 +02:00
.gitkeep	Add initial project structure with .gitignore, LICENSE, README, and CODEOWNERS	2026-04-17 05:56:10 +02:00