kris/afv-library
1
0
Fork 0
mirror of https://github.com/forcedotcom/afv-library.git synced 2026-07-30 03:09:50 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
19ee934c67
afv-library/skills/modeling-omnistudio-epc-catalog/references/naming-conventions.md
sandipkumar-yadav 37aa84df42
feat: @W-22444026@ Introducing Core Skills, Datacloud Skills, Industries and Utility Skills. (#268) 
* Migrating Core Salesforce Skills

* Updating pr comments

* updat reference

* Updating a skill

* Migrating Datacloud skills

* Migrating Industries cloud skills

* Validating - skills fixing

---------

Co-authored-by: Sandip Kumar Yadav <sandipkumar.yadav+sfemu@salesforce.com>
2026-05-14 19:32:15 +05:30

1.7 KiB
Raw Blame History

CME EPC Naming Conventions

Use deterministic naming across products, attributes, and offer bundles. Names should remain stable across environments and releases.

Product Name

Format:

<Business Domain> <Tier/Variant> (<Channel or Variant Tag>)

Examples:

  • Business Internet Essential (VPL)
  • Business Internet Premium (FTTC)

Product Code

Format:

<PREFIX>_<ENTITY>_<DOMAIN>_<VARIANT>

Examples:

  • VEPC_OFFERING_BUSINESS_INTERNET_ESSENTIAL
  • VEPC_SPEC_BUSINESS_ROUTER_ADVANCED

Rules:

  • Uppercase with underscores only
  • No environment suffixes (_DEV, _UAT, _PROD)
  • Stable after go-live

Attribute Code

Format:

VEPC_ATTR_<DOMAIN>_<ATTRIBUTE_NAME>

Examples:

  • VEPC_ATTR_DOWNLOAD_SPEED
  • VEPC_ATTR_CONTRACT_TERM

Attribute Category Code

Format:

VEPC_ATTRIBUTE_CATEGORY_<DOMAIN_BLOCK>

Examples:

  • VEPC_ATTRIBUTE_CATEGORY_INTERNET_DETAILS
  • VEPC_ATTRIBUTE_CATEGORY_CONTRACT_DETAILS

Offer Bundle Composition

When naming bundles and child items:

  • Bundle parent ProductCode should indicate offering intent (VEPC_OFFERING_*)
  • Child product codes should represent reusable specs (VEPC_SPEC_* recommended)
  • Sequence values (SeqNumber, ChildLineNumber) should be unique per parent and spaced for future inserts

Anti-Patterns

Bad pattern Why to avoid
Product1, Offer_New, CatalogItemA Non-descriptive and unstable
Mixed abbreviations without glossary Hard to maintain and search
Date/version in ProductCode Breaks long-term references
Same ProductCode in multiple products Downstream ambiguity