TDX, U of I Main Naming Conventions
This document explains naming conventions for each item within the U of I Main ticketing application. This covers standards for both UIUC and System Offices groups within the application. Application Admins should review and adhere to these conventions so that items are consistent and easy to manage. These have set by Technology Services and the U of I Main Advisory Group.
These are the decided naming conventions for the Groups in U of I Main:
UIUC Tech Services = TechSvc
Attributes
- [Campus]-[Group]-[Sub Group]-[Attribute Description]
- Campus = System or UIUC
- The Sub Group is only necessary if a Sub Group exists.
- Attribute Header Names should also follow this convention; however, the Campus/Unit names can be abbreviated as necessary.
- Example for header text for attribute: TechSvc = TS
Attribute Dependencies
- Parent Attribute Name -> Child Attribute Name
Automation Rules
- [Campus]-[Group]-[Sub Group]-[Automation Rule Description]
Email Monitor Names
- [Campus]-[Group]-[Sub Group]-[email address being monitored]
Forms
- [Campus]-[Group]-[Sub Group]-[Form Name]
Operational Hours
- [Campus]-[Group]-[Sub Group]-[Description]
Response Template
- No convention – All templates should be sorted into the appropriate category.
Response Template Categories
- [Campus]-[Group]-[Sub Group]-[Category Name]
Service Level Agreements (SLA)
- [Campus]-[Group]-[Sub Group]-[SLA Description]
Task Templates
- [Campus]-[Group]-[Sub Group]-[Description]
Webhooks
- [Campus]-[Group]-[Sub Group]-[Description]
Workflow Web Services
- [Campus]-[Group]-[Sub Group]-[Description]
Workflows
- [Campus]-[Group]-[Sub Group]-[Description]