App facts
|
Attribute |
Value |
|---|---|
|
Name |
Ventoo Case Management |
|
Publisher |
Ventoo |
|
Version |
1.0.0.1 |
|
App ID |
6388e61e-23c1-44a4-a04d-16c4565e6b93 |
|
Object ID range |
70679910–70680059 |
|
Target application |
Business Central 27.0.0.0 |
|
Runtime |
17.0 |
|
Namespace |
Ventoo.CaseManagement |
|
Dependencies |
none |
Legal references from the manifest: privacy statement, EULA, help/documentation at docs.ventoo.com.
Data classification
All tables and extension fields created by the app are classified as CustomerContent. The app stores business data exclusively in the customer's tenant. Calculated fields (FlowFields) carry no classification of their own, since they are derived at runtime from other fields.
External calls
The app is essentially self-contained. The only outbound call happens optionally as part of the setup wizard:
|
Attribute |
Value |
|---|---|
|
Trigger |
Setup wizard, "Preview" and "Full configuration" steps (only when using the AI suggestions) |
|
Target |
Ventoo configuration service (Azure Function, Switzerland North region) |
|
Data sent |
Company name, website URL, and language code; in the full call also the hierarchy names edited by the user |
|
Purpose |
AI-assisted suggestions for naming, roles, processes, and attributes |
|
Authentication |
API key in the header |
Optionality and fallback: The call is not required. Without company details it is skipped; if the service is unreachable or returns an error, the wizard uses generic defaults and setup continues entirely locally. No case, party, or financial data is transmitted in this call – only the company metadata above.
All other functions (case management, activities, billing, reports, API) run entirely within Business Central without external calls.
Isolated storage
The API key for the setup service is stored in the app's isolated storage (key VTO-CaseMgt-SeedApiKey). If no custom key is stored there, a shipped default key applies. No personal data is stored in isolated storage.
Data flows within Business Central
-
Parties reference BC master data (Customer, Contact, Employee, Vendor, Resource) and store cached name and contact fields for display.
-
Billing generates standard BC sales and purchase invoices; posting runs through BC standard routines. Posted documents produce case ledger entries as a pure analysis ledger.
-
Dimensions are merged from BC master data (Customer, Contact, Employee, Activity) by configurable priority and carried to the G/L postings through the invoice lines.
-
Translations are shipped through a separate translation app deployed in the tenant.
Extensibility and audit trail
-
At key points (case creation, status change, step change, posting, dimension merge), the app publishes integration events for tenant-specific extensions.
-
The change log (Case Change Log) records changes to cases, activities, relationships, and attribute values (enabled in the general settings).
-
Case ledger entries and their reversal/reassignment chains form a complete financial audit trail.