What's New in PageBuilder
Discover the latest updates to Arc XP's PageBuilder suite of products.
Release dates
Sandbox and Production - Wednesday, July 23, 2025
Release summary
This hotfix includes updates to prepare for an upcoming Mongo database upgrade.
Users affected
PageBuilder users
Action required
None
Release dates
Sandbox - Tuesday, July 8, 2025
Production - Thursday, July 10, 2025
Release summary
This release fixes the Import Page functionality, ensuring that new pages are accurately created based on the imported content.
Users affected
PageBuilder admins
Action required
None
Release dates
Sandbox - Tuesday, June 10, 2025
Production - Monday, June 23, 2025 (was previously Tuesday, June 17, 2025)
Release summary
This release contains the following updates:
You can now use Integrated Search capabilities on chains, in addition to blocks.
Adds additional validation to Resolvers to ensure data is saved as expected.
Updates error messaging in the Blocks search panel to be more accurate.
Removes Audience Targeting functionality when running PageBuilder Editor locally.
Fixes an issue that sometimes prevented users from updating a custom field.
Remove unused Stencil Page permissions that were inadvertently introduced. (These permissions are not functional).
Users affected
PageBuilder Editor users
Action required
None
PageBuilder Editor 3.21.2 (Sandbox) and PageBuilder Editor 3.20.3 (Production)
Release dates
Sandbox and Production - Monday, January 13
Release summary
This hotfix fixes a bug for number custom fields. Previously, when the user inserted over 15 digits into a number custom field, the value was automatically rounded up. Now, the value is not rounded up or adjusted in any way.
Users affected
Developers
Action required
None
PageBuilder Editor 3.21
Release dates
Sandbox - Wednesday, December 4, 2024 (was previously Tuesday, December 3, 2024)
Production - Monday, February 10 to 11 (was previously Monday, January 13, 2024)
Release summary
Note
When this change occurs, active users in PageBuilder Editor may see a prompt to refresh their browser. While we perform the upgrade in our services, users who are actively working in PageBuilder Editor may see an error message that instructs them to refresh their browser. When that message appears, simply refresh the browser and continue working. Rest assured that there will be no data loss during this process. Your work and information are safe, and you can continue your tasks with confidence.
This message appears only once, and only if a user is actively using PageBuilder Editor at the time of release.
If the issue persists after refreshing your browser, try clearing your cache. If that doesn't resolve the issue, contact Arc XP Customer Support.
This release contains the following bug fixes and improvements:
A bug that occurred when changing the Display Name and then Custom Fields on a block was fixed. The Display Name now saves as expected, and does not revert to the previous value.
Improved styling, font consistency, and alignment across the platform
Additional updates and bug fixes for faster loading and better error handling
Additionally, this release includes some updates in preparation for Micro Experiences (MX), which allows organizations to run multiple instances of PageBuilder in their organization. While MX is not yet available to use, this release contains the following updates in preparation:
PageBuilder Editor URLs in Arc Admin will change:
The previous URL pattern for PageBuilder Editor was:
https://{org-ID}.arcpublishing.com/pagebuilder/pagesWith this release, it will change to:
https://{org-ID}.arcpublishing.com/pagebuilder/experiences/_default/pages
All of the old URLs are automatically redirected to the new URL format. There is no action required from customers, and no expected impact to PageBuilder Editor users as a result of this change.
The Arc Home tile for downloading PageBuilder data (pb-data) is being removed: In May 2024, as part of our Editor 3.20 release, we introduced the ability for developers to download a copy of the pb-data file from within PageBuilder Editor’s Developer Tools menu. As part of this Editor release, we’re now removing the pb-data tile from Arc Home. Instead, developers should get a copy of PB Data by accessing Developer Tools > Data Center from within PageBuilder Editor.
Users affected
Editors and Developers
Action required
Developers: To download a copy of pb-data for use in local development, navigate to PageBuilder Editor > Developer Tools > Data Center.
Editors: If you're using PageBuilder Editor when we perform the upgrade, you may see an error message instructing you to refresh your browser. When this happens, refresh your browser to continue working. There will be no data loss during this process, so your work and information are safe.
PageBuilder Editor 3.20.0
Release dates
Sandbox - Wednesday, May 29, 2024 (was previously Thursday, May 23, 2024)
Production - Thursday, June 6, 2024
Release summary
This release includes some preliminary changes to support the upcoming PageBuilder Micro Experiences feature and several bug fixes and maintenance.
In Editor 3.20.0, we are introducing a new UI for downloading PageBuilder data. This change is in preparation for an upcoming PageBuilder feature called Micro Experiences, which allows organizations to run multiple, different bundles on separate PageBuilder Engine instances. In this Editor release, we are adding a new “PB Data” tab under the Developer Tools section of PageBuilder, so that in a future release, you can download the PageBuilder data on a per-Micro Experience basis. PageBuilder data download will live at a new URL, /pagebuilder/tools/data-center. In a future release, we will remove the PB Data download tile from the Arc Home screen.
 |
Small Improvements/Bug Fixes:
Characters of long website lists are no longer being cut off in the linking card modal
Confirm modal was refactored to ensure modals do not overlap
Click action on Edit and Delete of Resolvers is now working properly
All Resolver URL parameters are now encoded properly to ensure Resolvers map fields to content sources correctly
Added environment name checks for PageBuilder Data Copy (PB Data Copy Version 1.1)
Local Development - Default mock permissions have been updated.
Display Name field on blocks no longer reverts when not in focus
During our final testing phase, we encountered some regression issues that require additional attention. As a result, the fix for the bug initially slated for this release will now be included in the next release to ensure its quality and stability. We appreciate your understanding and patience as we work to deliver the best possible product.
Users affected
PageBuilder developers, admins, and users
Action required
None
PageBuilder Editor 3.19.3
Release dates
Sandbox - Wednesday, April 10, 2024
Production - Wednesday, April 10, 2024
Release summary
PageBuilder 3.19.3 includes Audience Targeting 1.1.1 which fixes an issue where variants were not shown on the Audience Targeting Dashboard list. Now, the filtering of sites is working appropriately and variants are shown for a site that has Audience Targeting enabled.
Users affected
PageBuilder Audience Targeting admins, PageBuilder Editor users, PageBuilder developers, PageBuilder admins
Action required
None
PageBuilder Editor 3.19.2
Release dates
Sandbox - Thursday, March 28, 2024
Production - Monday, April 1, 2024
Release summary
This release fixes a bug in Audience Targeting related to the Optimize workspace displaying an error message. No significant updates from the original 3.19 Sandbox release. This version goes to Production on April 1 in place of 3.19 and 3.19.1.
Users affected
PageBuilder Editor users, PageBuilder developers, PageBuilder admins
Action required
None
PageBuilder Editor 3.19.1
Release dates
Sandbox - Tuesday, March 26, 2024
Production - Monday, April 1, 2024
Release summary
This release resolves several bugs that were introduced with the 3.19 Sandbox release, mostly related to padding, color, and font size. No significant updates from the original 3.19 Sandbox release. This version goes to Production on April 1 in place of 3.19.
Users affected
PageBuilder Editor users, PageBuilder developers, PageBuilder admins
Action required
None
PageBuilder Editor 3.19
Release dates
Sandbox - Monday, March 18, 2024
Production - Monday, April 1, 2024
Release summary
PageBuilder Data Copy Sync
We are excited to announce the release of PageBuilder Data Sync, a programmatic, API-based solution that allows you to create a complete copy of your PageBuilder data from Production and lower environments and transfer and sync the data copy to a non-Production environment. Previously, this task required you to submit a request to Arc XP to execute, but with PageBuilder Data Sync, you now have a self-service option to execute this task.
Arc XP Audience Targeting Improvements
This release includes improvements to the PageBuilder Editor Audience Targeting experience. For more information, see What's new in Audience Targeting.
Users affected
PageBuilder Editor users, PageBuilder developers, PageBuilder admins
Action required
None
PageBuilder Editor 3.18.4
Release dates
Sandbox - Tuesday, February 20, 2024
Production - Wednesday, February 21, 2024
Release summary
In an effort to improve our product, Arc XP is collecting certain performance data so we can analyze trends and make more strategic product decisions. This hotfix includes internal updates that enable data collection for PageBuilder Editor feature usage from users who have consented to share this data with Arc XP through the consent banner that was deployed on December 11, 2023.
Users affected
PageBuilder Editor users
Action required
None
PageBuilder Engine release matrix
The following table provides an overview of which versions of PageBuilder Engine are available.
Release | Status | Release Date (Production) | End of support | Requirements |
|---|---|---|---|---|
6.x | Sandbox | April 28, 2025 | to be announced | Node 20.x |
5.x | Production | November 27, 2023 | September 30, 2025 | Node 18.x NPM 7.x or 8.x |
4.x | Deprecated | May 11, 2023 | July 10, 2024 | Node 16.x NPM 6.x or 7.x |
Release dates
Sandbox - Monday, June 23, 2025
Production - Tuesday, June 30, 2025
Release summary
This release contains the following updates:
contentCacheis now available inoutputTypes- We now exposecontentCacheinfusion:contextavailable inoutputTypefor greater developer access to request-level content caching data.Environment file fix in Micro Experience (MX) environments - We updated the PageBuilder Compiler to correctly resolve environment inheritance in multiple MX environments. Previously, MX runtime used an
{org}-{env}-{mxId}format for theENVIRONMENTvariable, but environment files were not consistently inheriting due tomxIdsuffixes. This patch ensures environment inheritance uses the base{org}-{env}format across MX environments.
As per the Engine versioning policy, this patch removes previous patch versions in the same major group.
Users affected
Developers
Action required
None
Release dates
Sandbox - Monday, June 23, 2025
Production - Tuesday, June 30, 2025
Release summary
This release contains the following updates:
contentCacheis now available inoutputTypes- We now exposecontentCacheinfusion:contextavailable inoutputTypefor greater developer access to request-level content caching data.Environment file fix in Micro Experience (MX) environments - We updated the PageBuilder Compiler to correctly resolve environment inheritance in multiple MX environments. Previously, MX runtime used an
{org}-{env}-{mxId}format for theENVIRONMENTvariable, but environment files were not consistently inheriting due tomxIdsuffixes. This patch ensures environment inheritance uses the base{org}-{env}format across MX environments.
As per the Engine versioning policy, this patch removes previous patch versions in the same major group.
Users affected
Developers
Action required
None
Release dates
Sandbox - Monday, April 14, 2025
Production - Monday, April 28, 2025
Release summary
PageBuilder Engine 6.0 introduces support for the Node.js 20 runtime, which ensures compatibility with the latest technologies while enhancing performance and security. There are no other functional or breaking changes for PageBuilder Engine or Arc XP blocks for bundles already running on Engine 5.0.
To plan your migration to PageBuilder Engine 6.0, see Migration from PageBuilder Engine 5.x and 6.x.
Users affected
Developers
Action required
AWS Node 18 runtime support and PageBuilder Engine 5.0 will be deprecated on September 30, 2025. To continue deploying changes in Arc XP environments beyond this date, you must upgrade to Engine 6.0.
Release dates
Sandbox and Production - Monday, March 17, 2025
Release summary
We added improved handling for encoded SVGs.
The
pagebuilderURLmethod is now available for server-side renders in output-types.If you include styled components within the
outputType, the PageBuilder Editor preview now displays those styles correctly. Previously, those styles were excluded within Editor preview but appeared in the actual render (outside of PageBuilder Editor).Our PageBuilder Engine version policy will be enforced by March 31, 2025. After this date, only Engine 5.1.3 will be available for Deployments. Versions 5.0.5, 5.1.1, and 5.1.2 will become unavailable in Deployer.
[Extended] Engine 5.0.7 will become unavailable on April 10, 2025.
Users affected
Developers
Action required
Our PageBuilder Engine version policy will be enforced by March 31, 2025. After this date, only Engine 5.1.3 will be available for Deployments. Versions 5.0.5, 5.1.1, and 5.1.2 will become unavailable in Deployer.
Release dates
Sandbox - Tuesday, February 4, 2025
Production - Monday, February 10, 2025 (was previously February 4)
Release summary
We updated PageBuilder Engine to support Micro Experiences.
Users affected
Developers
Action required
None
Release dates
Sandbox and Production - Monday, December 16, 2024
Release summary
This hotfix reverses the styled-components dependency to 5.3.5 to keep the Engine release in a non-breaking path.
Users affected
Developers
Action required
None
Release dates
Sandbox - Thursday, December 5, 2024 (was previously Tuesday, December 3, 2024)
Production - Monday, December 16, 2024 (was previously Tuesday, December 10, 2024)
Release summary
Micro Experiences Support: Initial support for Micro Experiences has been added to PageBuilder Engine. (Details about the Micro Experience feature will be announced separately.)
Security Enhancements: Implemented key security updates and performed dependency upgrades to maintain system integrity and performance.
Bug Fixes: Resolved an issue in Engine 5.0.7 where multiple client-side API calls were being triggered unnecessarily.
Users affected
Developers
Action required
No action required, and customers can safely deploy their current Engine 5.0.x bundle (that's tested and deployed with Engine 5.1.0) with no additional work required.
Release dates
Sandbox - Thursday, August 22, 2024
Production - Monday, August 26, 2024
Release summary
SPA Context Update: Fixed an issue in the Single Page Application (SPA) where the context was not being updated correctly.
Enhanced Meta Tag Handling: The Editor UI now supports both the property and name fields for generating Meta tags, offering more flexibility in meta tag management.
Preparation for Upcoming Micro Experiences Feature: Implemented a new resolver payload validation and updated the logic of generating cache keys, to support each Micro Experience has its own isolated cache space.
Users affected
Developers
Action required
None
Release dates
Sandbox - Thursday, May 16, 2024
Production - Tuesday, May 21, 2024
Release summary
Fixed a bug in SPA navigation preventing the page from accessing the correct global content.
Added additional type-safety around Bandito integrations
Implemented support for disabling client side data such as globalContent and contentCache for a given output type. See Output Type API documentation to learn more.
Prevent devtool override from affecting production builds
Fixed a bug where custom content sources throwing HTTP 301 redirects was not working correctly.
Users affected
Developers
Action required
None
Release dates
Sandbox - Wednesday, April 24, 2024
Production - Monday, April 29, 2024
Release summary
Faster local builds
We've improved local build speed using parallel threads that can be enabled with using parallel: true in arc.config.json.
Support for larger, complex bundles
You can now use a new build flag to prevent duplicated node modules in compiled content sources, resulting in smaller final server-side bundles. This allows you to have more space for your dependencies or more complex codebases. This is an opt-in behavior controlled in arc.config.json using compiler.contentSources.excludeModules.
Bug fixes
Fixed a bug in layouts where renderable content was incorrectly reflecting the original on-load value and didn't update when adding or removing components from PageBuilder Editor.
Surfacing node module loading errors to users during compilation to help client developers troubleshoot errors caused by dependencies.
Users affected
Developers
Action required
None
Release dates
Sandbox - Monday, January 29, 2024
Production - Monday, February 5, 2024
Release summary
All React components now properly rehydrate. This issue was caused by the underlying JSX parsing code using the legacy hydration method, which had been deprecated and replaced in the current React version.
Support for
schemaNamein content-source configs is now restored. This resolves a potential issue where stringifying a content source might strip the schema-name field from its body.Type-safety of
fetchandresolvemethods in Content Sources is now improved to prevent errors that may occur.
Users affected
Developers
Action required
None
Release dates
Sandbox - Wednesday, January 3, 2024
Production - Monday, January 8, 2024
Release summary
We optimized the content source compilation for duplicate bundled modules, which creates reduced bundle size inside deployed AWS Lambda and provides the ability to deploy larger bundle code and dependencies.
The custom TTL functionality inside of the Fetch Content Sources is now restored.
A silent validation now exists on the developer-defined content-source configuration options and unexpected content types now use their default values. This resolves some potential bugs where, for example, the
transformproperty may be set tonulland cause the content-source to raise an HTTP 500 error when it is invoked. The new validation logic replaces thetransform: nullwith an identity function (transform: x => x). Consequently, the risk of undefined behavior arising from incorrectly defined-configuration options is now mitigated.Content sources now consistently apply default parameters across content source types.
Users affected
Developers
Action required
None
Release dates
Sandbox & Production - Monday, November 27, 2023
Release summary
This release fixes a bug in the content-source caching logic that could crash upstream APIs on large traffic pages. This bug was caused by a change that resulted in cache entries not updating if they already existed.
Users affected
Developers
Action required
Clients who want to upgrade to Engine 5.x can learn more in Migrating from PageBuilder Engine 4.x to 5.x.
Release dates
Sandbox - Monday, November 13, 2023
Production - Monday, November 27, 2023
Release summary
PageBuilder Engine 5.0 supports Node.js 18 runtime. Newer Node.js runtime is the only change compared to Engine 4 versions.
There is no other functionality, or breaking change on PageBuilder Engine and Arc XP Blocks usage for bundles already upgraded to Engine 4.
Upgrading
If you're upgrading from Engine 3, see Engine 3 to 4 migration guide for the changes between Engine 3 and 4.
If you're upgrading from 4 to 5, you should expect minimal to no change in your bundle code, except that your dependencies may require development effort to support the new Node.js 18 runtime.
With every major runtime change, dependencies you use in your bundle (npm packages) may have introduced their breaking behaviors with runtime upgrades. We advise to you to review your npm packages' project pages for breaking changes in these packages. They may have published guides for upgrading if it requires change in your implementation.
We have compiled these suggestions in a brief Migrating from PageBuilder Engine 4.x to 5.x guide.
Users affected
Developers
Action Required
Engine 3 and 4 will be deprecated on March 31, 2024. You must upgrade to Engine 5.0 to be able to deploy changes in Arc XP environments after this date.
See full release notes and Deprecation notice: PageBuilder Engine 3 and Engine 4 notice for more information.
Discover the latest updates in PageBuilder CLI: @arc-fusion/cli npm package page.
PageBuilder CLI 2.3.0
Release dates
Sandbox and Production - Wednesday, July 31, 2024
Release summary
Clean up unset warning messages in the command line output for opt-in features.
Reduced number of ports fusion-cli maps in localhost to 80 (http), 27017 (mongodb). Previously PageBuilder mapped internal service ports to parent host which may have conflicted with customer developers services (such as zscaler) in their machines.
fusion verifycommand now checks the final bundle size and errors if customer code and dependencies exceed 150mb to prevent possible deployment errors.--composeflag supports setting the Docker Compose version. Valid values arev1(default) andv2.If you are working with newer Docker versions that use the v2
composecommand instead of the traditionaldocker-composecommand, you might get theError: spawn docker-compose ENOENTerror message.To solve this issue, configure fusion-cli to use the v2
composeversion by adding the appropriate flag:npx fusion start --compose v2.
Users affected
Developers
Action required
No action required.
To update your CLI, run npm install -g @arc-fusion/cli@latest
PageBuilder CLI 2.2.4
Release dates
Sandbox and Production - Wednesday, February 21, 2024
Release summary
CLI command options for
startandzipare no longer ignoredContent source redirects to external URLs in local development environments now work as expected.
Users affected
Developers
Action required
Update fusion-cli with npm install -g @arc-fusion/cli@latest
PageBuilder CLI 2.2.3
Release dates
Sandbox & Production - Thursday, December 21, 2023
Release summary
Resolver URLs should no longer have trailing slashes removed in local development.
Users affected
Developers
Action required
Update fusion-cli with npm install -g @arc-fusion/cli@latest
PageBuilder CLI 2.2.0
Release dates
Sandbox & Production - Monday, October 16, 2023
Release summary
This release introduced the following updates:
Added informational build-time logging when compiling customer bundle code.
fusion-clinow prints build timings for different build-steps and a build completion message to let developers know when the build is done and ready. See How to Work with Engine Logs in Local Development Environment for more information about build-steps and example outputs of this improvement.Reduced container log output in the
fusion-clioutput.
Users affected
Developers
Action required
Update
fusion-cliwithnpm install -g @arc-fusion/cli@latestNew features require the latest Engine release 4.0.5 (or newer) used together with this CLI update
PageBuilder Deployer 2.1.1
Release dates
Sandbox - Monday, February 3, 2025
Production - Wednesday, March 5, 2025
(was previously Wednesday, February 26, 2025)
Release summary
We’ve added a label in the Deployer that displays the number of pending deployments for your environment, along with the deployment limit.
Deployer enforces a limit on the number of pending deployments per environment: 10 for Production and 20 for lower (non-Production) environments. Previously, there was no indication of how many deployment slots were in use or whether you had reached the limit. The only indication was a disabled Deploy button in the bundles list, without an explanation.
With this update, you can now see at a glance how many deployments are pending and when you’ve reached the limit.
At the top of the bundles list, which is below the pending bundles list, you now see a message that if you reach the deployment limit of 10 bundles. This message explains why the Deploy option is disabled.
Users affected
Developers
Action required
None
PageBuilder Deployer 2.1
Release dates
Sandbox - Monday, January 13, 2025 (was previously Monday, January 6, 2025)
Production - Monday, February 10, 2025 (was previously Tuesday, January 21, 2025)
Release summary
We introduced a new underlying deployment service to PageBuilder Deployer, which adds support for Micro Experiences. Alongside this update, we’ve made several user experience improvements to the Deployer interface.
Previously, failed our timed-out deployments disappeared from the main deployments table, requiring developers to navigate to the Deployments History page to locate them. With this update, failed and timed-out deployments will remain visible in the main table until manually removed, streamlining access to important deployment information.
Developers can now view failure messages directly in the deployment list, along with a shortcut to download logs. This eliminates the need to locate failed or timed-out deployments in the Deployment History page, saving time and effort.
Deployer API - deployment endpoint now validates the Engine version provided in the API call and accepts only available Engine versions. If you pinned an older Engine version that is not available anymore, Deployer API returns an error rejecting the deployment request.
Users affected
Developers
Action required
None
PageBuilder Deployer 2.0
Release dates
Sandbox - Thursday, April 27, 2023
Production - Thursday, May 11, 2023
Release schedule by region:
Sydney: 8:00 AM to 11:00 AM Eastern Time
Tokyo: 11:00 AM to 2:00 PM Eastern Time
Washington, D.C.: 2:00 PM to 5:00 PM Eastern Time
Frankfurt: 4:00 PM to 7:00 PM Eastern Time
Release Summary
PageBuilder Deployer 2.0 includes the following items.
On-deck bundle limit is increased from 10 to 20 in non-production environments
We are excited to introduce a new feature to Deployer 2.0: an increased on-deck bundle limit in non-production environments. With this change, developers can now deploy up to 20 on-deck bundles at once, providing greater flexibility and control over the deployment process.
We understand the importance of speed and efficiency when it comes to web application deployment, and we believe that this feature helps you be more productive and test code changes using preview functionality with on-deck bundles.
This change is available only in environments other than Production and outboundfeeds Production environments.
Modernized User Interface using Arc Design System
The PageBuilder Deployer 2.0 release uses our Arc XP Design System to modernize and provide a consistent user experience with the rest of Arc XP Admin tools.
In addition to the Arc XP Design System integration, Deployer 2.0 incorporates a wealth of user experience improvements based on feedback from our user research survey. We've implemented changes that make managing current deployments, navigating deployment history, seeing and filtering failed deployments faster, more intuitive, and easier to use.
The biggest visible change in Deployer 2.0 is that Deployer History is now a standalone page instead of a drawer that opens on the right side of the visible page on top of the current view. This panel had limited real estate for you to scan, scroll, filter, and see details about past deployment activities.
With the full-page view of Deployer History, we display more details about each deployment activity, a faster infinite loading experience of deployments if you have a long history of events.
We did not introduce a change in core functionality and Deployer API specs in the Deployer 2.0 release.
Users affected
Developers using Deployer UI and API.
Action required
None
Known Issues
On the Deployer History tab, the Download Bundle button may not work. As a workaround, developers can use the download bundle option in the ... menu on the main "Bundles" page.
On the Deployer History tab, the download logs icon may not behave as expected on failed deployments.
Deployment logs may not be available in every deployment and developers may see a "No log was found" error message when clicking the Download logs button.
In the Upload panel, the file selector input field is currently not supporting drag and drop functionality directly from the operator system's file browser. Developers must click Upload Bundle and select the file manually.
Release dates
Sandbox - Tuesday, June 10, 2025
Production - Tuesday, June 17, 2025
Release summary
This release includes the following updates:
PageBuilder Data Copies in Staging now work as expected.
Backups of environments are now properly completed during the PageBuilder Data Copy process.
Users affected
Developers
Action required
None
PageBuilder Data Copy 1.2
Release dates
Sandbox - Tuesday, September 3, 2024
Production - not going to Production
Note
The PageBuilder Data Copy API is available only in Sandbox because you use Production as a source for copying.
Release summary
A couple of small improvements to the PageBuilder Data Copy API to prevent a failing job:
Environment names are now case agnostic; uppercase letters are now accepted
Fixed an issue where tables already existed, causing an exception
Users affected
PageBuilder developers, admins, and users
Action required
None
Release dates
Sandbox - Monday, February 3, 2025
Production - Monday, March 3, 2025
(was previously Tuesday, February 18, 2025)
Release summary
Introducing Micro Experiences (MX), a new capability within PageBuilder designed to enhance flexibility and efficiency for development teams. MX allows you to create multiple independent PageBuilder instances, each configured with its own codebase and features. This empowers organizations to tailor digital experiences for specific business need or audience segments while maintaining operational efficiency.
Key Benefits
Parallel Deployments: Teams can work and deploy changes independently, improving collaboration and productivity.
Enhanced Efficiency: Streamline workflows to accelerate development and reduce time to market.
Minimized Risk: Isolate business-critical components to reduce the impact of deployment errors.
Use Cases
Launching new digital properties with tailored designs and functionality.
Isolating business-critical systems like subscriptions and identity management.
Supporting multiple development teams with independent environments.
Iterative redesigns or upgrades without disrupting existing systems.
Availability and Setup
MX is available as an opt-in feature for PageBuilder customers. To enable MX for your organization, contact Arc XP Customer Support.
Learn More
Users affected
Developers
Action required
None