AVEVA™ PI System™ 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, 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.

Add a new idea Subscribe
Status Declined
Product PI Connectors
Categories PI Connector for UFL
Created by Kenneth Barber
Created on Aug 18, 2022

RELATED IDEAS

Be able to point the PI Connector for UFL to INI files

Please allow INI files to be pointed to by saving their full path, just like the PI Interface for UFL, rather than saving a copy of an uploaded INI file. This makes editing, testing, debugging, etc. much easier.
  • ADMIN RESPONSE
    Aug 18, 2022
    The proposed solution in this request is not advisable for security reasons. The current process ensures that the change to the parsing file is accomplished with credentials that allow administration of the connector. The question I have is what is the underlying problem that fostered this solution? If it is something like it is hard to deploy updates to the parsing script (.ini file) and maybe this is especially challenging during development, then that idea would be worth capturing for sure.
  • Attach files
  • Gabriel Verreault
    Reply
    |     Aug 18, 2022
    Since the connector can be managed remotely (web admin ui), then saving the INI as a path is not ideal in my opinion.
  • Mic Paluszak
    Reply
    |     Aug 18, 2022
    From my experience, deploying a UFL Connector solution requires a LOT of edits of the INI file as part of the development/testing/debugging process. After each INI file change, the required procedure is as follows: 1. Click on the Data Source List link. 2. Click on ‘See Configuration’. 3. Click on the ‘Change’ button. 4. Click on the ‘Browse…’ button. 5. Double-click on the INI file. 6. Scroll the page down until the ‘Save’ button is visible (I’m using a 1920 x 1080 monitor). 7. Press the ‘Save’ button. 8. Click on the ‘Overview’ link. 9. Press the ‘Start connector’ button. I think any enhancements to make the above process less tedious would be welcome.