Manual > Appendix > Naming Conventions

Naming Conventions

Naming rules for Panel Server

•Unit name

•Folder name

•Tag name

•Event name

•Action name

•Action child item name

•View name

When setting each name, please note the following:

1)Recommended characters are letters (A-Z, a-z), numbers (0-9), and underscores (_).

2)( # )( . )( / )( ! ) cannot be used.

3)Half-width characters other than the recommended characters in 1, and full-width characters may be subject to restrictions depending on the function used, so they are not recommended.

4)The first character cannot be a number or an underscore (_).

5)The name must be 50 characters or less.

The reason why we do not recommend naming is that although you can register the tag, it may not be usable in other scenarios. If the tag name is changed, it may affect other scenarios, so please be careful when naming.

There are other usage scenarios where it may not be possible to use the service.

•A problem may occur with the bind expression of Panel Browser.

•There is also a possibility that future expansions may cause problems.

Examples include:

•Environment variables

When setting environment variables, please pay attention to the following points. Also, when setting environment variables, it will be easier to see whether an environment variable is being used by establishing rules such as enclosing the environment variable name in [].

1)Do not use any characters other than letters (A-Z, a-z), numbers (0-9), underscores (_), and square brackets ([]).

Naming rules for Panel Editor / Panel Browser

Object name

The name of the object is set in the "Name" property. When naming an object, please note the following:

1)The first character should only be an alphabet (A-Z, a-z) or an underscore (_).

2)After the first character, only letters (A-Z, a-z), numbers (0-9), and underscores (_) can be used.

3)Full-width characters (such as kanji) cannot be used.

4)It cannot contain spaces.

Object names can be duplicated, but as a general rule, avoid duplicate object names within the same hierarchy (even if duplicate object names exist, no errors will be displayed). If an absolute path reference is made when multiple objects have duplicate names, there is no guarantee which control will be referenced among multiple controls with duplicate names.

Custom property name

Every object has custom properties that you can add to it however you like.When setting custom property names, keep the following in mind:

1)The first character should only be an alphabet (A-Z, a-z) or an underscore (_).

2)After the first character, only letters (A-Z, a-z), numbers (0-9), and underscores (_) can be used.

3)Full-width characters (such as kanji) cannot be used.

4)It cannot contain spaces.

To avoid duplication with existing property names, start withUnderscore ( _ )We strongly recommend that you create the property with rules such as adding the following. New properties may be added in future version upgrades. Please consider this in preparation for such cases.

Bind

Regarding tag names and other strings used in bindings, note the following:

1)You cannot use the same characters as the operator symbols defined in "Operators that can be used in binding".
*However, it can be used if the tag name is enclosed in single quotation marks (') as shown below.

'U01.F01.TAG-01' //If it contains a "-" sign

'U01!Alive' // System properties for tags (e.g. '!')

'U01.F01.#SD0000+FIL=LIN:0|1|0|100' //When using the Active tag filter

2)blank character. Example: "TAG 01"

3)"" double quotation marks and "'" single quotation marks Example: "TAG"02""

4)The first character cannot be a number. Example: "123TAG".

5)The first character cannot be an underscore. Example: "_TAG01".

It can be used by changing the PSTagDirectPathMark route property to a character other than "_".

For more information, see "Route Properties".

6)Full-width characters. Example: "U01.F01.Pump 1"

Although not all full-width characters can be used, there are cases where they cannot be used depending on the character code, so full-width characters are not recommended.

User-defined functions

When defining a user-defined function in a script (SC2), please note the following:

1)The first character should not be any alphabet or underscore (_).

2)After the first character, only letters (A-Z, a-z), numbers (0-9), and underscores (_) can be used.

3)Full-width characters (such as kanji) cannot be used.

4)It cannot contain spaces.

5)Reserved words reserved in scripts cannot be used.

6)Operator characters are not allowed.

Variable

When defining variables in the script (SC2), please note the following:

1)The first character should not be any alphabet or underscore (_).

2)After the first character, only letters (A-Z, a-z), numbers (0-9), and underscores (_) can be used.

3)Full-width characters (such as kanji) cannot be used.

4)It cannot contain spaces.

5)Reserved words reserved in scripts cannot be used.

6)Operator characters are not allowed.

Reserved Words

The script (SC2) has the following reserved words. These cannot be used as variable names, etc.

•break	•case	•continue
•default	•else	•for
•function	•if	•new
•return	•switch	•this
•var	•while	•parent
•event	•c	•T
•F	•TRUE	•FALSE