Overview and Naming Conventions in the Demo Center
Naming Conventions for Data Objects
1. General Guidelines
To ensure a consistent, transparent, and well-structured organization of data objects within the application, standardized naming conventions must be followed.
These conventions are mandatory for all newly created objects and enable clear identification based on company, environment type, language, functional area, and version.
The naming conventions apply to the following object types:
Entities
Perspectives
Sources
Workspaces
2. General Naming Structure
Entities and Perspectives follow the same general naming structure:
company_environment_language_name_specification_version
| Component | Description |
|---|---|
| Company | Name of the company associated with the object. By default, noreja is used. For partner environments, the respective partner company name is used instead. |
| Environment | Defines the intended purpose: demo, training, pov, or production. |
| Language | Language identifier: de for German or en for English. |
| Name | Functional unit or specific end-to-end process, depending on the object type. |
| Specification | Additional identifier to distinguish specific use cases or variations. Represented by xy in the examples. |
| Version | Sequential version number, such as v1, v2, or v3. |
2.1 Environment Types
The following environment identifiers are used:
| Identifier | Description |
|---|---|
demo | Demonstration environment used to showcase functionalities or use cases |
training | Training environment used for educational purposes and exercises |
pov | Proof of Value โ environment used to validate the business value of a solution |
production | Production environment used for actual operational activities |
2.2 General Formatting Rules
The following formatting rules apply to Entities and Perspectives:
All components must be written in lowercase.
Individual components must be separated using underscores (_).
The defined order of components must always be maintained.
Language identifiers must consistently use de or en.
The specification can be defined individually but should be short, meaningful, and clearly identifiable.
The version number must always appear at the end, separated by an underscore.
Sources and Workspaces follow separate naming rules, as described below.
3. Naming Conventions for Entities
Entities are named according to their functional area. For this purpose, predefined functional units are used.
Naming structure:
company_environment_language_unit_specification_version
Examples of functional units include:
sales
purchasing
patientcare
If an Entity combines multiple functional units, they must be separated using a forward slash (/).
Example: sales/purchasing
The specification (xy) allows additional differentiation between use cases, functional variations, or specific configurations within a functional unit.
Examples
| Entity Name | Description |
|---|---|
| noreja_demo_de_sales/purchasing_xy_v1 | German demo Entity combining Sales and Purchasing |
| noreja_training_de_sales_xy_v1 | German training Entity for Sales |
| noreja_pov_de_purchasing_xy_v1 | German PoV Entity for Purchasing |
| noreja_demo_de_patientcare_xy_v1 | German demo Entity for Patient Care |
| noreja_demo_en_patientcare_xy_v1 | English demo Entity for Patient Care |
| noreja_production_de_sales_xy_v1 | German production Entity for Sales |
Important: Functional unit names must be used consistently. When combining multiple units, the forward slash (/) must always be used as the separator.
4. Naming Conventions for Perspectives
Perspectives follow the same general naming structure as Entities. However, the main difference lies in the naming of the functional component.
While Entities are named according to predefined functional units, Perspectives must be named according to specific end-to-end processes.
Naming structure:
company_environment_language_end_to_end_process_specification_version
The process name must represent the complete business process rather than an individual functional area.
Examples of end-to-end processes include:
order_to_cash
purchase_to_pay
admission_to_discharge
Individual words within the process name must be separated using underscores.
Examples
| Perspective Name | Description |
|---|---|
| noreja_demo_de_order_to_cash_xy_v1 | German demo Perspective for Order-to-Cash |
| noreja_training_de_order_to_cash_xy_v1 | German training Perspective for Order-to-Cash |
| noreja_pov_de_order_to_cash_xy_v1 | German PoV Perspective for Order-to-Cash |
| noreja_demo_de_admission_to_discharge_xy_v1 | German demo Perspective for Admission-to-Discharge |
| noreja_demo_en_purchase_to_pay_xy_v1 | English demo Perspective for Purchase-to-Pay |
Important: Perspectives must always use the specific end-to-end process name. General functional unit names such as sales or purchasing should not be used as substitutes for process names.
5. Naming Conventions for Sources
Sources follow a simplified naming convention.
The Source name must exactly match the name of the underlying database (1:1).
No additional prefixes, suffixes, or version identifiers should be added unless they are already part of the original database name.
This ensures a clear and consistent relationship between the Source within the application and its corresponding database.
6. Naming Conventions for Workspaces
Workspaces use a more readable naming format. Unlike Entities and Perspectives, underscores are not used.
The Workspace name generally consists of the environment type followed by the corresponding end-to-end process name.
Naming structure:
Environment Process-Name
Common environment identifiers include Demo and PoV.
Process names are written in a readable format, with individual words separated by hyphens.
Examples
| Workspace Name | Description |
|---|---|
Demo Order-To-Cash | Demo Workspace for the Order-to-Cash process |
PoV Purchase-To-Pay | Proof of Value Workspace for the Purchase-to-Pay process |
Demo Admission-To-Discharge | Demo Workspace for the Admission-to-Discharge process |
Important: Workspace names should be immediately understandable to users. Therefore, technical naming formats using underscores must not be used.
7. Summary of Naming Conventions
| Object Type | Naming Structure | Example |
|---|---|---|
| Entity | Company + Environment + Language + Functional Unit + Specification + Version | noreja_demo_de_sales_xy_v1 |
| Perspective | Company + Environment + Language + End-to-End Process + Specification + Version | noreja_demo_de_order_to_cash_xy_v1 |
| Source | Exact name of the underlying database | Identical to database name |
| Workspace | Environment + Readable Process Name | Demo Order-To-Cash |
All newly created data objects must comply with these naming conventions to ensure consistency, clarity, and maintainability across the application.
Existing objects should also be aligned with these standards whenever they are updated or versioned.