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.

Add a new idea Subscribe
Status Will not implement
Portfolio area Enterprise SCADA Server
Created by Vitali Unke
Created on May 28, 2024

RELATED IDEAS

Deprecate the groupArray field and datatype in the Area table

Big Picture User Experience

Deprecate both the area field and the groupArray type in the realtime schema.

Detailed Description

The groupArray field holds information that was synced from ADAM.

It is currently hard-limited to 20 groups, whereas there is no actual limit in ADAM. As such, the sync code truncates to only 20 groups when syncing this data from ADAM into Realtime.

Since this information is not used to determine a user's actual AOR memberhsip, this field is not needed, and adds to confusion around where to get the actual ADAM configuration.

This deprecation will ensure that those still using this field are warned ahead of time before we actually remove it in a follow-up feature 3 major versions from now.

It must be shown that this information is available via API.


Acceptance Criteria

This will trigger compiler warnings for those still using them.

It must be shown that this information is available via API.


Business Value

None, other than to clean up some technical debt and reduce the amount of dead code in the product, and to prevent developers from making errornous assumptions.


Target Version

Target version for this feature: ES25


Assumptions

Noone/nothing is still using groupArray field in the Area table.

There exists other APIs to get this information that are appropriate for the types of processes that need it.


Dependencies

TBD


Upgradability

No concern


PSR - Performance, Scalability, Resilience

Important PSR aspects for this feature? none


NFR - Non-Functional Requirements

Documentation: Deprecation registy


  • Attach files