We have upgraded our Pega SaaS app to 25.1.3 from 24.2.4.
Post upgrade we are seeing the below message when we are processing a case.
- Component Not Found - Pega_Extensions_BannerInput
We have upgraded our Pega SaaS app to 25.1.3 from 24.2.4.
Post upgrade we are seeing the below message when we are processing a case.
Try checking if the component is listed under Enabled components of application definition.
Is this a Constellation application? Also, do you see detailed error in the logs?
Component Not Found - Pega_Extensions_BannerInput after upgrading to 25.x is typically a Constellation component registration/loading issue, rather than a case processing issue itself.
This error indicates that the client is trying to render a component named Pega_Extensions_BannerInput, but the component definition cannot be found in the Constellation component registry.
Check:
Records → UI → Component
Search for BannerInput
Verify the rule exists.
Verify it belongs to a ruleset included in the application.
From Pega 25 onwards, component availability is determined by the application’s rulesets, and published components must be available in those rulesets.
After platform upgrades, Pega recommends regenerating application metadata.
Try:
Open Application rule
Save
Generate Routing Table
Restart the node if possible
Similar Constellation issues after upgrades have been resolved by regenerating routing metadata and clearing cached data.
I don’t see the components coming under DX components. Do we need to specifically add them somewhere?
@AvisekM6 are you in the User Experience Expert Circle? I would like to move this under that area, so it can be found with other Constellation questions. However, if you are not a member you won’t be able to respond (until you join), so don’t want to just move on you.
Please let me know if you join and i’ll move.
In '25 the component must be in a ruleset in the application stack, commonly see this when people moving from '24.
Check out Webinar Replay! Extending Constellation: A Deep Dive into Constellation DX Components we do cover the changes there
Thanks @MarcCheong . It has been fixed after adding ConstellationUIGallery in the app stack.