Skip to Main Content
AVEVA™ PI System™ Feedback Portal

Welcome to our 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, 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 and comments are visible to all other users.


This page is for feedback specifically for AVEVA PI System. For links to our other feedback portals, please see the tab RESOURCES below.

Status No Status
Product PI Interfaces
Categories General
Created by Guest
Created on Aug 17, 2022

Customize UniInt Failover Sync File Permissions

Prior to UniInt v4.6.0.60, UFO sync files created during interface startup would inherit file permissions from their parent folder (assuming child inheritance had been enabled on the folder). With UniInt v4.6.0.60, this behavior changed and now sync files created by the interface do not respect inheritance.  Instead, they are created with a standard ACL containing only the local "Administrators" and "Users" security groups. For users with complex file permission schemas, this change introduces additional, unnecessary configuration efforts that scale as interface numbers grow beyond the site-level. 
  • Attach files
  • Shawn McNabb
    Reply
    |
    Aug 17, 2022
    would like to know the use case and design decision for this change. Why does the interface override a system setting for the folder? And why is this listed as an enhancement request if the "enhancement" is restoring previously defined behavior? The behavior is now significantly different, it doesn't appear to follow standard conventions and there doesn't appear to be any documentation explaining the new behavior or reason(s) for the change. It definitely is causing problems for our system and use cases because if the file is ever accidentally deleted or needs to be temporarily or permanently moved, manual intervention will now be needed to create the files, with the correct names, and with the correct (previously inherited) permissions. It no longer is automated and managed (as expected) by the interface. With more than a couple interfaces (we have over 50 easily), management of this is now a nightmare.