2022.2

l
An HTTP-based authentication process, once it has validated user credentials, could store ses-
sion information (unique ID, user name, session starting time) into the repository. All other
related processes could then look into the repository to determine if a new request is received
from an already authenticated user, if the session has expired, what the user name is, etc.
l
Data comes in and is merged into a Capture OnTheGo template and stored in the Data Repos-
itory. The end-user augments the data (using the COTG as a data-entry system). The process
that receives the augmented data could look into the Data Repository to retrieve the original data
(or the ID of the original data records) in order to augment, modify or delete it.
Structure
As can be seen in the "Data Repository Manager" on page707, the Data Repository consists of
Groups, Keys and KeySets.
Feature Name Description Equivalent Database Terminology
Group
A Group is defined by its Keys (columns), and may contain 0 or
more KeySets (rows) within it.
Table
Key
A Key is defined only by its name. The Data Repository only
supports STRING values and any data inserted into it is con-
verted to string automatically. The maximum size of a single
key is 1 billion bytes.
Column/Field
KeySet
A group may contain as many KeySets (rows), which contain
variable data, as necessary. A KeySet is inserted using the
"Push to Repository" on page392 task.
Row/Record
Lookup
A method of retrieving one or more KeySets from a group in
the data repository.
Query
Accessing the Data Repository
Via plugins
Storing data in the Data Repository
Data can be stored in the Data Repository using the Push to Repository task (see "Push to Repository"
on page392).
Retrieving data from the Data Repository
In any Workflow task where variable data is allowed (recognisable by the maroon field labels), inform-
ation can be retrieved from the Data Repository using a Lookup function. Right-click a field with a
maroon label and select Get Repository Location. This will bring up the "Data Repository Manager"
on page707. Select a Group, Key and KeySet entry to determine which value or values should be
retrieved at runtime; then click OK. The Lookup Function Syntax, displayed at the bottom left of the
Data Repository Manager, will be copied into the field.
The syntax is of the Lookup function is:
Lookup(Group_Name, Key_To_Retrieve, Key_To_Match, 'Value_To_Match')
Page 80