Run 2026-04-27 (8)

Focus: deepen DB-backed understanding of service categories (AccProductGroup) and how category hierarchy changes propagate to IT Shop product nodes (ShoppingRack), plus reconcile MDK ITShopInfo code hints (BG/BT) with live DB reality.

What I did

Live sandbox DB (SELECT-only):
Inspected AccProductGroupCollection (closure table) and QER_VACCProductGroupCollection (category-to-ancestor mapping view).
Pulled trigger definitions for QER_TUAccProduct and QER_TUAccProductGroup to confirm which DBQueue tasks fire when products/categories change.
Confirmed BaseTree has 0 rows with ITShopInfo IN ('BG','BT') in this sandbox.
Listed DBQueue task definitions related to ShoppingRack and category collection (dbo.QBMDBQueueTask).
Sandbox host (WinRM, read-only):
Searched installed product media (C:\Dev\OneIdentityManager.10.0\Modules\QER\database, ...\ADS\database) for AccProductInBaseTree, AccProductGroupCollection, and IsToHideFromITShop references.
Searched MDK (C:\Dev\OneIM10.0.0-MDK\MDK) for ITShopInfo/BG/BT references; found them in MMM module procedures.
Vendor docs (official PDF):
Noted the official 10.0 IT Shop Administration Guide PDF as the primary reference for concepts and configuration parameters.

Key findings (sandbox-specific)

Service category hierarchy has an explicit DB-backed “closure”:
AccProductGroupCollection stores Parent↔Child relations (incl. self rows) with LevelNumber.
QER_VACCProductGroupCollection provides category-to-ancestor mapping with CountSteps.
Category changes are wired into ShoppingRack refresh:
QER_TUAccProduct enqueues QER-K-ShoppingRackProductNode on AccProduct.UID_AccProductGroup changes.
QER_TUAccProductGroup enqueues QER-K-AccProductGroupCollection and may enqueue QER-K-ShoppingRackProductNode depending on which category columns change.
ITShopInfo BG/BT codes exist in MDK MMM procedures, but are not present in the live sandbox BaseTree rows; treat as module-specific (MMM) and not relevant for QER IT Shop behavior here.
AccProductInBaseTree and IsToHideFromITShop are shipped schema elements, but in this sandbox the primary IT Shop placement logic appears to use BaseTree + BaseTreeHas<type> tables rather than populating AccProductInBaseTree.

Evidence

Live DB evidence updates:
projects/identity-management/oim-kb-update/sandbox-db/2026-04-27-itshop-availability-db-evidence.md (added sections 12–13)
Sandbox host evidence updates:
projects/identity-management/oim-kb-update/sandbox-host/2026-04-27-itshop-file-hints.md (addendum run 8)

Vendor docs

One Identity Manager 10.0 IT Shop Administration Guide (PDF): https://support-public.cfm.quest.com/82111_one-identity-manager_it-shop-administration_10.0.pdf (Accessed: 2026-04-27)

Open questions / next experiments

Confirm the *supported path* for auto-publishing ADS groups into the IT Shop in this sandbox:
enable QER\ITShop\AutoPublish\ADSGroup,
sync seeded AD groups into ADSGroup,
observe ADSGroup.UID_AccProduct creation, PR node creation, and BaseTreeHasADSGroup placement under UID_OrgRoot='QER-V-ITShopOrg'.
Determine whether AccProduct.IsToHideFromITShop affects Web Portal listing/search only, or also influences PR node creation/visibility (likely needs a controlled UI/API test).