BC Observatoryunofficial, made by waldo
code change · featureAL Developmentofficial - Microsoftreviewed - checked by Opus

#214 UI knowledge: notification recall needs a known Id; open mixed-type documents through Page Management

Two new UI design guidance articles added to help developers properly manage notifications by using known IDs for recall and handle multi-document routing through Page Management instead of hard-coded mappings.

Open in Claude214.mdPull request #214

Pull request · merged into main on 2026-10-06 by MichaelDieringer · 8 files (+365 -7), 7 AL · feature · tier official · reviewed (checked by Opus)

What changed

  • Notification recall requires a fixed GUID ID set before sending; without it, later recall calls fail to dismiss notifications.
  • Use codeunit 1511 Notification Lifecycle Management to track and recall notifications for specific records when multiple records are visible.
  • Avoid duplicating Page Management routing logic with hand-written case statements; use Page Management events for new tables instead.
  • Two good/bad code examples provided covering notification lifecycle and document routing patterns.
  • Guidance includes documented Learn references and specific Base App examples showing correct implementation.

AL objects touched

  • microsoft/knowledge/ui/list-page-document-routing-uses-page-management.bad.al: added, not in the BC? snapshot yet
  • microsoft/knowledge/ui/list-page-document-routing-uses-page-management.good.al: added, not in the BC? snapshot yet
  • microsoft/knowledge/ui/list-page-document-routing-uses-page-management.md: added, not in the BC? snapshot yet
  • microsoft/knowledge/ui/notification-recall-needs-known-id.bad.al: added, not in the BC? snapshot yet
  • microsoft/knowledge/ui/notification-recall-needs-known-id.good.al: added, not in the BC? snapshot yet
  • microsoft/knowledge/ui/notification-recall-needs-known-id.md: added, not in the BC? snapshot yet
  • microsoft/skills/review/al-ui-review.md: modified, not in the BC? snapshot

Context

  • Systems: development, administration

Source: metadata of a merged pull request in microsoft/BCQuality (bcquality): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).