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

Property	Value
Blank Allowed	Not explicitly checked
Max Length	255 characters
Allowed Characters	No character restrictions
Disallowed Characters	None
Start Character Restriction	None
Regex / Notes	Only length validation is applied

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.