Disclaimer
The material in this document is for informational purposes only. The products it describes are subject to change without prior notice, due to the manufacturer’s continuous development program. Rampiva makes no representations or warranties with respect to this document or with respect to the products described herein. Rampiva shall not be liable for any damages, losses, costs or expenses, direct, indirect or incidental, consequential or special, arising out of, or related to the use of this material or the products described herein.
© Rampiva Technology Inc. 2023 All Rights Reserved
Introduction
Parameters are used throughout Rampiva Automate to link together the different features of the platform and to control the behavior of operations and jobs.
This document describes the types and formats of parameters, and provides sample values.
1. Name Syntax
The parameter names contain only lower-case letters and underscore, and are wrapped in curly brackets, for example: {case_name}
2. Parameter Realms
2.1. System Parameters
These parameters have predefined names and are used to either record the behavior of various operations and features, or to customize this behavior.
For example, the system parameter {last_item_set_name}
records the name of the last Item Set that was created in the Case, and when accessed in a Job, will return this name. Conversely, the system parameter {data_timezone_id}
can be set to configure the time zone under which data will be loaded in the Case during.
See the section Parameters Glossary for a complete listing of system parameters. |
2.2. User-Defined Parameters
These parameters can have any name with a valid syntax that is not already in use by a system parameter.
An example usage of user-defined parameters is configuring a parameter named {base_case_location}
for recording the path under which cases will be created or opened, and prompting the user to fill out the value of this parameter
3. Parameter Types
3.1. Parameters Defined in the Configuration Operation
3.1.1. Text
By default, parameter values are stored as Text and can contain any value.
3.1.2. Text (Masked)
Text (Masked) parameters will have their values masked in the user interface, but can be retrieved by any operation. See Parameters Security.
3.1.3. Text (Protected)
Text (Protected) parameters will have their values masked in the user interface. The values can only be accessed by the Rampiva operations which have a password or key field. See Parameters Security.
3.1.4. Number
Number parameters can contain an integer or real number.
3.1.5. Boolean
Boolean parameters can contain the value True
or False
.
3.1.6. Date
Date parameters are presented to the user as a date picker. The value has the format yyyyMMdd
.
3.1.7. Date Time
Date Time parameters are presented to the user as a date and time picker. The value has the format yyyyMMddTHHmmss
.
3.1.8. Relativity
Relativity parameters are used to select a Relativity object. To use these parameters, a Relativity Service must be configured, and the user submitting the Job must be logged in to the Relativity Service.
The parameter value resolves to the Artifact ID of the Relativity object. The user-printable value resolves to the name of the Relativity object.
3.1.9. Microsoft User Service
Microsoft User Service parameters are used to select a Microsoft Service object, configured in the Settings → User Services section.
3.1.10. Library File
Library File parameters are used to select a file defined in the Settings → File Library section.
The value contains the path to the file, accessible during the Job execution.
3.1.11. User File
User File parameters are used to select a file during the submission of the Job.
The value contains the path to the file, accessible during the Job execution.
3.1.12. Server File
Server File parameters are used to select a file from an In-Place Data Repository during the submission of the Job.
The value contains the path to the file, accessible during the Job execution.
The list of available data repositories and files can be filtered when building the Workflow.
3.1.13. Server Folder
Server Folder parameters are used to select a folder from an In-Place Data Repository during the submission of the Job.
The value contains the path to the folder, accessible during the Job execution.
The list of available data repositories can be filtered when building the Workflow.
3.1.14. Data Set
Data Set parameters are used to select a finalized Data Set from the Matter to which the Job is submitted.
The parameter value resolves to the ID of the Data Set. The user-printable value resolves to the name of the Data Set.
To access additional metadata related to data sets, use the dataSetsMetadata
in a Script operation.
3.1.15. Legal Hold
Legal Hold parameters are used to select a Legal Hold. These parameters can only be used in a Schedule triggered on a Legal Hold event.
The parameter value resolves to the ID of the Legal Hold. The user-printable value resolves to the name of the Legal Hold.
3.1.16. Lock
Lock parameters can be used to create interdependencies between Jobs. If two Jobs use a lock parameter with the same name and value, these two Jobs will not run concurrently.
For example, if two Jobs use the parameter {job_lock}
defined with a value of Initech
, the first Job will start and run to completion before the second Job can start, even if enough resources are available to run both Jobs in parallel.
Alternatively, if two Jobs use the parameter {job_lock}
defined with a value of Test1
and Test2
, this will not prevent the Jobs from running in parallel.
3.1.17. Separator
Separator parameters are used to create a visual separation between a group of parameters.
3.1.18. Warning-Supression Parameters
Parameters with the name starting in suppress_warnings_
can be used to suppress warnings from an operation of a certain type.
For example, to suppress the warnings from the Add Evidence operation, set the parameter {suppress_warnings_add_evidence}
with the value true
.
3.2. Parameters Defined in the Execution Profile
By default, all parameters defined in the Execution Profile will be of the type Text.
By adding the suffix _protected
or _password
to the parameter name sets the type to Text (Protected). Similarly, by setting the suffix _masked
to the parameter name, sets the type to Text (Masked).
3.3. User-Printable Values
Certain parameters, such as Relativity objects, Legal Holds, Data Sets, etc., have both a system value as well as a user printable value. The system value corresponds to the ID of the object, whereas the printable value contains the name of the object.
When evaluating a parameter, the system value is returned by default. To access the user-printable value, call the parameter along with the suffix _userprintable
.
4. Filters
4.1. Regex
The values allowed to be submitted in a user-defined parameter can be restricted with a regular expression. This is done in the Configuration operation.
Parameters using regular expressions that have values separated by alternations |
will only allow for those choices, and will be presented to the user as dropdowns.
The regular expression must only contain characters and alternations. Special regex characters must be escaped.
For example, the regular expression GMT\+1|GMT\+2|GMT\+3
corresponds to the choices GMT+1
, GMT+2
and GMT+3
. However, the regular expression GMT+1|GMT+2|GMT+3
is an invalid and will not trigger a choice parameter.
To allow empty values, place an alternation at the end of the regular expression, for example: GMT\+1|GMT\+2|
. This results in the choices GMT+1
, GMT+2
and a blank option.
4.2. Relativity Conditions
Relativity Conditions can be used to restrict the accepted values of a Relativity parameter, for example, to only objects from a specific Relativity Workspace, or Relativity Matter.
4.3. Scripted Parameters
Scripted parameters let users provide a script can be used to return the list of allowed values.
Scripted parameters support the following scripted language Powershell
, Python
, Ruby
and ECMA
scripts.
Scripted parameters have access to the following variables:
-
client_id
-
client_name
-
client_reference
-
matter_name
-
matter_id
-
matter_reference
-
library_name
-
library_id
-
workflow_name
-
workflow_id
-
user_name
-
parameter_name
Scripted parameters also have access to all parameters above the scripted parameter defined in the Configure Parameters operation. |
Workflows with Scripted Parameters requires a Security Policy with the Modify permission set on the Built-In scope Scripts. |
Powershell scripts have access to the same variables except all variables are wrapped with curly brackets {}
, additionally Powershell scripts have access to the variable {results_file}
which is where the values generated from the script should be written to, where each allowed value is written on a separate line.
Scripted parameters may run more than once, as dependant parameters and parameters defined above the script change the script will update as needed. |
Sample Powershell script:
## DEBUG
#Write-Output("Starting script to evaluate "+{parameter_name}+" - this will be logged to the Scheduler log")
$result = @()
# Sample Result
$result += "C:\\Temp\\Powershell"
# Sample result to confirm live execution
$date = Get-Date
$result += "C:\\Temp\\$date"
# Sample result containing client name
$result += "C:\\Client\\{client_name}"
## DEBUG
#Write-Output(result)
# Return the array
Set-Content -Path "{results_file}" -Value $result
Sample JavaScript script:
//// DEBUG
//print("Starting script to evaluate "+parameter_name+" - this will be logged to the Scheduler log")
var result = []
// Sample result
result.push("C:\\Temp\\JS")
// Sample result to confirm live execution
var today = new Date();
result.push("C:\\Temp\\"+today)
// Sample result containing client name
result.push("C:\\Client\\"+client_name)
//// DEBUG
//print (result)
// Return the array
result
Sample Python script:
import datetime
## DEBUG
#print("Starting script to evaluate "+parameter_name+" - this will be logged to the Scheduler log")
result=[]
# Sample result to confirm live execution
result.append('C:\\Temp\\Python')
# Sample result to confirm live execution
result.append('C:\\Temp\\'+str(datetime.datetime.now()))
# Sample result containing client name
result.append("C:\\Client\\"+client_name)
## DEBUG
#print("returning: "+str(result))
# The resulting list is expected in the variable named "result"
Sample Ruby script:
## DEBUG
#puts("Starting script to evaluate "+parameter_name+" - this will be logged to the Scheduler log")
result = []
# Sample result
result << "C:\\Temp\\Ruby"
# Sample result to confirm live execution
result << "C:\\Temp\\"+Time.now.strftime("%d/%m/%Y %H:%M:%s")
# Sample result containing client name
result << "C:\\Client\\"+client_name
## DEBUG
#puts(result)
# Return the array
result
5. Display Conditions
Display Conditions are used to define when a parameter should be presented to the user when submitting a Job.
The conditions can be defined based on the value of a previously defined parameter in the same Configuration operation.
6. Parameters Security
6.1. Accessible Parameters
By default, parameters are accessible throughout Rampiva Automate. This means that the parameter values can be stored in the audit logs, are retried when submitting a Job and can be used in any Job operation.
6.2. Protected Parameters
The values of Protected parameters can be set in the Configuration operation,
The values of Protected parameters can be set when queueing a Job, or in the Execution Profile. The values of the Protected Parameters are stored encrypted in the Automate database and can only be accessed by the Rampiva operations which have a password or key field.
6.3. Masked Parameters
Masked parameters have their values masked in the user interface, but can be retrieved by any operation.
These parameters can be used to capture sensitive information that should not be displayed back to the user, but that needs to be accessed in fields that are not designated as passwords, or in custom scripts.
7. Parameters Glossary
This section lists all system parameters used in Rampiva Automate.
The Scope column indicates the scope of the application to which the parameters apply. For example, parameters that are specific to certain operations, such as the Add Evidence operation, will indicate this operation in the scope, and parameters which are specific to a certain feature, will indicate the feature name in the scope.
The R/W column indicates if the parameter is read-only (R), or if it can be written to (W) to customize the behavior of the platform.
The search box can be used to search in any field of the table, including the parameter name and scope. |
Parameter | R/W | Scope | Description | Example |
---|---|---|---|---|
|
W |
Production Set Nuix |
Specify a number for the box to cycle from |
|
|
W |
Production Set Nuix |
Specify a number for the box to stop numbering at |
|
|
W |
Production Set Nuix |
Specify a number for the box to start numbering at |
|
|
R |
Brainspace |
The ID of the Brainspace Dataset |
|
|
R |
Brainspace |
The name of the Brainspace Dataset |
|
|
R |
Brainspace |
The Brainspace version |
|
|
W |
Nuix Workers |
The number of workers to use from the worker broker |
|
|
R |
Call API |
The API response body. This parameter is not exposed as a variable in the Script operation. |
|
|
R |
Call API |
The API response code |
200 |
|
R |
Call API |
The API response headers, JSON encoded |
|
|
R |
Case Nuix |
The folder in which the Nuix case resides |
|
|
R |
Case Nuix |
The name of the case |
|
|
R |
Case Relativity |
The last set value of the name of the case or the name of the Relativity workspace |
|
|
R |
Case Nuix |
At most the first 5 alphabetic characters from the case name, to be used in document ID numbering schemes |
|
|
W |
Case Nuix |
The timezone to use when opening cases. See Joda Time Zones for a list of valid timezone IDs |
|
|
R |
Scheduler Job |
The system ID of the client under which the job was submitted, if available |
|
|
R |
Scheduler Job |
The name of the client under which the job was submitted, if available |
|
|
R |
Scheduler |
The Client reference set using the API |
|
|
W |
Assign Custodians |
Specify the folder level from which custodian names should be extracted |
|
|
W |
Legal Hold |
The name of the custodian |
|
|
W |
Workflow |
Specify a custom metadata field which records the digest size of items to use instead of the regular digest size calculation |
|
|
W |
Add Evidence Nuix |
The source data locale country to use when adding evidence |
|
|
W |
Add Evidence Nuix |
The source data locale language to use when adding evidence |
|
|
W |
Add Evidence Nuix |
The source timezone of the data to use when adding evidence. See Joda Time Zones for a list of valid timezone IDs |
|
|
R |
Utility |
The date in local format |
|
|
R |
Utility |
The date in spreadsheet format |
|
|
R |
Utility |
The current date and time at execution as epoch millis |
|
|
R |
Utility |
The current date and time at execution, in local format as reported by Nuix |
|
|
R |
Utility |
The date and time in spreadsheet format |
|
|
R |
Utility |
The current date and time at execution, formatted using |
|
|
R |
Utility |
The current date at execution, formatted using |
|
|
R |
Discover |
The ID of the Discover case |
|
|
R |
Discover |
The name of the Discover case |
|
|
R |
Discover |
The Discover version |
|
|
W |
Production Set Nuix |
Specify a custom number of digits |
|
|
W |
Production Set Nuix |
Specify a custom number of family digits |
|
|
W |
Production Set Nuix |
Specify a custom document ID start number |
|
|
W |
Add Evidence Nuix Documentum |
This parameter specifies the Documentum docbase repository |
|
|
W |
Add Evidence Nuix Documentum |
This optional parameter defines the Windows networking domain of the server account |
|
|
W |
Add Evidence Nuix Documentum |
The password needed to access the account |
|
|
W |
Add Evidence Nuix Documentum |
The port number to connect on |
|
|
W |
Add Evidence Nuix Documentum |
This optional parameter specifies the Documentum property file |
|
|
W |
Add Evidence Nuix Documentum |
A DQL query. This optional parameter specifies a query used to filter the content |
|
|
W |
Add Evidence Nuix Documentum |
This parameter specifies the Documentum server address |
|
|
W |
Add Evidence Nuix Documentum |
The username needed to access the account |
|
|
W |
Add Evidence Nuix Dropbox |
A string retrieved using the authCode that enables access to an account. If the access token to an account is already known, provide it directly using this parameter instead of |
|
|
W |
Add Evidence Nuix null |
A string retrieved via a webpage on Dropbox that enables access to an account |
|
|
W |
Add Evidence Nuix Dropbox |
A boolean that indicates that a Dropbox team will be added to evidence. This optional parameter should be present and set to |
|
|
R |
ElasticSearch |
The version of the ElasticSearch cluster |
8.5.0 |
|
W |
Add Evidence Nuix Enterprise Vault |
An archive ID. This optional parameter limits the evidence to the specified Enterprise Vault archive |
|
|
W |
Add Evidence Nuix Enterprise Vault |
The hostname or IP address of Enterprise Vault |
|
|
W |
Add Evidence Nuix Enterprise Vault |
A name. This optional parameter limits the evidence to the specified custodian or author |
|
|
W |
Add Evidence Nuix Enterprise Vault |
This option parameters specified the Enterprise Vault flag for the collection. Only one flag value must be specified. |
|
|
W |
Add Evidence Nuix Enterprise Vault |
This optional parameter limits the evidence to a date range beginning from the specified date/time |
|
|
W |
Add Evidence Nuix Enterprise Vault |
This optional parameter limits the evidence to results matching Enterprise Vault’s query using the words in this string. Subject and message/document content are searched by Enterprise Vault and it will match any word in the string unless specified differently in the |
|
|
W |
Add Evidence Nuix Enterprise Vault |
This optional parameter limits the evidence to a date range ending at the specified date/time |
|
|
W |
Add Evidence Nuix Enterprise Vault |
A vault store ID. This optional parameter limits the evidence to the specified Enterprise Vault vault |
|
|
W |
Add Evidence Nuix Exchange |
This optional parameter defines the Windows networking domain of the server account |
|
|
W |
Add Evidence Nuix Exchange |
This optional parameter limits the evidence to a date range beginning from the specified date/time. It must be accompanied by the |
|
|
W |
Add Evidence Nuix Exchange |
Specify a value to instructs Exchange to impersonate the mailbox user instead of delegating when the mailbox and username are different |
|
|
W |
Add Evidence Nuix Exchange |
The mailbox locations to add evidence from |
|
|
W |
Add Evidence Nuix Exchange |
The mailbox to ingest if it differs from the username |
|
|
W |
Add Evidence Nuix Exchange |
The password needed to access the account |
|
|
W |
Add Evidence Nuix Exchange |
This optional parameter limits the evidence to a date range ending at the specified date/time. It must be accompanied by the |
|
|
W |
Add Evidence Nuix Exchange |
The path to the Exchange Web Service |
|
|
W |
Add Evidence Nuix Exchange |
The username needed to access the account |
|
|
R |
Production Set Nuix |
The name of the production set being exported |
|
|
W |
Add Evidence Nuix |
Set the after date filter to use when adding evidence |
|
|
W |
Add Evidence Nuix |
Set the before date filter to use when adding evidence |
|
|
R |
Case Nuix |
The folder in which the first Nuix used case resides |
|
|
W |
Production Set Nuix |
Specify a number for the folder to cycle from |
|
|
W |
Production Set Nuix |
Specify a number for the folder to stop numbering at |
|
|
W |
Production Set Nuix |
Specify a number for the folder to start numbering at |
|
|
W |
Production Set Nuix |
Sspecify if pages from the same document should be grouped |
|
|
W |
Production Set Nuix |
Specify if documents from the same family should be grouped |
|
|
R |
Call API Scheduler |
The Bearer token that can be used to authenticate to Scheduler from a Job using the Call API operation. This token is valid while the Job is running and will authenticate the request as the user who last submitted the Job |
|
|
R |
Scheduler Job |
The system ID of the engine that is running the job |
|
|
R |
Scheduler Job |
The name of the engine that is running the job |
|
|
R |
Scheduler Job |
The location of the job execution log |
|
|
R |
Job |
The name of the Execution Profile |
|
|
R |
Scheduler Job |
The system ID of the job |
|
|
R |
Scheduler Job |
The name of the job |
|
|
R |
Scheduler Job |
The notes assigned to the job |
|
|
R |
Scheduler Job |
The job priority |
|
|
R |
Scheduler Job |
The system ID of the Resource Pool to which the job was assigned |
|
|
R |
Scheduler Job |
The name of the Resource Pool to which the job was assigned |
|
|
R |
Scheduler Job |
The system ID of the server hosting the engine that is running the job |
|
|
R |
Scheduler Job |
The name of the server hosting the engine that is running the job |
|
|
W |
Job |
The path to a Job-Side Script file |
|
|
R |
Scheduler Job |
The name of the user who submitted the job |
|
|
R |
Scheduler Job |
The time and date when the job was submitted |
|
|
R |
Job Nuix Workers |
The IP of the Job worker broker |
|
|
R |
Job Nuix Workers |
The port of the Job worker broker |
|
|
W |
Add Evidence Nuix |
The password for the alias |
|
|
W |
Add Evidence Nuix |
The alias to use from the keystore |
|
|
W |
Add Evidence Nuix |
The password of the keystore |
|
|
W |
Add Evidence Nuix |
The path to the keystore |
|
|
W |
Add Evidence Nuix |
The notes storage format file |
|
|
W |
Add Evidence Nuix |
The file path to the keystore tsv file |
|
|
R |
Add Evidence Nuix |
The date and time of the last batch loaded into the case, in local format as reported by Nuix |
|
|
R |
Add Evidence Nuix |
The date and time of the last batch loaded into the case |
|
|
R |
Add Evidence Nuix |
The date of the last batch loaded into the case |
|
|
R |
Add Evidence Nuix |
The GUID of the last batch loaded into the case |
|
|
R |
Add Evidence Nuix |
The GUID of the last evidence loaded into the case |
|
|
R |
Add Evidence Nuix |
The name of the last evidence loaded into the case. The actual name assigned to the evidence might be different than the one specified in the workflow, for example, if an evidence with the same name previously existed in the case |
|
|
R |
PowerShell External Application |
The exit code of the external application. |
0 |
|
R |
Legal Export Nuix |
The folder of the last legal export |
|
|
R |
Item Set Nuix |
The batch ID of the last item set to which items were added, including both original and duplicate items |
|
|
R |
Item Set Nuix |
The duplicates batch ID of the last item set to which items were added |
|
|
R |
Item Set Nuix |
The name of the item set to which items were last added |
|
|
R |
Item Set Nuix |
The originals batch ID of the last item set to which items were added |
|
|
R |
Metadata Nuix |
The full file name and path of the last metadata export, from operations Generate Domain Fields, Generate Duplicate Custodians, Generate Duplicate Fields and Metadata Export |
|
|
R |
Relativity |
The location of the last overwritten permissions file |
|
|
R |
Production Set Nuix |
The name of the last production set created in this workflow session. The actual name assigned to the production set might be different than the one specified in the workflow, for example, if frozen production set with the same name previously existed in the case |
|
|
R |
Relativity |
The description of error encountered during Relativity script execution. If no exception was encountered, this will be blank |
|
|
R |
Report Nuix |
The full file name and path of the last report produced |
|
|
R |
Script |
The description of error encountered during script execution. If no exception was encountered, this will be blank |
|
|
R |
Script |
The text outputted by the script, for example using the print method. If no text was outputted by the script, this will be blank |
|
|
R |
Script |
The string representation of the object returned by the script. If no object was returned, this will be |
|
|
W |
Legal Hold |
The name of the Legal Hold |
|
|
W |
Nuix Workers |
The number of local workers to use |
|
|
W |
Nuix Workers |
The memory in MB for each worker to use |
|
|
W |
Workflow |
Set this parameter to |
|
|
R |
Scheduler Job |
The system ID of the matter under which the job was submitted, if available |
|
|
R |
Scheduler Job |
The name of the matter under which the job was submitted, if available |
|
|
W |
Metadata Nuix |
Specify a custom metadata profile for operations Legal Export, Metadata Export and Relativity Metadata Overlay |
|
|
W |
Add Evidence Nuix Microsoft Graph |
The password for the PKCS#12 certificate store, if present |
|
|
W |
Add Evidence Nuix Microsoft Graph |
The path to a PKCS#12 certificate store, to use instead of the client secret, for authentication |
|
|
W |
Add Evidence Nuix Microsoft Graph |
The client secret that has been configured for the client ID provided, for authentication |
|
|
W |
Add Evidence Nuix Microsoft Graph |
The client/application ID for the app that has been registered with Azure AD which and granted the necessary privileges |
|
|
W |
Add Evidence Nuix Microsoft Graph |
The end of the collection date range |
|
|
W |
Add Evidence Nuix Microsoft Graph |
The locations to retrieve mailbox data from |
|
|
W |
Add Evidence Nuix Microsoft Graph |
The password for the username, if it is present |
|
|
W |
Add Evidence Nuix Microsoft Graph |
The type of data to retrieve |
|
|
W |
Add Evidence Nuix Microsoft Graph |
The beginning of the collection date range |
|
|
W |
Add Evidence Nuix Microsoft Graph |
Optionally, a list of team names to filter on |
|
|
W |
Add Evidence Nuix Microsoft Graph |
The tenant ID for Azure AD |
|
|
W |
Add Evidence Nuix Microsoft Graph |
Optionally, a list of user principal names to filter on |
|
|
W |
Add Evidence Nuix Microsoft Graph |
Optionally, the username for a user that is a member of the Teams to be processed, only needed for ingesting Team Calendars |
|
|
W |
Add Evidence Nuix Microsoft Graph |
Optionally, an integer limiting the number of versions retrieved if version retrievel is enabled. Defaults to |
|
|
W |
Add Evidence Nuix Microsoft Graph |
Optionally, a boolean indicating of all versions should be retrieved. Defaults to |
|
|
W |
Legal Hold |
The subject of the Notice |
|
|
R |
Workflow |
The position of the operation in the workflow |
|
|
W |
Add Evidence Nuix null |
A string representation of the connection params |
|
|
W |
Add Evidence Nuix null |
The driver type used to connect. Can be |
|
|
W |
Add Evidence Nuix null |
The maximum number of rows to return from each table or query. This parameter is optional. It can save time when processing tables or query results with very many rows. The selection of which rows will be returned should be considered arbitrary |
|
|
W |
Add Evidence Nuix null |
The password needed to access the account |
|
|
W |
Add Evidence Nuix null |
A SQL query. This parameter specifies a query used to filter the content |
|
|
W |
Add Evidence Nuix null |
The role to login as. For normal logins, this should be blank |
|
|
W |
Add Evidence Nuix null |
The username needed to access the account |
|
|
W |
Legal Hold |
The respond-by date of the original Notification, to use in reminder or escalations |
|
|
W |
Legal Hold |
The sent date of the original Notification, to use in reminder or escalations |
|
|
W |
Legal Hold |
The subject of the original Notification, to use in reminder or escalations |
|
|
W |
Production Set Nuix |
Specify a number for the page to cycle from |
|
|
W |
Production Set Nuix |
Specify a number for the page to stop numbering at |
|
|
W |
Production Set Nuix |
Specify a number for the page to start numbering at |
|
|
R |
PowerShell |
The folder to use in PowerShell scripts to write parameters values |
|
|
R |
Case Nuix |
The folder in which the previously used Nuix case resides |
|
|
W |
Nuix Add Evidence |
Specify a custom timeout for the initialization of the Add Evidence. A value of |
|
|
R |
Add Evidence Nuix |
Specify a custom processing profile |
|
|
R |
Utility |
HTML image tag showing the Rampiva logo |
|
|
R |
Utility |
A randomly generated GUID |
|
|
R |
Relativity |
The Relativity API response body. This parameter is not exposed as a variable in the Script operation. |
|
|
R |
Relativity |
The relativity API response code |
200 |
|
R |
Relativity |
The relativity API response headers, JSON encoded |
|
|
R |
Relativity |
Indicates if a client was created in the Set Relativity Client operation |
|
|
R |
Relativity |
The artifact ID of the client used in the Set Relativity Client operation |
|
|
R |
Relativity |
The name of the client used in the Set Relativity Client operation |
|
|
R |
Relativity |
Indicates if a matter was created in the Set Relativity Matter operation |
|
|
R |
Relativity |
The artifact ID of the matter used in the Set Relativity Matter operation |
|
|
R |
Relativity |
The name of the matter used in the Set Relativity Matter operation |
|
|
W |
Legal Export Relativity |
Specify the Relativity native copy mode |
|
|
W |
Legal Export Relativity |
Specify a the Relativity overwrite mode for the Legal Export, Relativity Loadfile Upload and Relativity Metadata Overlay operations |
|
|
R |
Relativity |
Indicates if a workspace was created in the Set Relativity Workspace operation |
|
|
R |
Relativity |
The artifact ID of the workspace used in the Set Relativity Workspace operation |
|
|
R |
Relativity |
The name of the workspace used in the Set Relativity Workspace operation |
|
|
W |
Report Nuix |
Specify the password to lock the Excel report files with |
|
|
W |
Add Evidence Nuix S3 |
This parameter specifies the access key ID for an Amazon Web Service account |
|
|
W |
Add Evidence Nuix S3 |
This optional parameter specifies a bucket and optionally a path to a folder within the bucket that contains the evidence to ingest. Omitting this parameter will cause all buckets to be added to evidence |
|
|
W |
Add Evidence Nuix S3 |
This optional parameter is only valid when access and secret are not specified. A |
|
|
W |
Add Evidence Nuix S3 |
This optional parameter specifies a particular Amazon Web Service server endpoint. This can be used to connect to a particular regional server |
|
|
W |
Add Evidence Nuix S3 |
This parameter specifies the secret access key for an Amazon Web Service account |
|
|
R |
Call API Scheduler |
The URL used to access Scheduler. This value is defined in the Execution Profile |
|
|
W |
Legal Hold |
The date of the Notification |
|
|
R |
Scheduler |
The fully qualified domain name (FQDN) of the server running the workflow |
|
|
R |
Scheduler |
The name of the server running the job |
|
|
W |
Assign Custodians |
Specify whether to assign custodian names from folder names with typical custodian names |
|
|
W |
Assign Custodians |
Specify whether to assign custodian names from folder names |
|
|
W |
Assign Custodians |
Specify whether to assign custodian names from the PST file information |
|
|
W |
Add Evidence Nuix Sharepoint |
This optional parameter defines the Windows networking domain of the server account |
|
|
W |
Add Evidence Nuix Sharepoint |
The password needed to access the account |
|
|
W |
Add Evidence Nuix Sharepoint |
A URI specifying the site address |
|
|
W |
Add Evidence Nuix Sharepoint |
The username needed to access the account |
|
|
R |
Utility |
Simple HTML style code for the workflow progress table |
|
|
W |
SQL |
The SQL connection string to use for overwriting the default behavior of the SQL-related operations |
|
|
W |
Add Evidence Nuix SQL |
The hostname or IP address of the SQL Server |
|
|
W |
Add Evidence Nuix SQL |
This optional parameter defines the Windows networking domain of the server account |
|
|
W |
Add Evidence Nuix SQL |
A SQL Server instance name |
|
|
W |
Add Evidence Nuix SQL |
The maximum number of rows to return from each table or query. This parameter is optional. It can save time when processing tables or query results with very many rows. The selection of which rows will be returned should be considered arbitrary |
|
|
W |
Add Evidence Nuix SQL |
The password needed to access the account |
|
|
W |
Add Evidence Nuix SQL |
A SQL query. This optional parameter specifies a query used to filter the content |
|
|
W |
Add Evidence Nuix SQL |
The username needed to access the account |
|
|
W |
Add Evidence Nuix SSH |
A boolean. When set to |
|
|
W |
Add Evidence Nuix SSH |
The hostname or IP address of Enterprise Vault |
|
|
W |
Add Evidence Nuix SSH |
The expected host fingerprint for the host being connected to. If this value is not set then any host fingerpint will be allowed, leaving the possibility of a man in the middle attack on the connection |
|
|
W |
Add Evidence Nuix SSH |
Points to a folder on the local system which holds the SSH authentication key pairs |
|
|
W |
Add Evidence Nuix SSH |
The password needed to access the account |
|
|
W |
Add Evidence Nuix SSH |
The port number to connect on |
|
|
W |
Add Evidence Nuix SSH |
A folder on the SSH host to start traversing from. This optional parameter limits the evidence to items underneath this starting folder |
|
|
W |
Add Evidence Nuix SSH |
The password needed to access protected files when using SSH key based authentication |
|
|
W |
Add Evidence Nuix SSH |
The username needed to access the account |
|
|
R |
Utility |
The start date in local format |
|
|
R |
Utility |
The start date in spreadsheet format |
|
|
R |
Utility |
The start date and time as epoch millis |
|
|
R |
Utility |
The start date and time, in local format as reported by Nuix |
|
|
R |
Utility |
The start date and time, formatted using |
|
|
R |
Utility |
The start date, formatted using |
|
|
R |
Utility |
The start time in spreadsheet format |
|
|
R |
Utility |
The start time |
|
|
R |
Utility |
The time in spreadsheet format |
|
|
R |
Utility |
The time |
|
|
W |
Add Evidence Nuix Twitter |
The access token secret of the Twitter app |
|
|
W |
Add Evidence Nuix Twitter |
A string retrieved using the authCode that enables access to an account. A new app can be created at https://apps.twitter.com to generate this token |
|
|
W |
Add Evidence Nuix Twitter |
The consumer secret (API secret) of the Twitter app |
|
|
W |
Add Evidence Nuix Twitter |
The consumer key (API key) of the Twitter app |
|
|
R |
Webhook |
The body of the Webhook call that triggered the Scheduled Job |
{"custom_data":"1234"} |
|
R |
Webhook |
The headers of the Webhook call |
{"Accept":"/","User-Agent":"Zapier","Content-Type":"application/json"} |
|
R |
Webhook |
The ID of the Schedule that triggered the job |
c2b64747-505d-4719-bb5f-75bbd8a63774 |
|
R |
Webhook |
The name of the Schedule that triggered the job |
Sample Workflow |
|
R |
Workflow Job |
Text indicating the status of each workflow operation, up to the current point of execution. This parameter is not exposed as a variable in the Script operation. |
|
|
R |
Workflow |
The name of the workflow |
|
|
R |
Workflow Job |
The execution state of the workflow or of the job |
|
|
R |
Workflow Job |
HTML table showing an overview of the workflow progress, up to the current point of execution. This parameter is not exposed as a variable in the Script operation. |
|
|
R |
Workflow Job |
Tab-separated text table showing an overview of the workflow progress, up to the current point of execution. This parameter is not exposed as a variable in the Script operation. |