Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

In this release cycle phase, we are entering the post-release period and where the Pricefx grace period for N-1 compliance will begin. Pricefx encourages all customers to familiarize themselves with the concept of automatic upgrades and the impact on their deployed solutions.

Tasks During Post-Release

While we are in the Post-Release phase of your Pricefx implementation, this is the time to understand our current standing regarding N-1 Compliance and possible outcomes if my implementation doesn’t meet the guidelines for N-1 Compliance In order to be prepared, we should be discussing the following questions:

  • Is my environment N-1 compliant?

  • What needs to be done to be N-1 compliant?

  • Do I need assistance upgrading my environment to N-1 compliance?

  • If I am non-compliant, then what will happen?

Upgrade Preparation during Post-Release

During the Post-Release period of the upgrade cycle, and as a best practice, Pricefx recommends that these steps be performed:

Code Promotion

Once all of the test cases have been performed and the results have been verified, then it is time to promote the core code from the QA system to your PROD environment.

LEARN MORE: To learn more about the code promotion process and the migration from QA to PROD environment, then click here.

Upgrade Smoke Test

The final step of your checklist will be the performance of a smoke test or build verification test to determine if all of the most critical functions of your application are performing as expected. This is a preliminary test of the new upgrade and its functionality.

LEARN MORE: To learn more about the concept of Smoke Testing and how to apply it in your environment, then click here.

LEARN MORE: To learn more about resolutions to common issues related to Pricefx upgrades, you can click here.

  • No labels