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 Shipped
Portfolio area Enterprise SCADA Server
Products Compile / Build
Created by Gerald Tseng
Created on Apr 8, 2022

RELATED IDEAS

Create DNASourceRoot environment variable once during installation

The Initialize-DevEnvironment.ps1, line 59, creates or modifies the DNASourceRoot environment every time it is run. As a developer, the location of my latest DNASourceRoot may not be the folder that I would like to use. For example, I would like to keep the configurations for each system in the DNASourceRoot for reference and deployment. I have 4 systems and they are D:\ProjectSource\PPRD, D:\ProjectSource\SPRD, D:\ProjectSource\PPRDDSS, and D:\ProjectSource\SPRDDSS. I also have a folder called D:\ProjectSource\Development for application developments. When I go to do my work, I would like to go to D:\ProjectSource first so that I can get to this folder and then navigate to the one that I would like to work on or generate an MSI. The D:\ProjectSource should also be the central location for all users to create applications for easy management.

The current script creates or updates the DNASourceRoot every time the script is run and is created per user. This environment variable is viewable in the RegEdit only for user with no Administrative permission and every user can create their own DNASourceRoot. At the end of the day, you may have 5 different DNASourceRoot directory for 5 different users rather than 1 central location. It becomes really confusing.

Expectation

A line is added to Initialize-DevEnvironment.ps1 above 59 to check if DNASourceRoot already exist or not. An administrator or dnaInstaller should run this command first to create the entry. The MACHINE option should be used rather than the USER such that this becomes a System environment variable rather than a user environment variable.
Idea business value

Forcing everyone to put everyone to use the same directory for application development and generate sub-folders inside DNASourceRoot to handle different structures.
Idea Type Improvement
Idea priority 4 – Important to my company
Work in
OASYS-580 Relocate Development Environment Scripts to Practice
Work status
Release
Enterprise SCADA 2023
Release date
Jan 31, 2023
  • Attach files
  • Admin
    Jake Hawkes
    Jul 10, 2023

    These scripts were relocated from product to practice, and are maintained there as part of their standardised deployment processes.

    Reply
1 MERGED

Initialize-DevEnvironment.ps1 provide option to create bin as junction or not

Merged
When Initialize-DevEnvironment.ps1 is executed, the bin directory is always a junction between DNADataRoot and DNASourceRoot. With the Extensions team deploying their files to DNADataRoot, packing a project MSI also includes the binaries from Exte...
Gerald Tseng about 4 years ago in Enterprise SCADA Server / Compile / Build Shipped