---
id: change/bcquality/214
type: change
title: "#214 UI knowledge: notification recall needs a known Id; open mixed-type documents through Page Management"
summary: 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.
tier: official
language: en
tags:
  - feature
  - main
system: development
review:
  state: reviewed
  by: opus
  at: "2026-10-08T02:02:06.528Z"
  flags: []
generated:
  at: "2026-10-08T01:26:53.141Z"
  pipeline: 0.2.0
  prompts:
    extract-change: 1
  input_hash: 86d809b5252aa2fe187ccb9f16bef435bb8c9be6
evidence:
  - kind: code
    url: https://github.com/microsoft/BCQuality/pull/214
    title: "microsoft/BCQuality#214: UI knowledge: notification recall needs a known Id; open mixed-type documents through Page Management"
    date: "2026-10-06"
    commit: 86d809b5252aa2fe187ccb9f16bef435bb8c9be6
    t: null
    quote: null
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
  changes: []
number: 214
repo: microsoft/BCQuality
source_id: bcquality-prs
url: https://github.com/microsoft/BCQuality/pull/214
kind: pr
base_branch: main
major: null
merged_at: "2026-10-06T11:31:00Z"
author: MichaelDieringer
author_type: User
community_contribution: false
labels: []
change_class: code
change_kind: feature
behavior_change: false
breaking: false
files:
  count: 8
  additions: 365
  deletions: 7
  al: 7
apps: []
objects_touched: []
objects_unjoined:
  - path: microsoft/knowledge/ui/list-page-document-routing-uses-page-management.bad.al
    status: added
    reason: not-in-snapshot
  - path: microsoft/knowledge/ui/list-page-document-routing-uses-page-management.good.al
    status: added
    reason: not-in-snapshot
  - path: microsoft/knowledge/ui/list-page-document-routing-uses-page-management.md
    status: added
    reason: not-in-snapshot
  - path: microsoft/knowledge/ui/notification-recall-needs-known-id.bad.al
    status: added
    reason: not-in-snapshot
  - path: microsoft/knowledge/ui/notification-recall-needs-known-id.good.al
    status: added
    reason: not-in-snapshot
  - path: microsoft/knowledge/ui/notification-recall-needs-known-id.md
    status: added
    reason: not-in-snapshot
  - path: microsoft/skills/review/al-ui-review.md
    status: modified
    reason: not-in-snapshot
obsoletions: []
backports: []
fixes_issues: []
work_items: []
systems:
  - development
  - administration
quote: null
joined_against:
  major: null
  commit: null
---

# #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.

[Pull request](https://github.com/microsoft/BCQuality/pull/214) · 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).