Adopt class library changes

Before you determine the appropriate approach to incorporate changes to the class library, consider whether the customer project uses:

• The AVEVA Master Library Project (MLP).

• A proprietary or custom class library.

For all projects, complete the minimum update requirements. Then, if necessary, follow the update approach that's appropriate for the target project's class library.

Minimum update requirements

When upgrading to a new product version, you must always complete the following steps to run the project on the new version of the product:

1. Open the project class model in the new version of AVEVA Unified Engineering.

2. Run a vocabulary validation and resolve any vocabulary issues.

3. Run the Model Integrity tool and resolve any reported issues.

4. Build the model.

These steps are sufficient for any customer project class model that uses the AVEVA MLP.

Additional class library update steps

After completing the minimum update requirements, additional updates may be required.

To adopt class library changes in a project that requires only the updates introduced in the latest MLP release, see Delta update.

To adopt class library changes in a project that uses a proprietary or custom class library, see Custom class library update.