2022.2

Table Of Contents
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 page393).
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 page710. 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')
Note: Value_To_Matchcan be a static string, a jobInfo or a variable, but not a data selection.
For the Value_To_Match parameter, the single-quotes surrounding the value are mandatory
even if the value is dynamic.
This function may also be used anywhere else where the contextual menu gives access to it. You
could, for example, use it on the General tab of the Create File task, to fill in the value of a key/value
pair in a JSON string.
Tip: The Data Repository Manager displays, at the bottom left, the syntax used for accessing a
specific value.
Note: Lookup()returns NODATA when the group and/or key does not exist.
In previous versions of the software, trying to do a look-up in a non-existent group and/or key
would cause an error. This change in behavior may affect any Workflow configuration that uses
an on error process related to invalid groups/keys.
Scripts
In a script you can access the Data Repository using the "Data Repository API" on page146.
For a quick start, turn to this How-to: Interacting with the Data Repository API.
Page 81