Immediately before the release launch of the a major release (generally 7 days before), you customers can expect to receive additional communication from Pricefx on the release and its impact on your implementation. The Pricefx will also identify the potential for impending N-1 non-compliance will be identified.
...
While in the The Release Pending phase of your the Pricefx implementation, this is the an ideal time to conclude your the assessment of the release and corresponding impact on your the customer’s environment. In order to be prepared, we customers should be discussing the following questions:
...
Release Pending Phase Tasks
During this phase we the upgrade acceptance testing should have already begun our upgrade acceptance testing, and should consider the impact of the following:
...
Confirm that testing in QA has/is being performed to assess how the upgrade will impact your the environment from both a change and risk perspective. For example, to reveal if changes or updates would be needed to your SSO or ERP integrations, or help bring your the superusers up to speed on the new release.
Info |
---|
NOTE: If no upgrade testing is performed, then all issues, misunderstandings, or problems encountered later are resolved under COSA. If these issues aren’t aren not discovered and resolved before the upgrade, then the production application will be temporarily unavailable until resolved. |
...
Confirm the status and progress of your the upgrade testing and test plan. It is a good time to review the test plan timeline and its completion as compared to N-1 compliance timeline and communicate this information to Pricefx. If you don’t anticipate completing your completion of the acceptance testing is not anticipated prior to the expiration of the release Grace Period, then contact Pricefx.
Info |
---|
LEARN MORE: To learn more about the development of a Test Plan, guidelines, and recommendations for this task, |
...
click here. |
Acceptance Testing Progress
...