Differences

This shows you the differences between two versions of the page.

--- custom_proc:custom_processors [2021/02/16 17:30] – [Plugin architecture] emcodem
+++ custom_proc:custom_processors [2023/10/25 15:42] (current) – [Plugin Development] emcodem
@@ Line 254: / Line 254: @@
 ** Set Outputs from a processor **
 Setting outputs is optional. If you develop a processor that is not intended to deliver any output back to ffastrans, thats ok and you do not have to read on ;-)
@@ Line 276: / Line 275: @@
     * s_job_error_msg
       * setting this will cause the FFAStrans host to go the "error" path in the workflow or end the job with error
+Usually outputs are already part of the job json because they are passed in from the processor GUI html.
+So the processor code does not have to "generate" a new object but instead it only sets the "data" attribute of existing outputs in the existing job json.
+Take special note about the field names, "id" is optional as it is just the html id of the field on index.html GUI. FFAStrans only needs to know "value" and "data", where "value" has to be some existing variable (user var or predefined system var)
+<code>
+"proc_data": {
+    "inputs": [],
+    "outputs": [
+      {
+        "id": "",
+        "value": "s_source",
+        "data": "C:\\test\\test.ts"
+      }
+    ]
+  }
+</code>