π A note about Validation Engine deployment:
When Pinnacle 21 Enterprise releases a Validation Engine update, that new engine will deploy to your environment automatically, so there is no need for any action on your part to add it. Once deployed, the new Engine will appear in the Data Package Configuration's Validation Engine section.
π What Validation Engines are currently available?
The Data Package Configuration screen currently lists total of 8 Engines:
|
|
π Deployment impact on your Data Packages
Data Packages configured with FDA Engines
For the FDA Validation Engine, P21E respects your prior Configuration settings. That means your Data Package will remain configured to the Engine you selected when you last configured it.
For example, after the release of FDA 2405.2, a Data Package configured to FDA 2304.3 will remain as FDA 2304.3 (Legacy). To use FDA 2405.2 for that Data Package, you will need to manually update the configuration to FDA 2405.2, then revalidate prior to submission.
π Note: For patch Engine versions, P21E will override your prior Configuration settings "in place." For example, a Data Package with Configurations set to FDA 2304.1, after the release of FDA 2304.2, those Configurations will change to FDA 2304.2.
Patch releases are indicated by a number above 0 after the decimal in the Engine's version number.
Data Packages configured with P21 and NMPA Engines
For the P21 and NMPA Engines, there is no "Legacy" concept. A Data Package's prior Configuration settings will update automatically to the newest P21 Engine (if configured to the P21 Engine) or NMPA Engine (if configured to the NMPA Engine).
For example, a Data Package that was configured to P21 Engine 2405.2, after the release of P21 2411.1, will update automatically to P21 2411.1.
π Note: P21 recommends revalidating your data after updating validation engine configuration.
π£ What's Next?
Learn more in the Validation & Issue Management Collection.
Email questions or feedback to support@pinnacle21.atlassian.net.