Velox Knowledge Map
This document groups the Velox codebase into logical subsystems. It is intended as a navigation aid for future development, review, and onboarding.
Complexity is estimated from code surface area, coupling, runtime risk, database impact, threading, persistence compatibility, and number of dependencies. It is not a formal metric.
Related documentation is now split across the PKB topic files in this folder, including architecture, domain model, feature inventory, module library, flow execution, API, services, UI/dialog/menu inventories, database, logging, security, errors, data formats, and configuration references. _Documentation contains user-maintained topic notes and is referenced only where those notes add context outside the PKB.
Runtime Entrypoints and Project Composition
Purpose:
- Defines the main executable boundaries and process roles for Velox Designer, VeloxService, VeloxAPIService, and VeloxTest.
- Sets global runtime flags such as Designer/server/background/test mode.
- Performs early memory manager, exception reporting, connection, setup, logging, and database-upgrade initialization.
Main classes:
TMainTVeloxWorkerTVeloxAPIWorker- VeloxTest main form
- Global startup helpers such as
CheckTrial,CreateSystemLog,CheckDatabaseUpgrade,SwitchSystemConnectionMode
Dependencies:
- VCL application/service framework
- Modified
Vcl.SvcMgr - FastMM5
- madExcept
vxConvxSetupvxDBUpdatevxConfigPathvxModule
Important entry points:
Velox.dprVeloxService.dprVeloxAPIService.dprVeloxTest.dprVeloxGroup.groupproj
Important configuration:
- Command-line connection key parameter
- Test mode command-line flags
AppDataFolder.cfgConnections.jsonVX_SETUPvxConstant.MajorVersion
Related documentation:
ARCHITECTURE.md: Overall Architecture, Purpose of Each Major Project, Startup Sequence
Estimated complexity: Medium
Velox Designer GUI
Purpose:
- Provides the Windows GUI for designing, configuring, importing, exporting, testing, and managing Velox flows and modules.
- Manages the main tree, form lifecycle, Designer mode changes, and service control UI.
Main classes:
TMainTvxModuleManager- Form manager classes under
Classes\GUI - Designer forms under
Forms - Flow setup forms under
Forms - Transport configuration forms under
Forms\Transports
Dependencies:
- VCL
- DevExpress VCL controls
- Custom components under
Components TvxModuleManagergServiceManagergSystemConnectiongSetupgVariableGroups- IPC/service manager code
Important entry points:
Velox.dprForms\frmMain.pasTMain.FormCreateTMain.InitialiseFormTMain.ChangeMode- Designer menu actions, including
Tools > Sync RelationsandTools > Create XSD
Important configuration:
- Active system connection key
- Test/production mode
VX_SETUP- Module tree/folder configuration
- Service state and service names
Related documentation:
ARCHITECTURE.md: Velox Designer, Startup Sequence_Documentation\_Development
Estimated complexity: High
Configuration and ProgramData
Purpose:
- Resolves application data paths.
- Loads the active system database connection configuration.
- Loads general Velox setup from the configuration database.
- Supplies filesystem locations for config, logs, data, files, schemas, scripts, resources, certificates, temp files, and comparison output.
Main classes:
TvxConnectionTvxDBParamsTvxSetup- Path helper functions in
vxConfigPath
Dependencies:
- SuperObject JSON
vxEncryptionvxConstantvxConfigvxDBParams- Windows known folders and common application data paths
Important entry points:
gSystemConnection.LoadSwitchSystemConnectionModeTvxSetup.CreateAndLoadTvxSetup.Reload- Path accessors in
Classes\Tools\vxConfigPath.pas
Important configuration:
AppDataFolder.cfgC:\ProgramData\Velox\Config\Connections.json- Installer ProgramData template at
C:\_GIT\Velox\Install\ProgramData\install-veloxprogramdata VX_SETUPConfig,Log,Data,Files,Files_Test,Temp,Schema,Script,Resource,Certificate,Compare
Related documentation:
ARCHITECTURE.md: Configuration Loading_Documentation\OpenSSL
Estimated complexity: Medium
Database Connectivity and Connection Pools
Purpose:
- Connects Velox to SQL Server.
- Provides per-thread pooled connections for system databases and business data connections.
- Supports query creation, transaction handling, and ReportBuilder database settings.
Main classes:
TvxDBParamsTvxSQLConnectionTvxSystemConnectionPoolTvxSQLConPoolTvxSystemDBTvxDBConTvxSQL
Dependencies:
- Microsoft SQL Server
- Devart dbExpress SQL Server driver
dbexpsda41.dll- OLE DB provider settings
- ReportBuilder data settings and pipelines
Connections.jsonVX_DBCON
Important entry points:
TvxSQLConnection.VxConnectTvxSQLConnection.NewQueryTvxSystemConnectionPool.LoadgSysConPool.GetConnectiongSQLConPool.GetConnectionTvxSystemDB.NewConfigQueryTvxSystemDB.NewLogQueryTvxSystemDB.NewDataQuery
Important configuration:
Connections.jsonTvxDBParams- Config, log, and data database keys
- Windows or SQL authentication settings
- Encrypted database passwords
- Trust server certificate setting
Related documentation:
ARCHITECTURE.md: Database Access Architecture
Estimated complexity: High
Database Schema Upgrades
Purpose:
- Owns all Velox database schema changes.
- Creates and upgrades
VX_*tables and indexes. - Tracks the current schema version through
VX_VERSION.
Main classes:
TVxDBUpdateTVxDBUpdateVersionTVxDBUpdateVersion300throughTVxDBUpdateVersion311TDatabaseUpgrade
Dependencies:
TvxSQLConnectionTvxSQLvxConstant.MajorVersionvxDBUpdateVersion- Designer modal upgrade UI
Important entry points:
CheckDatabaseUpgradeTVxDBUpdate.CheckDatabaseVersionTVxDBUpdate.UpdateDatabaseTVxDBUpdate.UpgradeToTVxDBUpdateVersion.Execute
Important configuration:
vxConstant.MajorVersionVX_VERSION- Config and log database connections
Related documentation:
ARCHITECTURE.md: Database Access Architecture, Areas of Technical Debt
Estimated complexity: Medium
Module Persistence and Compatibility
Purpose:
- Provides the base persistence model for Velox configuration objects.
- Loads and saves module metadata and streamed module configuration.
- Preserves compatibility with old module class names and missing streamed properties.
Main classes:
TvxModuleTvxModuleTemplateTvxModuleManagerTModuleOwnerTvxConfigTemplateConvertOldClass
Dependencies:
- ReportBuilder
TppTemplate - Delphi class registration
TvxSystemDBVX_*module tablesVX_RELATION- Missing property logging
Important entry points:
TvxModule.LoadModuleTvxModule.AddModuleTvxModule.SaveModuleTvxModule.ExportModuleTvxModule.SaveModuleRelationsTvxModuleTemplate.LoadErrorTvxModuleTemplate.FindComponentClassTools > Sync Relations.cfgimport/export paths
Important configuration:
- Module table names
- Module FIDs and parent FIDs
- Active/archive flags
- Revision/version/test/prod metadata
.cfgexport filesVX_RELATION
Related documentation:
ARCHITECTURE.md: Plugin and Module Architecture, Serialization Formats
Estimated complexity: High
Flow and Action Model
Purpose:
- Represents a Velox Flow as an ordered set of executable action items.
- Defines the persisted business process that moves, transforms, validates, reports, and integrates data.
Main classes:
TvxActionManTvxActionItemTvxActionMapTvxActionReportTvxActionCustomScriptTvxActionTransportTvxActionAPI(source-visible transport-derived subclass; no current class registration or main setup creation path was found)TvxActionFileRouterTvxActionShellExecuteTvxActionSQLTvxActionSubActionTvxRouteItem
Dependencies:
- Module persistence
- Maps
- Reports
- Scriptlets
- Transports
- Database/file definitions
- Variable groups
- Logging
- Connection pools
Important entry points:
TvxActionMan.ExecuteTvxActionMan.ExecuteOnceTvxActionMan.CheckTransportsTvxActionMan.LoadLinkedActions- Designer action configuration forms
Important configuration:
VX_ACTION- Flow execution type, including scheduled, monitored, and REST/API execution
- Action order and active flags
- Retry behavior
- Linked actions
- Test mode
Related documentation:
ARCHITECTURE.md: Flow Execution Architecture
Estimated complexity: High
Service Execution Managers and Threading
Purpose:
- Runs service-managed flow execution.
- Synchronises database-defined work into active service runtime items.
- Starts, limits, tracks, and shuts down worker threads.
Main classes:
TvxExecutionManagerTvxExecutionItemTvxScheduleManagerTvxScheduleItemTvxMonitorManagerTvxMonitorItemTvxTransportManagerInTvxTransportManagerOutTvxRESTManagerTvxExecutionMonitorTActionThreadTScheduleActionThreadTMonitorActionThreadTTransportInActionThreadTTransportOutActionThreadTRESTActionThreadTvxStopWaitThread
Dependencies:
VeloxServiceVeloxAPIServiceTvxActionPoolTvxModuleOwner- Connection pools
- Logging
- Timers
- IPC
- COM initialization
Important entry points:
TVeloxWorker.ServiceExecuteTVeloxAPIWorker.ServiceExecute- Manager
Synchronisemethods - Manager
Disablemethods - Thread
Executemethods - Service shutdown paths
Important configuration:
gSetup.ServiceState- Schedule and repeat timings
- Max pending/running threads per action
gSetup.MaxWaitBeforeTermination- Transport retry settings
- Execution type on flows/actions
Related documentation:
ARCHITECTURE.md: VeloxService Startup, VeloxAPIService Startup, Flow Execution Architecture, Areas of Technical Debt
Estimated complexity: High
REST API Service Dispatch
Purpose:
- Hosts REST/API-triggered flows in the Delphi
VeloxAPIService. - Maps HTTP endpoints to active REST flow execution items.
- Dispatches WebBroker requests into Velox flow execution.
Main classes:
TVeloxAPIWorkerTRESTModuleTvxRESTManagerTvxRESTItemTRESTActionThreadTvxAPIRequestTvxAPIResponse
Dependencies:
- WebBroker
- Indy
TIdHTTPWebBrokerBridge TvxActionPoolTvxActionMan- API stream wrappers
- Logging
- Connection pools
gSetup
Important entry points:
VeloxAPIService.dprTVeloxAPIWorker.ServiceStartTVeloxAPIWorker.ServiceExecuteRegisterWebModuleTRESTModule.WebModuleBeforeDispatchTvxRESTManager.SynchroniseTvxRESTManager.ExecuteAPIForEndpoint
Important configuration:
- API domain
- API port
- API SSL setting
- REST endpoint path
VX_ACTIONrows withfstRESTX-UserNumrequest header
Related documentation:
ARCHITECTURE.md: VeloxAPIService Startup, Flow Execution Architecture, Architecture Questions
Estimated complexity: High
API Definitions and OpenAPI Schema
Purpose:
- Groups REST flows into API definitions.
- Generates OpenAPI JSON schemas for REST API documentation.
- Supplies schema output to the separate C# IIS VeloxAPIService frontend.
Main classes:
TvxAPITvxAPIActionItem- OpenAPI schema generation methods in
TvxAPI
Dependencies:
TvxActionMan- REST execution type
fstREST - System.JSON
- Neon JSON serialization
- OpenAPI-Delphi
- C# IIS VeloxAPIService frontend
Important entry points:
- API module configuration in Designer
TvxAPI.CreateOpenAPISchemaTvxAPI.ExportOpenAPISchema- Linking REST flows into
TvxAPIActionItem
Important configuration:
VX_APIVX_API_ACTION- REST flow endpoints
- AppData resource/schema output paths
- C# frontend schema load process
Related documentation:
ARCHITECTURE.md: Flow Execution Architecture, Serialization Formats
Estimated complexity: Medium
C# IIS VeloxAPIService Frontend
Purpose:
- Acts as the current IIS-hosted gateway/frontend to the Delphi
VeloxAPIService. - Currently handles SSL termination.
- Loads OpenAPI schema generated by
TvxAPIso it can present Swagger/API documentation.
Main classes:
- Not visible in this repository.
Dependencies:
- IIS
- C#/.NET project outside this repository
- Generated OpenAPI JSON from Velox
- Delphi
VeloxAPIService - SSL certificate configuration in IIS
Important entry points:
- IIS application startup outside this repository
- Schema load path outside this repository
- Gateway calls into the Delphi API service
Important configuration:
- IIS site/application settings
- SSL certificate binding
- Generated OpenAPI schema location
- Delphi API service address and port
Related documentation:
ARCHITECTURE.md: Flow Execution Architecture, Architecture Questions
Estimated complexity: Medium
Transports
Purpose:
- Implements inbound and outbound integration transports.
- Allows flows to receive, monitor, send, retry, and log transport activity.
Main classes:
TvxTransportTvxTransportLinkTvxTransportFTPInTvxTransportFTPOutTvxTransportSFTPInTvxTransportSFTPOutTvxTransportLANInTvxTransportLANOutTvxTransportHTTPInTvxTransportHTTPOutTvxTransportMSMQInTvxTransportMSMQOutTvxTransportIBMMQInTvxTransportIBMMQOutTvxTransportIMAPTvxTransportPOPTvxTransportSMTPTvxTransportManagerInTvxTransportManagerOut
Dependencies:
- Indy
- SecureBridge/SFTP components
- MSMQ/IBM MQ support where configured
- File connections
- Flow execution
- Logging
- Service managers
Important entry points:
- Transport action execution
TvxTransportManagerIn.SynchroniseTvxTransportManagerOut.SynchroniseTTransportInActionThread.ExecuteTTransportOutActionThread.Execute- Transport
StartDownloadand outbound execute/send methods
Important configuration:
VX_TRANSPORT- Transport direction
- Transport retry settings in setup
- File connection FIDs
- Transport log tables
Related documentation:
ARCHITECTURE.md: Flow Execution Architecture, Logging_Documentation\AS2_Documentation\OAuth SMPT SASL
Estimated complexity: High
Data Definitions and File Engines
Purpose:
- Defines structured access to database data and files.
- Reads and writes flat, XML, JSON, EDI, and Excel formats.
- Supplies data views and datasets used by maps, reports, scripts, and actions.
Main classes:
TvxDBDefTvxFileDefTvxFileDefFlatTvxFileDefXMLTvxFileDefJSONTvxFileDefExcelTvxFileDefEDITvxDataDefTvxDefManagerTvxDefDBTvxDefFileTvxFileEngine- Flat, XML, JSON, Excel, and EDI file engine classes
Dependencies:
- SQL connection pools
- File connections
- NativeExcel
- NativeXML/MSXML
- System.JSON and custom JSON helpers
- XML schema files under ProgramData
Schema - API request/response streams
Important entry points:
- File/data definition Designer forms
- File engine load/save methods
- API stream load paths
- Map/report/action data access
Important configuration:
VX_DBDEFVX_FILEDEF- File type settings
- Delimiter/fixed-width settings
- XML schema and transform settings
- Excel workbook/template settings
- ProgramData
Schema,Files,Files_Test, andTempfolders
Related documentation:
ARCHITECTURE.md: Serialization Formats_Documentation\Fast Delphi Code
Estimated complexity: High
Mapping and Transformation
Purpose:
- Maps fields between definitions, views, files, databases, scripts, variables, and runtime data.
- Implements core data transformation behavior for Velox flows.
Main classes:
TvxMapTvxViewMapTvxFieldMapTvxActionMap
Dependencies:
- Database definitions
- File definitions
- Scriptlets
- Variables
- Logging
- Module relations
- Connection pools
Important entry points:
TvxActionMapexecution- Map Designer forms
TvxModule.SaveModuleRelations- Map import/export
Important configuration:
VX_MAP- Source and target definition FIDs
- Field mappings
- Scriptlet and variable relations
VX_RELATION
Related documentation:
ARCHITECTURE.md: Flow Execution Architecture, Plugin and Module Architecture
Estimated complexity: High
Scripting
Purpose:
- Provides custom script execution and reusable scriptlets.
- Extends flow behavior through Pascal Script and Velox script functions.
Main classes:
TvxScriptletTvxScriptItemTvxActionCustomScript- Pascal Script integration classes under
Scripting
Dependencies:
- RemObjects Pascal Script
- Velox module persistence
- Variables
- Data definitions
- Maps
- Logging
- Modified PascalScript code under
Modified
Important entry points:
- Custom script action execution
- Scriptlet execution
- Script Designer/configuration forms
- Script function registration under
Scripting
Important configuration:
VX_SCRIPTLET- ProgramData
Scriptfolder - Scriptlet relations
- Runtime variables and parameters
Related documentation:
ARCHITECTURE.md: Key Frameworks and Libraries, Flow Execution Architecture_Documentation\Scripting
Estimated complexity: High
Reporting
Purpose:
- Generates reports as part of Velox flows.
- Persists report definitions and ReportBuilder templates.
Main classes:
TvxReportTvxPPReportTvxPPChildReportTvxActionReport
Dependencies:
- ReportBuilder
- Data definitions
- Connection pools
- Module persistence
- Logging
- Native file/output handling
Important entry points:
- Report action execution
- Report Designer forms
- Report template load/save
TvxActionReport
Important configuration:
VX_REPORT- Report template streams
- Data definition relations
- Output file settings
Related documentation:
ARCHITECTURE.md: Plugin and Module Architecture, Serialization Formats
Estimated complexity: Medium
Logging, Audit, and Diagnostics
Purpose:
- Records flow execution, system startup/shutdown, warnings, errors, files, transports, SQL/log details, audit events, and diagnostics.
- Provides both database logs and file/event-log diagnostics.
Main classes:
TvxLogTvxSystemLogTvxLogItemTvxCustomLogItemTvxCustomDBLogItemTvxLogFile- Transport log classes
- Event logger helpers in
vxEventLogger
Dependencies:
VX_LOGVX_LOG_ITEMVX_LOG_FILEVX_LOG_TRANSPORTgSetup- Windows Event Log
- madExcept
- FastMM5
- AppData log paths
Important entry points:
CreateSystemLogSaveSystemLogFinaliseSystemLogTvxLog.MessageLogTvxLog.SaveLogLogAuditLogAuditDebugLogUser
Important configuration:
- Setup logging/debug flags
- Detailed system audit flag
- AppData
Logfolder - Missing properties log
- API request debug log
- FastMM and madExcept report paths
Related documentation:
ARCHITECTURE.md: Logging
Estimated complexity: High
Variables and Runtime Context
Purpose:
- Provides reusable and runtime values used by flows, maps, scripts, APIs, and execution context.
- Loads variable groups at startup and during mode/service changes.
Main classes:
TvxVariableGroupTvxVariableTvxParametergVariableGroups
Dependencies:
- Module persistence
- Flow/action execution
- Scriptlets
- Maps
- REST query fields and request context
Important entry points:
gVariableGroups.LoadVariableGroups- Designer variable configuration forms
- Action execution variable lookup
- REST thread query-field setup
Important configuration:
VX_VARIABLE- Variable group module data
- Runtime local variables
- REST query parameters
Related documentation:
ARCHITECTURE.md: Startup Sequence, Flow Execution Architecture
Estimated complexity: Medium
Import, Export, Templates, and Relations
Purpose:
- Exports and imports module configuration bundles.
- Maintains dependency relations between modules.
- Supports legacy
.cfgimports and migration to currentTvx*classes.
Main classes:
TvxConfigTemplateTvxModuleTemplateTvxModuleConvertOldClass
Dependencies:
- Module persistence
- ReportBuilder template streams
VX_RELATION- AppData compare path
- Legacy class mapping
Important entry points:
TvxModule.ExportModuleTvxConfigTemplate.SaveAllModules- Import paths in Designer
TvxModule.SaveModuleRelationsTools > Sync Relations
Important configuration:
.cfgfilesVX_RELATION- Module FIDs
- AppData
Comparefolder - Legacy class mapping table in code
Related documentation:
ARCHITECTURE.md: Plugin and Module Architecture, Serialization Formats
Estimated complexity: High
IPC and Service Control
Purpose:
- Allows the Designer to query and control Velox services.
- Provides internal service-management messaging for status, enabling/disabling work, task counts, ending tasks, and connection details.
Main classes:
TIPCServer- Service manager classes used by the Designer
- IPC request handlers in
TVeloxWorker - IPC request handlers in
TVeloxAPIWorker
Dependencies:
- Cromis IPC
- Windows services
- Service name/config key conventions
gActionPoolgSQLConPoolgSysConPool- Execution managers
Important entry points:
TVeloxWorker.ServiceCreateTVeloxWorker.ServiceStartTVeloxWorkerIPC handlersTVeloxAPIWorker.ServiceCreateTVeloxAPIWorker.ServiceStart- Designer service-control actions
Important configuration:
- Config key
- Test mode suffix
- IPC server name constants
- Service state
- Service display name/startup parameters
Related documentation:
ARCHITECTURE.md: Startup Sequence, Flow Execution Architecture
Estimated complexity: Medium
Security, Licensing, Encryption, and Certificates
Purpose:
- Handles trial/licensing checks, encrypted stored values, password handling, certificate folders, and future direct API-service SSL management.
Main classes:
CheckTrial- Encryption helpers in
vxEncryption TvxDBParams- Setup SSL-related properties
Dependencies:
- Startup code in each executable
- Encrypted passwords in connection configuration
- ProgramData
Certificatefolder - Future OpenSSL/Indy SSL integration
- IIS SSL for the current C# API frontend
Important entry points:
CheckTrialTvxDBParams.Passwordgetter/setter behaviorgSystemConnection.Load- API service startup SSL-related setup fields
Important configuration:
- Encrypted database passwords
- API SSL setting in setup
- ProgramData
Certificate\Public - ProgramData
Certificate\Private - IIS SSL binding for the C# frontend
Related documentation:
ARCHITECTURE.md: Configuration Loading, Flow Execution Architecture, Architecture Questions_Documentation\OpenSSL
Estimated complexity: Medium
Custom Components and UI Infrastructure
Purpose:
- Supplies custom VCL components and UI helpers used by the Designer and forms.
- Encapsulates tree views, combo boxes, editor/memo controls, and other reusable UI pieces.
Main classes:
- Custom components under
Components vxTreeViewvxTreeComboBoxvxSynMemo- Form classes under
Forms
Dependencies:
- VCL
- DevExpress VCL
- SynEdit
- VirtualTreeView
- DFM streaming and published properties
Important entry points:
- Form creation and DFM loading
- Designer module forms
- Main tree/UI setup in
TMain
Important configuration:
.dfmresources- Published component properties
- Designer layout/form state where persisted
Related documentation:
ARCHITECTURE.md: Velox Designer, Key Frameworks and Libraries
Estimated complexity: Medium
Test Harness and Developer Utilities
Purpose:
- Provides internal testing, diagnostics, and helper tooling outside the main production executables.
Main classes:
- VeloxTest main form
- Test buttons/actions in
VeloxTest\frmMain.pas VeloxXSDutilityEventMessagesproject artifacts
Dependencies:
- Designer units
- Service units
- API service units
- Managers and transports
- XSD/schema libraries for
VeloxXSD
Important entry points:
VeloxTest.dprVeloxTest\frmMain.pasVeloxXSD\Program.cs- Designer
Tools > Create XSD
Important configuration:
- Test mode flags
- Active
Connections.json VX_SETUP- ProgramData
Testing - ProgramData
Schema
Related documentation:
ARCHITECTURE.md: Purpose of Each Major Project_Documentation\_Development
Estimated complexity: Medium
Vendor and Modified Framework Integration
Purpose:
- Supplies third-party frameworks and intentionally maintained Velox modifications to third-party/framework code.
- Keeps vendor code separate from Velox-maintained modifications.
Main classes:
- Modified VCL service manager code
- Modified Indy code
- Modified PascalScript code
- Modified ReportBuilder code
- Modified VCL code
- Vendor OpenAPI-Delphi
- Vendor Delphi Neon
- Vendor Scalar assets
Dependencies:
- Delphi RTL/VCL source
- DevExpress VCL
- Indy
- PascalScript
- ReportBuilder
- OpenAPI-Delphi
- Neon
- Other vendor frameworks listed in project search paths
Important entry points:
- Project search paths in
.dprojfiles - Units resolved from
Modified - Units resolved from
Vendor - Initialization sections in third-party and modified code
Important configuration:
- Delphi search path order
$(DXVCL)- Local
VendorandModifiedfolders - Modified units that shadow vendor/framework units
Related documentation:
ARCHITECTURE.md: Key Frameworks and Libraries, Solution and Project Structure
Estimated complexity: High
Installer and ProgramData Assets
Purpose:
- Defines the default files and folders installed under
C:\ProgramData\Veloxon first install. - Provides runtime files that are not part of the main source tree but are important to configuration and operation.
Main classes:
- No Delphi classes directly. This is filesystem/install payload.
Dependencies:
- Installer project outside this repository area
- ProgramData path resolution in
vxConfigPath Connections.json- Schema files and default readme files
Important entry points:
- First install process
- ProgramData update scripts
- Runtime path accessors in
vxConfigPath
Important configuration:
C:\_GIT\Velox\Install\ProgramData\install-veloxprogramdataC:\ProgramData\VeloxConfig\Connections.jsonSchemafiles, including UBL and XML schemasCertificate,Custom Web Parts,Data,Files,Files_Test,Log,Resource,Script,Temp,Testing
Related documentation:
ARCHITECTURE.md: Configuration Loading
Estimated complexity: Medium