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 Will not implement
Portfolio area Production Management (AMPLA MES)
Created by Nina NICHOLLS
Created on Feb 22, 2021

RELATED IDEAS

Ampla to provide more informative error messages/stack traces for code items

https://schneiderampla.atlassian.net/browse/CE-2067



[Enhancement Request]

The Rio Tinto CLDBDT and OCDT Ampla Systems are quite large and complex. As part of the Ampla Upgrade to 7.3, Rio Tinto were undertaking significant amount of work to reduce the number of exceptions that are reported. However, in certain, circumstances, they found it difficult to isolate the item that produces exceptions due to the lack of information. One such example is the following error:

_The following information was included with the event (insertion strings):
SampleStream:this[int index] invalid index -1, count 27639_

The error is produced by Citect.Ampla.Runtime.Data.Streams.Streams class:


The Rio Tinto project has wrapped their custom code that might cause this exception but they still get these errors. So, the enhancement request is for Ampla to provide better error information. For instance, with this example, it would be beneficial to have a full stack trace, along with targeted information such as the name of the stream and the object that called it.

  • Attach files
  • Admin
    Nina NICHOLLS
    Reply
    |     Sep 21, 2023

    Code items are intended for simple extension scenarios, there is the ability to add trace logging messages for these scenarios. For more complex scenarios the recommended best practise is to create a separate service that runs independently to Ampla.