Harrier Open Standards
  • Open Standards
  • Technical
    • Best Practices
      • Naming conventions
        • Object / Metadata Type / Settings Conventions
        • Custom Permissions Conventions
        • Profile Conventions
        • Permission Set (Group) Conventions
        • Apex Style Guide
      • Feature flags
    • Documentation
      • GPT Instructions
    • Frameworks
      • flxbl - Continuous Delivery
      • fflib - Apex Framework
      • Nebula Logger - Logging
    • Integration Strategies
      • Data warehouse & Reverse ETL
    • Development & Deployment Strategies
  • Functional
    • Requirement definition
      • GPT Instructions
    • Documentation
Powered by GitBook
On this page

Was this helpful?

  1. Technical
  2. Best Practices
  3. Naming conventions

Object / Metadata Type / Settings Conventions

PreviousNaming conventionsNextCustom Permissions Conventions

Last updated 1 year ago

Was this helpful?

All Naming Conventions Are and compliant.

  1. All API names MUST be written in English, even when the label is in another language.

  2. All API names MUST be written in PascalCase.

  3. Objects SHOULD NOT contain an underscore in the objects name, except where explicitly defined otherwise in these conventions.

  4. Objects generally MUST (but you probably won't) contain a description.

  5. In all cases where the entire purpose of the object is not evident by reading the name, the object MUST contain a description.

  6. Junction object API names MUST be singular (not pluralized) and contain the API names of both objects.

RFC 2119
RFC 6919