Ideas for Arc XP

Make PB config portable between environments

Re-creating layout/output/feature definitions between environments is a time consuming process. it would be great if, in any environment, you could push a button somewhere to export the entire mongo database associated with that environment. Then, in some other environment, you would be able to import what you just exported.

  • Greg MacGregor
  • Jan 8 2016
  • Future consideration
  • Attach files
  • James Butler commented
    25 Oct, 2021 11:28pm

    I will paste my comment from https://ideas.arcxp.com/ideas/PB-I-156, which was a very incremental improvement:

    This would be a very valuable addition for us. We are building an API from Arc using a JSON output type, which means that the structure of the API depends on a specific configuration of resolvers, templates and pages. Manually replicating this across environments to test and deploying new features is slow and error-prone. Ideally this feature would be API-driven so that we can use it from a CI pipeline, and would allow us to specify exactly which components are exported/imported so that changes can be isolated from each other.

  • Grzegorz Junka commented
    13 Jul, 2021 06:29pm

    Thsi is also the only way of copying pages that use linked components. Copying pages with linked components with the export/import added in PageBuilder Editor 3.4 is currently broken.

  • Tania Lee commented
    29 May, 2020 03:19pm

    We definitely know that this will be a useful feature. Currently, you can request this from ACS. We'll be planning on when we can add this work to our Engine roadmap.

  • Ian Krantz commented
    5 Feb, 2019 10:31pm

    Along with copying pages and features from Production to Sandbox, this is essential for doing meaningful testing in Sandbox environment

  • +1