Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ System Platform

Define object naming conventions

  • Last UpdatedAug 12, 2024
  • 1 minute read

The second workflow task defines naming conventions for templates, objects, and object attributes. Naming conventions should adhere to:

  • Conventions in use by the company.

  • System Platform IDE naming restrictions. The following are reserved Galaxy and template names and cannot be used as object names:

    • Me

    • MyArea

    • MyContainer

    • MyEngine

    • MyHost

    • MyPlatform

    • System

  • The extension "_New" cannot be used when naming an object, if the name already exists in the Galaxy without the "_New" extension. This is because automatic renaming of imported objects will append an existing object name with the "_New" extension.

  • For more information on allowed names and characters, see the Application Server User Guide.

The following (instance) tagname is used as an example:

YY123XV456

It has the following attributes:

OLS, CLS, Out, Auto, Man

The following figure shows the differences between the HMI and Application Server naming conventions:

Naming Conventions - Differences

Create references using the following IDE naming convention:

<objectname>.<attributename>

For example:

YY123XV456.OLS

Related Links
TitleResults for “How to create a CRG?”Also Available in