# Naming Standards & Validation Rules

A Project Task represents an individual unit of work within a project. It can be associated with data objects such as tables, terms, and reports, or created independently to track governance, curation, and review activities.

#### Validation Rules

<table><thead><tr><th width="235.00006103515625">Property</th><th>Value</th></tr></thead><tbody><tr><td>Blank Allowed</td><td>Not explicitly checked</td></tr><tr><td>Max Length</td><td>255 characters</td></tr><tr><td>Allowed Characters</td><td>No character restrictions</td></tr><tr><td>Disallowed Characters</td><td>None</td></tr><tr><td>Start Character Restriction</td><td>None</td></tr><tr><td>Regex / Notes</td><td>Only length validation is applied</td></tr></tbody></table>

#### Supported Character Types

* Alphabets (A–Z, a–z)
* Numbers (0–9)
* Spaces
* Special characters and symbols

#### Validation Behavior

* Accepts any character combination.
* Supports free-form descriptive text.
* Does not validate:
  * Special characters
  * Character patterns
  * Starting or ending characters
  * Character sequences
* Validates only the maximum length of 255 characters.

#### Valid Examples

* Data Quality Check
* Validate Customer Table Data
* Fix Null Values in Orders\_Table
* Task #101 - API Validation
* Review Data @ Monthly Cycle
* !! Urent Task - Cleanup Required
* Check schema consistency (Phase-1)
* Task\_with\_special\_chars\_@#$%^&\*()

#### Invalid Examples

* Task names exceeding 255 characters

#### System Behavior on Validation Failure

* Prevents saving the Project Task if the name exceeds 255 characters.
* Displays a validation error message.
* Requires correction before saving.

#### Best Practices

* Use clear and meaningful task names.
* Follow structured naming patterns where possible.
  * Example: `<Action> + <Object>`
  * Example: Validate Sales Data
* Avoid excessively long names for better readability.
* Use special characters only when required.
* Maintain consistent naming standards across Project Tasks.

***

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


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ovaledge.com/release8.1/projects/naming-standards-and-validation-rules.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.