Ideas for Arc XP

Versioning of Pagebuilder Bundles

This is a request to add versioning support for PageBuilder Bundles.
This requirement/idea is to specifically service the mobile apps.

PageBuilder templates are a great tool to define and customize UI of the Apps but the resolvers lack support for adding versions of the PageBuilder Bundle.
Since mobile apps versions cannot be controlled by us, we cannot upgrade the templates by deprecating older components in the bundle.
We are forced to add a version string to the template resolver and also always have the older feature in the new bundle too.

This would be

  1. Maintenance issue for PageBuilder development team

  2. Cause confusion for the editors when they select the FEATURE in the editor as all the versions would be available.


This could be solved

  1. Creating an ability to version the PageBuilder Bundles (similar to the “d” param), it would be best if we could get this version selection inside the resolver configuration

  2. Creating multiple environments to support PageBuilder Bundle version which is much less desired.


  • Guest
  • Nov 9 2021
  • Will not implement
  • Attach files
  • Admin
    Fatih Yildiz commented
    November 09, 2021 20:57

    Hi Mrudula,

    Thanks for submitting this idea. Versioning change sets along with the bundles is a fundamental Editor change to how we do deployments. For the time being, because of the complexity this will bring, we will not implement this. But there are a few alternative ways that I'm sure you guys are already exploring. A few of them:

    1) Using new "Themes Settings UI" app that allows you to set custom configuration per site. These configurations are separately versioned than the bundles. You can preview the configuration sets and you can pick and chose the bundle to deploy when it's time to deploy. If you don't need the UI for configurations, Theme Settings UI may not be effective and essentially no different than having all configurations as environment variables.

    2) Alterantively you can use site properties for site-specific configuration variables.

    3) And lastly, you can keep your configurations as json files and manually version them then bundle them manually when doing deployments. This will allow configurations to be swap-able.