ChronoScan keeps the program and your data apart. Knowing where each thing is helps with backups, support and moving an installation.
Program: the Program Files folder (Bin subfolder with ChronoScan.exe, the modules and the OCR engines). Nothing to back up here.
Configuration: C:\ProgramData\ChronoScan is the default configuration; additional configurations are folders named C:\ProgramData\ChronoScan.<Name> (one per customer, test...). The launcher lists them, and -customdir:"folder" starts ChronoScan against one of them. A configuration folder can also be a pointer to another disk or server through a config.redirect.xml file.
Inside a configuration:
Folder or file
Content
Config.xml
Station settings: paths, OCR engine, PDF rendering, SMTP, Enterprise connection, API keys (encrypted).
Jobs\
One subfolder per job (<Name>@<GUID>) with its config.xml, document types, scripts (VBScript\*.vbs) and AI configurations.
WorkDir\
Batches: <Job>@<GUID>\<Batch>\ with the images, the OCR, the data (FS\FS.xml) and the batch logs. Configurable per station and per job.
OutDir\
Default output folder of the exports.
Types\
Document types shared at station level; the types of a job are in Jobs\<job>\Types\.
ListsTxt\
Help lists (.txt, one value|description per line) and database lists (.db).
DataConnections\
Database connections (.udl) used by lookups, lists and database exports.
HotFoldersCfg\
Hot folder and scheduled task definitions, their logs and the engine status.
MFilesConn\, SharePointConn\, OAuth\
Saved connections to M-Files and SharePoint Online and the OAuth2 tokens (encrypted).
Dbs\
Internal databases: system lists, supplier patterns and trigger patterns. In Enterprise they live in SQL Server instead.
ErrorLogs\, Logs\
One error log per day and the program logs: the first thing support asks for.
Backup\, SnapShots\
Copies of Config.xml and configuration snapshots.
chronolink\cslinks\
Vector indexes of the AI Assistants.
In ChronoScan Enterprise the jobs are shared from the server, the batches are referenced in the SQL Server database and the system lists, suppliers, Intelli-Tag patterns and entities move to that database.
Good practice
Keep jobs and batches on a local disk or a fast network share, with backups; see How to Back Up ChronoScan.
Never copy batch folders by hand between PCs: each batch has a unique identifier and the copy duplicates it.
Credentials are encrypted for the machine and user that saved them: a configuration restored on another computer has to enter them again. See Where data and credentials are stored.
