Managing of components with Pega Deployment Manager

General
,
1

We have created multiple components to promote reusability across different applications.

A described and discussed in How to manage components with PDM? | Support Center we are still facing the challenge of having components not beeing treated as first class citizens in PDM.

We are currently also employing the workaroud described in the Post linked above. But this poses the questions as to why to create a component in the first place, if we need to wrap it with an application for deployment and development reasons anyways.

Is there any plan to have “native” support for components in PDM (we are currently running PDM 5.5)?

Is there any benefit of wrapping a component in an application and referencing that to just using built on applications?

Thanks in advance for any insights / opinions.

2

@FlorianB1448 Hi Florian, You can use the Deployment pipeline on version 5.5 for components as well. You will not be able to select a component when creating a pipeline however you can just specify the name of the component. The tasks like VerifySecurityChecklist will not work for a component. You will need to configure the Product rule with the Component.

3

Hi @nayam, thanks for the reply. We will look into deploying components directly with PDM.

Do you know if the dependency management within PDM works with components as well as with applications?

4

@FlorianB1448 please see the latest response from the SME in a parallel question here:

Deploying Components with Deployment Manager Pipeline

If it does not cover your question, please tag @nayam again.

5

@FlorianB1448

As @nayam and @MarijeSchillern mentioned, you can use the Deploy Pipeline for deploying components across environments.

Only additional suggesstion I can make, keep a dedicated Pipeline for each of the component and its versions [ in case multiple versions exist in your Deployement Manager].

This is a successful process we are using today since 2022.