Software Version

the purple experience software (pxp) is versioned, and you can control which version runs for your web experience and your native apps this page explains what versions exist, what branches mean, and how to change the version in each context pxp uses a branch based versioning model a branch represents a specific line of development of the software and determines both the features available and the stability level you can expect branch stability notes release x y z stable a published, tested release recommended for production use hotfix x y z stable a targeted fix release on top of a release version safe for production develop unstable unstable | the latest code under active development may contain incomplete features and can change without notice not recommended for production feature unstable a specific feature under development may differ from `develop` and can be removed at any time, making any site using it unavailable master stable permanently set to pxp 4 2 rule of thumb use `release` or `hotfix` branches for production use `develop` or feature branches for early testing only changing the purple experience version for web websites in purple may be accessed through default domains or custom domains their respective experience versions are determined differently changing the version of the custom domain the version dropdown in purple manager only applies to a configured custom domain without a custom domain setup docid 5qp36x0omn32fk oye2ey , there is no way to pin your production website to a specific pxp version you would always be on the default this means to control exactly which pxp version your users see, you need a custom domain for testing a new pxp version using a custom domain (e g , to validate your configuration in a production like environment), you need a separate staging setup with its own custom domain you cannot use your production custom domain for testing without affecting live users for testing a new pxp version with production content but without a dedicated staging custom domain, use the default domain url scheme described below how to to change the branch for your web experience's custom domain , navigate to your app in purple manager via the dots menu, switch to "experience" and choose the proper branch in the version dropdown for further information on branches, see above after upgrading your purple experience, you may verify the proper version in your environment by opening its preview in the developer tools of your browser the dropdown is only applied to the configured custom domain to test a new pxp version with a custom domain, a separate staging setup with a custom domain must be used if you want to test a new pxp version with production content, you must use a default domain refer to the next section for details changing the version of the default domain for any website, we provide an environment using a default domain, web purplemanager com please refer to your purple manager settings for your respective url web purplemanager com always points to pxp 4 2, labeled purple web master you may switch versions by modifying as follows \<branch> web \<env> purplemanger com/\<brand> branch develop, release x y z, hotfix x y z, feature branches if deployed env staging or dev; if not set, prod brand refer to the basic settings of your app in purple manager switching the purple experience version for apps versions of experience used in apps are set in pxp builder you can check your current version and new versions available in the burger menu (1) in the top right corner of your experience builder when clicking on 'upgrade purple experience version' (2) upgrade app experience version by moving the toggle (3), you have the option to get only the final experience versions displayed or also snapshots and unstable versions your currently used purple experience version is displayed (4) on this page as well you have a list of all available purple experience versions on which you can upgrade below, e g , 2 5 0 (5), and you can select the desired version from the list by clicking on 'select a version' (6), you confirm your selection please refer to the release notes in the product updates https //updates purplepublish com/?type=t63e4fea162bf7 for details on the different versions we recommend upgrading the purple experience version separately on staging and not mixing it with any other changes you might want to make you can do the necessary configurations afterward on staging and publish the full package to prod as a final step to release your changes, you need to go to your app in purple manager > overview > three dot menu > dynamic and perform the 'copy to release' action returning to the previous purple experience/ dynamic version since summer 2025, we offer using a git system for handling dynamic resources for details, please refer to the following documentation git support for dynamic resources docid\ iscjtiic kffdun75ftst if the purple experience version was upgraded for testing reasons , it is sometimes necessary to downgrade the purple experience to the previous version once the testing is completed this is done via dynamic resources in the purple manager navigate to your app in purple manager via the dots menu (1), click on ' dynamic' (2) app overview in purple manager in the change history, go to the latest content version that was uploaded before your experience upgrade and click on the download icon (1) in the dynamic preview content row click on the upload icon (2) change history of dynamic content in purple manager choose the previously downloaded file in your local download folder (1) and press "open" (2) if the upload was successful, you will get a confirmation message in purple manager confirmation message in purple manager and your newest upload will appear in the change history change history of dynamic content in purple manager