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 Already exists
Portfolio area Enterprise SCADA Server
Products Administration / Installation Realtime
Created by Brad Tomanik
Created on Jul 31, 2023

RELATED IDEAS

GroupArea in the area table only contains the first 20 groups

Do we actually have a limit of 20 groups per area?

Some testing has shown that one can add more then 20 groups into an area. The GroupAreaJoin table populates all of them correctly however the "group[0-19].name” array-field in the area table only contains 20 groups from the full list found in the groupAreaJoin table.

Expectation

If we are limited to 20 groups, please say that. If not, why does the Area table only contain 20 groups if there are more configured?
Idea business value

Need to know if there is a limit or not, as it will impat some legacy customers who are using this AOR with more than 20 groups.
Idea Type Investigation
Idea priority 3 – Some use to my company
User Persona SCADA Administrator
  • Attach files
  • Admin
    Jake Hawkes
    Reply
    |     Jul 31, 2023

    AOR data is mastered in ADAM, and then periodically synchronised into realtime for use by realtime processes.

    There is no hard limit in ADAM for the number of groups in an area.

    The sync code is limited by the size of the groupArray field in the area table, which is limited to 20 elements, hence the apparant limit.

    However, the data synced to Realtime is not not when determining a users AOR - only data straight from ADAM is used for this.

    In other words, the groupArray field in the Area table should be deprecated, and all users should use natvie ADAM APIs instead.