2022.2

l
FileID (optional):If the file ID is not given, the first file - the root document - will
be retrieved.
l
Retrieve by search: This section allows the retrieval of files by searching for spe-
cific properties (Definition entries). Enter the properties under Index data.
l
Field:The property to search for. Enter a property, or click the button between
the Field and Value columns to select one of the properties defined for this par-
ticular Document Class in the Metadata Structure of the Vault on the M-Files
server.
l
Value:The value to search for.
Use the Index data buttons to:
l
, Add and removeproperties.
l
, Change the order of the properties by moving them up or down. This is
for convenience only; to the M-Files Server, this order is not important.
l
Validate properties and check for duplicates. Any properties that have
already been defined higher up in the list are displayed in orange. Any prop-
erties that are not defined in the Metadata Structure for the selected Document
Class are displayed in red.
Note that values arenotvalidated.
l
Add missing properties. Any properties that are defined in the Metadata
Structure for the selected Document Class, but not specified in the Index data,
are added to the Index data.
l
Response: Select whether to store the file name, response or document index data
that the plugin gets from the M-Files server in a variable, and specify the name of the vari-
able to use.
l
Response: Select which result you wish stored, and which Workflow variable is to be used
to store the result.
l
Store file name in variable: Stores the name of the downloaded file in a variable.
l
Store response in variable: Stores the success/failure response in a variable.
l
Save document index data to Job as XML/JSON: Outputs the document index
data to the Job File as XML or JSON (according to the selected option)andstores the
status information in a variable (if it exists). The downloaded document itself is
Page 577