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.

Status Future consideration
Portfolio area Enterprise SCADA Server
Created by Jason New
Created on Sep 14, 2023

Document all Configuration JSON files

Global Practice has requested that documentation to catalog the various user-modifiable JSON files and their full list of parameters, potential values, limitations, and most importantly their purpose and effect on the system.

They have also asked for all JSON files to be moved into a database.

It will be a pretty significant effort, and will need alot of work from Tech Pubs and QA.

Expectation

Documentation should include an entry for any JSON file that the project can modify.

Doc should include all details of all config items.

Idea business value

Knowing how to properly configure all configurable aspects of the product reduces TCO and risk for Delivery.

Idea Type Improvement
Idea priority 3 – Some use to my company
User Persona SCADA Administrator, IT/Network Administrator
Work in
OASYS-353 Document all Configuration JSON files
Work status
  • Attach files
  • Admin
    Jake Hawkes
    Reply
    |
    Feb 21, 2024

    There was an innovation days project to create a "Registry Editor", that centralised all the JSON files from throughout the product into a single configuration tool. Might be worth dusting that off and having a look to see what shape it is in, and perhaps include it in the scope for "Common Configuration" initiative.