code change · featureAL Developmentofficial - Microsoftreviewed - checked by Opus

#8556 [Quality Management] Enforce rules and restrictions with indirect and implicit permissions

Quality Management uses InherentPermissions so that, when no setup or triggered generation rule exists, users need no QM permissions. When a rule does trigger, users without QM permissions get a standard permission error instead of silently skipping inspection creation. A new 'QltyMgmt - I. Create' permission set grants the minimum indirect rights.

Pull request · merged into main (BC30) on 2026-07-08 by JakovljevicDusan · 31 files (+373 -103), 29 AL · feature · tier official · reviewed (checked by Opus)

What changed

  • InherentPermissions used for the setup and generation rule tables so users without QM permissions are not blocked when nothing triggers
  • When a generation rule triggers, users without QM permissions now get a standard permission error instead of a silent skip
  • New permission set ‘QltyMgmt - I. Create’ grants indirect permissions to create inspections, including via Create Quality Inspection actions
  • Users with only that permission set cannot view or process inspections; View actions are hidden via AccessByPermission
  • Behaviour changes for users or extensions.

AL objects touched

Context

  • Work items: AB#626330
  • Labels: AL: Apps (W1), Team: SCM
  • Systems: development, integration, platform
  • From the description: “Implement InherentPermissions so users without QM permissions would not silently skip mandatory Quality Inspection creation or transaction restrictions.”

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