There are many benefits to maintaining your Pricefx solution at the most current release, or one release behind (i.e. N-1). These benefits span more than just incorporating our latest advancements. They will also reflect improvements in our core product, allowing the support team to respond quickly to our customer's needs. Therefore, to provide a high-quality product and support, starting in June 2023 Pricefx will enforce an N-1 upgrade compliance policy for our clients.

Defining N-1 Compliance

Essentially, our customers will need to be no more than 1 release behind our most current major release. So, when Paper Plane 11.0 was released in 2023, then our support will cover Bee's Knees 10.x and Paper Plane 11.0.

Compliance in Shared Environment

Customers who are hosted in our Shared environment, are upgraded regularly and automatically to the latest release, once it is made available. The Product Marketing team will send out notifications on the timeline for automatic upgrades to your environment.

The Shared environment option has the capability to use the Pricefx Shared Staging cluster for their QA partition. As such, the shared cluster is updated approximately one month prior to a Major release and 1 week before a Minor release.

Compliance in the Private Environment

The customers who are using Private hosting environment are NOT upgraded regularly and automatically to the latest release. They will receive notifications from the Product Marketing team on the timeline for automatic upgrades to their environment.

How Do I Maintain N-1 Compliance?

Maintaining good standing with the Pricefx N-1 policy will mean that your PROD release is either at the current release, or, at most, one release behind. To ensure compliance, be prepared to migrate to a new release during every release cycle and perform your release acceptance testing within the time period provided.

What Happens if I am Non-Compliant?

If your PROD release does not meet the N-1 compliance policy, then your environment will be automatically scheduled for upgrade to the nearest release that will maintain your compliance. All non-compliant environments are given an automatic 30 day Grace Period to allow them to migrate to a compliant state.