An object repository is structured in the same way as a datatable. The difference is in the type and use of the data used in scripts.
Rather than a pure data source e.g. for form filling, creating standard documents the object repository is used for storing common flow data, separating the scripts from confidential data and allowing data to be reused in multiple scripts while it can be updated from a central source.
The data is formatted in the same way as in a datatable with the top row being the header row which identifies the variable names which can be referenced in the scripts.
Object Repository Data
//top row identifies variable and variable value (identity, value) identity,value home, VerdaPress blogBtn, Blog search, https://google.com dylan, bob dylan
Object Repository Script
// use data from tagui_local.csv https://verdapress.uk/services/test-bed/ click `home` wait 5 click `blogBtn` wait 5 `search` wait 5 type input as `dylan`[enter] wait 5
This can be run from the command line as tagui [script filename] [object repository filename]
Local vs Global Repository Files
Each flow has a local object repository and all flows share the global object repository.
The local object repository is the tagui_local.csv in the same folder as the flow.
The global object repository is the tagui_global.csv in the tagui/src/ folder.
The local repository file takes precedence over the global.