Skip to main content
Skip table of contents

Edit Workflow - Workflow variables

Variables are used to further customize workflows. Access the following types of variables:

  • capture variables – Available during the entire workflow lifecycle, e.g. information about the logged user, terminal, etc.
  • user input variables – Defined on the MFD by the user
  • process variables – Available during the workflow processing and delivery, e.g., a selected billing code


Workflow User Input Fields

Workflow Processing

Workflow Destination

Capture Variables(tick)(tick)(tick)
User Input Variables(error)(tick)(tick)
Process Variables(error)(warning)*(tick)

* Please note, it depends on the order in which processing is done.


Variables start with the '%' character followed by a variable name (no spaces allowed) and end with the '%' character, e.g. %userEmail%, %barcode%, etc.

NameWorkflow DestinationVariable TypeUsage
%barcode%allprocessContains the value extracted from the upper-left most barcode. For more details, see section Barcode.
%barcode<X>%allprocessContains each barcode value with X starting from 1. For more details, see section Barcode.
%barcodeInsecure<X>%allprocessContains each unmodified barcode value with X starting from 1. The value may contain unsafe user input that should not be directly used in a workflow. For more details, see section Barcode.
%barcode_<JSON key path>%allprocessContains barcode JSON values with key path using dot notation replaced by underscore character. For more details, see section Barcode.
%separationBarcode%allprocessContains the value extracted from a barcode that triggered a separation of scan jobs. For more details, see section Scan Job Separation.
%billingCode% allprocess

The code of billing code used for this scan job (can be null if none is assigned).

%fileLocations%allprocessThe comma-separated file paths of all scanned files in the destination.
%highlightedText%allprocessContains the text from highlighted text extraction. For more details, see section Highlighter Extraction.
%deviceID%allcaptureThe ID of the device where a scan was made.
%deviceName%allcaptureThe name of the device where a scan was made.
%deviceGroupID%allcaptureThe ID of a group to which the device where a scan was made belongs.
%deviceGroupName%allcaptureThe name of a group to which the device where a scan was made belongs.
%deviceGroupIP%allcaptureThe IP address of a group to which the device where a scan was made belongs.
%deviceLocation%allcaptureThe location of the device where a scan was made.
%deviceIP%allcaptureThe IP address of the device where a scan was made.
%deviceActivationDate%allcaptureThe activate date of the device where a scan was made (in the 'YYYY-MM-DD HH:MM:SS.MS' format).
%deviceEquipmentID%allcaptureThe equipment ID of the device where a scan was made.
%deviceServiceAgreementID%allcaptureThe device service agreement ID of the device where a scan was made.
%deviceContactPerson%allcaptureThe contact person for the device where a scan was made.
%deviceCostCenterID%allcaptureThe cost center number of the device where a scan was made.
%deviceCostCenterName%allcaptureThe cost center name of the device where a scan was made.
%invitationLink%OneDrive for Business (OAuth 2.0)captureThe invitation link where users authorize access to their OneDrive storage.
%safeqHome%allcaptureThe full path to the folder where YSoft SafeQ is installed on the server where the Workflow Processing System is running (typically C:\SafeQ6).
%scanDate%allcaptureThe local date on Terminal Server at the time of a scan in the format yyyy-MM-dd, e.g., '2012-12-21' for December 21, 2012.
%scanTime%allcapture

The local time on Terminal Server at the time of a scan in format HH-mm-ss-fff, e.g., '12-15-00-000' for a quarter past twelve.

%userCostCenterID%allcaptureThe cost center number of the terminal user who made a scan.
%userCostCenterName%allcaptureThe cost center name of the terminal user who made a scan.
%userEmail%allcaptureThe email of the terminal user who made a scan.
%userFirstName%allcaptureThe first name of the terminal user who made a scan.
%userHome%allcaptureThe home folder of the terminal user who made a scan.
%userSurname%allcaptureThe surname of the terminal user who made a scan.
%userUsername%allcaptureThe YSoft SafeQ username of the terminal user who made a scan.
%pdfPassword%allcaptureThe Password being used to encrypt a PDF document. For more details, see section Highlighter Extraction.
%fileLocations%except scriptcaptureThe final comma-separated list of processed files, including the path to file. This variable is only accessible in notifications.
%filePath%scriptprocess

The full path of the currently executed file if script execution mode is "Per file", or the path of the last file processed by the Workflow Processing System if script execution mode is "One time". For more details, see section Scan to Script.

%fileList%script and external processing stepprocess

Full path to the file-list file containing the list of all scanned files. Relevant for the External Processing Step and for the "One time" execution mode of the Scan to script destination. For more details, see the sections Scan to Script and External Processing Step.

%metadata%script and external processing stepprocessFull path to the metadata file containing the list of all workflow variables. Relevant for the External Processing Step and for the "One time" execution mode of the Scan to script destination. For more details, see the sections Scan to Script and External Processing Step.
%externalStepExitCode%allprocessAfter executing the External Processing Step, this variable will contain the numeric exit code from the external process. If the exit code is not zero, the workflow is aborted and the failure notification is delivered, which is where this variable may be useful.
%externalStepStdOut%allprocessAfter executing the External Processing Step, this variable will contain the captured standard output from the external process (but not the standard error output).
%targetDir%scriptprocess

Specifies the location where scanned files (and optionally, metadata and file list files) are stored. For more details, see section Scan to Script.

%scanJobID%allprocessThe unique ID of the scan job instance. This identifier of the scan job is also visible in the log files.
%scanJobSize%allprocessA summary of the scan job files sizes. The variable is available only when there is a restriction set on the connector.
%scanJobFileCount%allprocessThe scan job files count. The variable is available only when there is a restriction set on the connector.
%connectorFileCountLimit%allprocessThe max file count restriction limit. The variable is available only when there is a file count restriction set on the connector.
%connectorFileSizeLimit%allprocessThe file size restriction limit. The variable is available only when there is a file size restriction set on the connector.
%connectorRestrictionsDirectory%allprocessThe path to the folder where the scan jobs are stored when a restriction is applied. The variable is available only when there is a restriction set on the connector.
%workflowID%allcaptureThe ID of the workflow used to make the scan.
%workflowName%allcaptureThe name of the workflow used to make the scan.
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.