Skip to content

@W-24087851 Correct CAP uninstall IMPEX element order - #145

Merged
shauryemahajanSF merged 1 commit into
release/26.8from
W-24087851-cap-uninstall-impex-order-26.8
Sep 10, 2026
Merged

shauryemahajanSF merged 1 commit into
release/26.8from
W-24087851-cap-uninstall-impex-order-26.8

Conversation

@shauryemahajanSF

Copy link
Copy Markdown
Contributor

Summary

  • Same change as @W-24087851 Correct CAP uninstall IMPEX element order #144, targeted at release/26.8.
  • CAP uninstall services.xml must follow Site Impex services.xsd: credential → profile → service, the same order as install. The previous service → profile → credential guidance matched Business Manager UI delete-in-use rules but produced invalid uninstall files, so services were not deleted.
  • Updates generate-service-impex, validate-impex, validate-app, the scaffold uninstall template, AGENTS.md, docs/testing.md, and the PR template. Skills now distinguish BM UI (service-first) from CAP uninstall IMPEX (XSD order).
  • GUS: W-24087851

Test plan

  • Confirm services-uninstall.xml.tmpl lists credential, then profile, then service, each with mode="delete"
  • Confirm no remaining skill or template tells authors to delete service → profile → credential for IMPEX
  • Confirm generate/validate skills still document BM UI service-first delete as UI-only, not IMPEX
  • Spot-check xmllint --noout on the uninstall template

…e → service

Site Impex services.xsd requires the same element sequence as install. The old service-first guidance matched BM UI delete rules but produced invalid uninstall files.
@shauryemahajanSF
shauryemahajanSF requested review from a team September 10, 2026 15:59
@shauryemahajanSF
shauryemahajanSF merged commit f28e9bd into release/26.8 Sep 10, 2026
1 check passed
@shauryemahajanSF
shauryemahajanSF deleted the W-24087851-cap-uninstall-impex-order-26.8 branch September 10, 2026 16:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant