If you already have an Extend file id (for instance from running a parser or a previous file creation) then you can
run a processor via file id, and any parsed data will be reused.
Predetermined outputs that can be used to override the outputs
generated. Generally not recommended for most use cases, however, can be
useful in cases of overriding a classification in workflow or a subset
of extraction fields when data is known.
An array of raw strings. Can be used in place of files when passing raw data.
The raw data will be converted to .txt files and run through the workflow. If
the data follows a specific format, it is recommended to use the files
parameter instead. Either files or rawTexts must be provided.
An optional version of the workflow that files will be run through. This
number can be found when viewing the workflow on the Extend platform. When a
version number is not supplied, the most recent version of the workflow will
be used. To run the “draft” version of a workflow, use “draft” as the version.
An optional value used to determine the relative order of WorkflowRuns when
rate limiting is in effect. Priority values must be an integer between 1 and
100 inclusive. Lower values will be prioritized before higher values. The
default priority value is 50.
The status of a WorkflowRun. This will either be “PENDING” as the WorkflowRun has just started, or “PROCESSING” if the WorkflowRun is immediately started.
An array of outputs that were generated by the WorkflowRun. This will be empty as the WorkflowRun has just started.The shape of the outputs will match the shape of a processor run’s output.And the output field will conform to the shape of output types.