Because Ventoo Case Management is a generic framework, you name each entity to fit your business: "Case" might be "Job", "Consultation", or "Dossier" for you. This renaming is done via Naming Entries and shipped through a delivered translation app.
Naming Entries
Open Case Management Setup → Naming Entries. Each entry defines a singular and plural form for one entity and one language.
|
Field |
Description |
|---|---|
|
Entity Code |
Code of the entity, e.g. |
|
Language Code |
Language code, e.g. |
|
Singular |
Singular form, e.g. "Case", "Engagement", "Consultation". |
|
Plural |
Plural form, e.g. "Cases", "Engagements", "Consultations". |
|
Group / Sort Order |
Grouping and order for the guided editing in the wizard. |
If an entry for an entity and language is missing, the app uses the English default name. At runtime a helper (naming management) reads these values and composes page titles, action captions, and messages dynamically.
The translation app
The actual display names are not written directly from the naming table into the UI, but shipped through a separate, automatically generated translation app. It contains your naming as a translation file and translates all entity names throughout the application.
You can deploy it two ways:
-
In the setup wizard, step 7, via Deploy Translation & Finish.
-
Later, via the corresponding action in the naming area after you change naming.
Order when redeploying
Keep this order, otherwise the old generator still runs:
Rebuild the base app.
Review/adjust naming.
Deploy the translation app.
Sign out and back in so the new names take effect.
Delivered Swiss German translation
The base app is fully translated into Swiss High German (de-CH). The core entity terms there are:
|
English |
German (de-CH) |
|---|---|
|
Case |
Fall |
|
Engagement |
Mandat |
|
Scope |
Leistungsumfang |
|
Scope Schema |
Leistungsschema |
|
Party |
Beteiligter |
Swiss orthography (no ß) and the formal address form are used. Standard BC terms (Customer, Vendor, Contact, Employee, Resource, Item) follow Microsoft terminology.
Notes
-
Fixed message texts, enum values, and non-entity field captions are intentionally not part of the naming table. Their translation is handled through the app's standard translation files, not through naming configuration.
-
Changing an entity name affects composed captions (e.g. "New Case", "Case Report"), because those fragments insert the configured name.