Parent
Parent: #1690
Workbench inventory P1 (AS-07). Filter create/save/delete already ships on origin/main. Remaining: operators can write rule rows in Developer chrome (today the rules table is read-only and Save only round-trips loaded rules).
Slice goal
One user-visible increment: An Admin can add, edit, and remove item-filter rules (name + params) on Developer → Item Filters detail, persist via existing Admin PUT /services/itemfilters/{idOrName} (rules[]), see the catalog GET round-trip, and follow product-docs.
HARD BAN: do not split REST vs SPA vs Playwright. Do not invent a new SOAP surface. Do not stack with #4434 product-docs XSL (different parent; avoid admin/index.md thrash if that PR is open — prefer in-page links).
In scope
- SPA: rule editor on
ItemFilterDetailPanel (add/edit/remove rows; params name/value). Create may send rules[]; PUT omitted rules stays unchanged; rules: [] clears.
- REST/adaptor only if the existing PUT contract is insufficient (unit tests on exact production types). Prefer using shipped
ItemFilter.rules.
- Surface-filtered Playwright (QA H2:
perc-devctl qa-up → qa-health → TEST_CMS_URL → npm run test:surface path/grep/tag → qa-down). Do not HTTP-poll /Rhythmyx/login after a failed Jetty start.
- Update
product-docs/8.2/admin/developer-item-filters.md and product-docs/8.2/developer/rest.md Item filters section. Keep frontmatter id: stable.
Out of scope
- Shared field nested field editor (slice 2)
- System-def control properties (slice 3)
- Pipeline graph editor / mapper persist
- 100% classic Workbench visual metaphor
Acceptance
Modules
rest (only if contract gap), projects/sitemanage (only if adaptor gap), WebUI, modules/perc-qa-automation, product-docs/8.2/
Leave unassigned. Do not add In Progress.
Co-Authored by Grok Build 1.0.24 using grok-4.6 with agent night-issue-prs-triage.
Parent
Parent: #1690
Workbench inventory P1 (AS-07). Filter create/save/delete already ships on
origin/main. Remaining: operators can write rule rows in Developer chrome (today the rules table is read-only and Save only round-trips loaded rules).Slice goal
One user-visible increment: An Admin can add, edit, and remove item-filter rules (name + params) on Developer → Item Filters detail, persist via existing Admin
PUT /services/itemfilters/{idOrName}(rules[]), see the catalog GET round-trip, and follow product-docs.HARD BAN: do not split REST vs SPA vs Playwright. Do not invent a new SOAP surface. Do not stack with #4434 product-docs XSL (different parent; avoid
admin/index.mdthrash if that PR is open — prefer in-page links).In scope
ItemFilterDetailPanel(add/edit/remove rows; paramsname/value). Create may sendrules[]; PUT omittedrulesstays unchanged;rules: []clears.ItemFilter.rules.perc-devctl qa-up→qa-health→TEST_CMS_URL→npm run test:surfacepath/grep/tag →qa-down). Do not HTTP-poll/Rhythmyx/loginafter a failed Jetty start.product-docs/8.2/admin/developer-item-filters.mdandproduct-docs/8.2/developer/rest.mdItem filters section. Keep frontmatterid:stable.Out of scope
Acceptance
rules: []or UIModules
rest(only if contract gap),projects/sitemanage(only if adaptor gap),WebUI,modules/perc-qa-automation,product-docs/8.2/Leave unassigned. Do not add In Progress.