Importing Constellation DX Components

Hi,

We are using several components from the Constellation UI Gallery (GitHub - pegasystems/constellation-ui-gallery).

Our current approach is to download the COMPONENTS_ONLY ZIP packages (for example, ConstellationUIGalleryLib_5_0_6_COMPONENTS_ONLY.zip) and import them into our development environment whenever we need a major release or patch update.

I have a question regarding version management of the imported assets.

The downloaded ZIP always contains the ruleset ConstellationUIGalleryLib with a ruleset version of 01-01-01. In newer releases, many existing components are delivered with updated JavaScript files that have different names. As a result, importing a new release creates additional rules instead of replacing the existing ones.

Over time, all component updates accumulate under the same ruleset version (01-01-01), causing that ruleset version to grow significantly.

Questions:

  1. Is it acceptable to continue importing component updates into a single ruleset version (01-01-01) as provided by the ZIP packages?
  2. Are there any best practices for managing versioning and rollback support when importing newer component releases?
  3. How do other teams handle cleanup or governance of older component versions that remain in the ruleset after multiple imports?

Any guidance, recommendations, or examples of how others manage Constellation UI Gallery component upgrades would be greatly appreciated.

Thanks!

Hello @duraisankar

In my view, it’s worth keeping in mind the primary purpose of the Constellation UI Gallery components. These components are provided as reference implementations, samples, and accelerators to help teams explore patterns and extend Constellation capabilities. They are community-driven contributions, and their design goals may differ from the governance, versioning, and maintenance standards typically expected for production-grade enterprise assets.

Because of that, I would recommend evaluating any external component before adopting it broadly within your organization, particularly for production use. Areas that are typically worth reviewing include:

  1. Security considerations
  2. Accessibility compliance
  3. Third-party package dependencies and potential vulnerabilities
  4. UI performance and rendering efficiency
  5. Alignment with your organization’s development and support standards

A strong governance process can help ensure that imported components meet your organization’s quality, security, and maintainability requirements. In many cases, having an experienced React developer review the implementation is also beneficial, especially before promoting the component to higher environments.

Another approach some teams take is to use the Gallery component as a starting point and then create their own organization-managed version within a dedicated component library. This allows them to apply internal standards, implement enhancements, address security or accessibility requirements, and manage versioning according to their own release processes.

Regarding the specific versioning and upgrade questions, I don’t believe there is currently a formally documented best practice for lifecycle management of imported UI Gallery assets. Since the assets are delivered under a fixed ruleset version, questions around upgrade strategy, cleanup of superseded assets, and long-term governance would ideally be clarified by the maintainers of the project. It may be worth seeking guidance from the UI Gallery maintainers, such as @RichardMarsot and the broader contributor community, to understand the rationale behind the current packaging approach and any recommended upgrade practices.

Overall, if these components become business-critical within your organization, I would treat them similarly to any other third-party code dependency: establish internal ownership, define governance standards, and maintain a clear upgrade and rollback strategy independent of how the assets are distributed.

Hope this helps.

Regards

JC