Best Practices Analyzer · pattern code · OSGi configuration
BPA code UMI: Modified OSGi configurations that break upgrades
When Adobe's Best Practices Analyzer reports UMI, it has found modified OSGi configurations that break upgrades on your AEM instance. Here is what that means for a move to AEM as a Cloud Service.
What to do
Move configuration into the code base as .cfg.json files.
Step-by-step fix: Converting OSGi configurations to .cfg.json for AEM Cloud Service.
Can it be fixed automatically?
- Not by Adobe's Content Transformer, which only handles content findings (ACV, CAV, DOPI, OAUI, PCX, REP and URS).
- In our pipeline, automation for this pattern is rated high: agents prepare the change and an engineer reviews it.
How much work is it?
Our readiness scan plans about 1 hour per finding at MAJOR importance (1.5× for CRITICAL, 0.5× for ADVISORY), plus a small fixed cost, capped at 60 hours for this code. INFO rows are treated as inventory and not costed. These are planning figures, not a quote.
Reading the row in results.csv
Filter the code column for UMI. The importance column says how urgent each row is, identifier usually holds the repository path, and message describes the finding. See how to read a BPA report for every column.
Source: Adobe Pattern Detector documentation for UMI. Checked 19 October 2026.