Enhanced P2T Flexibility Is Here: Greater Scheduling Flexibility
We’re excited to share that the enhanced P2T process has been successfully validated in a scenario where Production and Test were on different application releases, a condition that previously prevented a P2T refresh and created a release-based blackout period.
Historically, a P2T refresh could not be completed when the source and target environments were on different application releases. With this successful validation, that restriction has been removed. Institutions can now request P2T refreshes throughout the release cycle without planning around release-based blackout dates.
There remains one blackout date: a P2T refresh cannot be scheduled on the day of an application release. Outside of the release day, institutions have greater flexibility to schedule P2T refreshes according to their testing priorities rather than waiting for Production and Test to align on the same application release.