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 Planned
Portfolio area Application Server & OMI
Products IDE
Created by Ernst van Wyk
Created on Jul 28, 2024

Properly handling default values and locks in the IDE

Currently users use the lock functionality to set a default value for an attribute but this locks the value at instance level and at every template level in between the configured template and the instances. It means that users need to go back and unlock every one of these template levels separately - each time waiting for the full check-in of all derived templates and instances - this has a severe negative impact on productivity.

The proposal is to add a new lock type (an open lock with a down arrow - known as default)

  • Open lock behaviour remains the same:

    • No value propagated to derived templates/objects on check-in.

    • The value can be changed in runtime.

  • Closed lock behaviour remains the same:

    • The value is propagated to derived templates/objects on check-in.

    • The value cannot be changed in runtime.

  • Default (Open lock with arrow)

    • This introduces a new behaviour

      • The value is propagated to derived templates/objects on check-in.

      • The value can be changed in runtime.

    • This behaviour is a one-time behaviour:

      • The Default (unlocked with arrow) becomes a standard unlocked value after the check-in is completed

      • Derived templates and instances become standard unlocked values

The folowing behaviou is introduced:

  • Any open lock can be changed to Default (unlocked with arrow)

    • This propagates the value on check-in.

    • But the value can be changed in runtime.

  • A top level lock can be changed to Default (unlocked with arrow)

    • This propagates the value on check-in.

    • It also propagates the lock state to unlocked for all derived tempaltes and instances

    • But the value can be changed in runtime.

  • An inherrited lock cannot be changed

Note that the default setting only propagates once, when it is checked in. All the derived templates and instances have there values changed, and their locks set to standard unlocked. The Default setting is not stored with any templates. The next time a template with Defaults are opened the lock is a standard unlocked value.

  • Attach files
  • Danny Power
    Reply
    |
    Nov 6, 2024

    Need to also separate out security mode propagation locking from attribute value locking

  • Jim MacDonald
    Reply
    |
    Aug 5, 2024

    Yes, this is confusing to new people

  • Jakob Drescher
    Reply
    |
    Jul 31, 2024

    This is something that always needs to be explained twice for new SP engineers at the training course. A 3-option padlock would make it much easier to explain what is happening.