In the traditional UI (Theme Cosmos / Section-based) for Pega Sales Automation, there is an option (+ icon) to directly create/associate a Lead from the Leads tab within an Account context (as shown in the attached screenshot).
However, in the Constellation UI version of Sales Automation, this option to create a Lead directly under the Account > Leads tab is not available.
Could anyone clarify:
Is there a specific architectural/design reason why this action is not available OOTB in Constellation?
What is the recommended best practice / approach to enable or configure this “Add Lead” action under the Leads tab in Constellation?
Any guidance or reference to Pega documentation would be greatly appreciated.
In Constellation, the absence of the"+" (Create/Add Lead) action under Account → Leads is primarily due to the architectural shift from traditional section-based UI to a view- and case-centric experience.
In Theme Cosmos/UI-Kit, related lists often included inline actions implemented through sections, local actions, and custom harness configurations. Constellation, on the other hand, promotes standardized actions, reusable views, and DX API-driven interactions, reducing dependency on embedded UI customizations.
From the Sales Automation feature comparison documentation, Lead Creation and Conversion are supported in Constellation, but there is no indication that creating a Lead directly from the Account’s Leads related list is provided as an OOTB capability.
Recommended Constellation approach:
Expose a Create Lead action from the Account context.
Launch the Lead creation flow with the current Account prepopulated.
Automatically associate the newly created Lead to the Account during processing.
Refresh the related Leads list after creation.
This achieves the same business outcome while remaining aligned with Constellation design principles and preserving upgradeability.
If the business specifically requires an inline “Add Lead” experience within the Leads tab, it would likely require an extension using Constellation actions or a custom view configuration rather than relying on an OOTB capability. In general, I’d recommend following the standard case creation pattern wherever possible to stay within the supported Constellation model.
Thank you Anil for the detailed insights and explanation regarding the architectural direction in Constellation.
To add a bit more context to our business requirement: When a user launches the Create Lead modal from within the Account context, the expected behavior is that the Organization details (such as Organization Name, Territory, Industry, Website, etc.) should be automatically pre-populated on the creation form.
However:
When a Lead is created independently via the global + Create menu, these fields should remain blank and require manual entry.
When initiated from the Account context, we want these values fetched and mapped automatically to streamline user entry.
Any guidance or reference to Pega documentation would be greatly appreciated.
hi Venkatesh! I just heard back from the Pega Sales Automation team and they are aware of this missing feature. They are working on it and it’s expected that it will be included in the new release.
Thanks for your patience and thank you for informing us about this.
Thank you for confirming and following up with the Sales Automation team.
Since this capability is critical for our ongoing workflow, is there an estimated timeline or a planned HotFix / Patch release for Platform version 25.1.3 where we can expect this fix?
Alternatively, if this will only be available in a future minor/major release, could you share the target release version and whether an interim HotFix can be requested via an INC / Support Case?
