2022.2

/* both methods perform the same task */
repoObject.SetValueByID "Users", "FormOfAddress", "Mr.", 10
repoObject.SetValue "Users", "FormOfAddress", "Mr.", "ID=10"
Updating a row
There is currently no 'update' feature in the API for a whole KeySet. This JavaScript example retrieves
the KeySet ID, which is then used to update values in the row.
/* Get KeySet ID */
var repoObject = new ActiveXObject("RepositoryLib.WorkflowRepository");
var keySetID = repoObject.GetValue("customers", "ID", "Cus-
tomerID='CURD654321'");
/* Update Values */
repoObject.SetValueByID("customers", "FormOfAddress", "Mr.", keySetID);
repoObject.SetValueByID("customers", "Country", "US", keySetID);
repoObject.SetValueByID("customers", "Language", "EN", keySetID);
Version
Returns the version of the DLL library used by the Repository.
Syntax
Version(): string
Metadata API
The "Metadata" on page67 is a hierarchical structure describing the data in a job. It is composed of 5
basic levels, from top to bottom: Job, Group, Document, Datapage, and Page.
There is a set of plugins that allow to edit the Metadata during a Workflow process (see "Metadata
tasks" on page469), but you can also manipulate the Metadata in your process via scripts using the
Metadata API.
In the Metadata API, each unit, on all levels in the hierarchy, is represented by an object called a
"Node" on page172.
A Node item is a collection of its lower level node type items. At the top of this tree sits a single Node
object named "MetaJob" on page165. The MetaJob is a collection of "MetaGroup" on page166
objects, where each MetaGroup is a collection of one or more "MetaDocument" on page168 objects. In
turn, MetaDocument objects hold "MetaDatapage" on page169 objects, which have "MetaPage" on
page171 objects.
In addition, a Node contains a collection of "Attributes" on page184 and can contain any number of
"Fields" on page185.
Page 162