How to create custom Constellation DX component in FW applications

General
, , , , ,
1

Team, We got some requirement from customer to create a custom constellation DX component in FW application

Can someone share the inputs, i saw in an article that

we have some feasibility issues.

Thanks

2

@umamaheswar.bkTo create a custom Constellation DX component in a FW application, first, clearly understand the requirements and check if Pega’s built-in components can be extended. Use React to design the component, ensuring it follows Pega’s Cosmos design system. Define the component in Pega App Studio and map it to DX API endpoints. Embed the component in the application by referencing it in sections or views and bind data using Pega data pages or data transforms. Test thoroughly to ensure it works as expected across devices and resolves any feasibility issues. Optimize the component for performance, document its usage, and deploy it through Pega’s deployment manager or CI/CD pipelines. If limitations arise, consult Pega documentation or explore alternative approaches like extending existing components ​​​​​​​

3

@Sairohith

Thank you for your response, Are there any limitations while creating Custom DX component in CS FW application

As per the note mentioned in the below article Framework might not support classic features

https://docs.pega.com/bundle/platform/page/platform/user-experience/creating-custom-dx-components-con.html

“While using Constellation DX components, keep in mind that it is an expanding product with a narrower feature set. Consequently, the framework might not support some classic features. You might also encounter unforeseen issues”

Could you please give me little more details on this..,

4

@umamaheswar.bkWhen creating custom DX components in a Customer Service (CS) Framework application, there are limitations due to the evolving nature of Constellation’s feature set. Constellation focuses on modernizing the UI and may not fully support some classic Pega features, such as advanced configurations available in traditional section-based designs or legacy features like non-standard scripts or specific rule types. For example, integrating custom JavaScript, handling highly complex conditional layouts, or certain mashup functionalities might require workarounds. Additionally, unforeseen issues could arise, particularly when combining Constellation components with older frameworks. It’s essential to evaluate your use case thoroughly, consult Pega’s official documentation, and test extensively to identify compatibility gaps and potential workarounds for your application ​​​​​​​