Constellation DX Custom Component RAP not Pushing to APPStatic

General
, , , , ,
1

We have created a custom component in Dev environment and pushed to APP Static and able to configure it in APPStudio as well.

We are planning to maintain two different APP Static container. One for non prod & one for prod.

When we are planning to deploy DX Custom component as RAP file to other environment to push it to different APP Static server it is not working.

As per the below page only RAP file required to push it to other environment. Please suggest if I am missing anything.

I have tried to resave application and resave DSS for ConstelationSvcURL as well.

2

@SalaimathimamaniG please share PegaRULES logs when trying to import RAP

3

@SalaimathimamaniG I see that in September last year you had opened INC-B38728 for this issue: (Constellation DX Custom Component RAP not Pushing to APPStatic on version 24.1.1 )

It would help everyone enormously if in future you provide details of your open support tickets so that we can provide the final solution for others to see here on the forum searches…

The root cause was identified to be a user error:

“Using two different App Static services is causing the deployment of DX custom components to not work.”

Details provided by our Support Team:

"When upgrading to new versions, you need to ensure that your components will be compatible with the version you’re upgrading to. Specifically, you need to ensure that the changes that have occurred to PCore API’s will not have an impact on your custom components that use the APIs. The following document contains the changes that have been made to PCore APIs in 24.1 as an example https://docs.pega.com/bundle/pcore-pconnect/page/pcore-pconnect-public-apis/api/whats-new-pcore-pconnect-apis-infinity-24-1.html. Generally, you should avoid having your own custom components if Pega provides an alternative as this would allow you to avoid any maintenance overhead when upgrading.

You can find Pega’s OOTB components at https://pegasystems.github.io/constellation-ui-gallery/?path=/docs/getting-started–docs."

Solution description:

  • It is not recommended to have two different App Static Services in your application. One is sufficient to be used by all your environments.
  • After you publish your custom component, export the RAP of Rule-UI-Component instances from your lower environment to you higher environment to use the components.
    • Please note that both environments must use the same App Static Service.
  • When you publish a component, the changes will reflect in the current environment only. For the changes to reflect in higher environments also, you will have to export the RAP and import it in the higher environment. Publishing the changes to App Static will not impact the higher environments without importing the changes.