Skip to Main Content
AVEVA™ Products Feedback Portal

Welcome to our new feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, select the product of your interest in the left column. Then take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas will first be moderated before they are made visible to other users of this portal.

This page is for feedback for specific AVEVA solutions, excluding PI Systems and Data Hub. For links to these other feedback portals, please see the tab RESOURCES below.

Created by Geoffrey Coad
Created on Feb 16, 2022

Make Obsolete inheritable by it's children in a Class Library

When setting Obsolete on a top level of a class tree all of it's child classes should be set as 'Obsolete' - WorleyParsons/GTC

If a customer is working with a large master Class library which has Classes and Structures not required by every type of project they will want to make certain classes obsolete - and therefore not usable in a specific project.

If you make a Class which has children obsolete - this is not currently inherited by its children. these means that:

  1. The children will remain active until you manually make every child obsolete

  2. Depending on the level this parent it might have a large number of children - meaning the best way may be to export into excel make the changes and upload

  3. The user can't be certain that all children are obsolete until validation is run and succeeds

All of which is a time consuming process and can be resolved by inheriting the Obsolete property within the class structure

  • Attach files