> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.3/tags/naming-standards-and-validation-rules.md).

# Naming Standards & Validation Rules

A **Tag** is used to label and classify objects for easier search, grouping, and filtering. Tag names must follow standardized naming rules to maintain consistency and system compatibility.

#### Validation Rules

<table><thead><tr><th width="230.2000732421875">Property</th><th>Value</th></tr></thead><tbody><tr><td>Blank Allowed</td><td>No</td></tr><tr><td>Maximum Length</td><td>Not specified</td></tr><tr><td>Allowed Characters</td><td>Alphabets (A–Z, a–z), Numbers (0–9), Spaces</td></tr><tr><td>Start Character Rule</td><td>Name must start with an alphabet or number</td></tr><tr><td>Disallowed Characters</td><td>Dot (<code>.</code>), Comma (<code>,</code>), configured concatenation delimiter, and special characters such as <code>! @ # $ % ^ &#x26; * _ + : ; &#x3C; > ? / \ " '</code></td></tr><tr><td>Validation Notes</td><td>The system rejects names containing restricted special characters or names starting with special characters</td></tr></tbody></table>

#### Examples

**Valid Examples**

* Sensitive Data
* Finance Tag
* Customer Info
* DataQuality

**Invalid Examples**

* `Tag.Name` → Contains dot
* `Tag,Data` → Contains comma
* `Tag@Data` → Contains restricted special character
* `Tag#1` → Contains restricted symbol
* `#Tag` → Starts with a special character
* `@DataTag` → Starts with a special character

#### System Behavior on Validation Failure

* The system prevents saving the Tag.
* Validation error messages are displayed.
* Correct the name before proceeding.

#### Best Practices

* Keep tag names short and meaningful.
* Avoid unnecessary symbols and special characters.
* Use consistent naming conventions across tags.

## Master Tag

A Master Tag is a standardized tag used across the system to ensure consistent classification and tagging. Master Tag names must follow standardized naming rules to maintain consistency and system compatibility.

#### Validation Rules

<table><thead><tr><th width="234.99993896484375">Property</th><th>Value</th></tr></thead><tbody><tr><td>Blank Allowed</td><td>No</td></tr><tr><td>Maximum Length</td><td>Not specified</td></tr><tr><td>Allowed Characters</td><td>Alphabets (A–Z, a–z), Numbers (0–9), Spaces</td></tr><tr><td>Start Character Rule</td><td>Name must start with an alphabet or number</td></tr><tr><td>Disallowed Characters</td><td>Dot (<code>.</code>), Comma (<code>,</code>), configured concatenation delimiter, and special characters such as <code>! @ # $ % ^ &#x26; * _ + : ; &#x3C; > ? / \ " '</code></td></tr><tr><td>Validation Notes</td><td>The system rejects names containing restricted special characters or names starting with special characters</td></tr></tbody></table>

#### Examples

**Valid Examples**

* PII Data
* Confidential
* Internal Use
* DataSecurity

**Invalid Examples**

* `Tag.Name` → Contains dot
* `Confidential@Data` → Contains restricted special character
* `Tag,Master` → Contains comma
* `#PII` → Starts with a special character
* `@Confidential` → Starts with a special character

#### System Behavior on Validation Failure

* The system prevents saving the Master Tag.
* Validation error messages are displayed.
* Correct the name before proceeding.

#### Best Practices

* Use standardized and reusable names.
* Avoid duplicate or similar tags.
* Maintain consistent naming conventions across the system.

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ovaledge.com/release8.3/tags/naming-standards-and-validation-rules.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.