The Marketplace now lists the Constellation Modernization Assistant as deprecated (“no further enhancements are planned”) and points to Pega Application Signature as “a modernized and fully supported approach for your application”.
The two tools do not have the same scope:
- CMA: analysis mode and migration mode: it could move assets from an existing application into a Constellation one.
- Application Signature: extracts metadata into a .pegasign file for Blueprint. Analysis only, by design.
So the replacement removes the migration capability rather than modernizing it. Read side by side, the two pages look less like one tool succeeding another, and more like a change of position on whether UI-Kit applications should be converted at all.
Questions
-
Is Application Signature formally the successor to the CMA for UI-Kit → Constellation, or is the CMA’s migration mode retired with no equivalent in the product?
-
For an application on ’24.2 today, is running the deprecated CMA still a legitimate assessment step, or is the guidance to go straight to Application Signature?
-
Should we read this as Pega’s position that there is no automated conversion path from UI-Kit to Constellation, and that the supported route is a regeneration through Blueprint?
We are documenting migration options for a decision this autumn and would rather rely on Pega’s stated path than on inference.
Any official guidance would be much appreciated.
Thanks,