Job As JSON Action

With the help of the Job As JSON action, it is possible to write all information that belongs to the job object in a JSON file and to define the location where it should be stored. This can be necessary for various workflows in which the payload of the stream should be externally accessible.


The Job From JSON node will no longer import the job id of the job that has previously been extracted with the Job As JSON node. This change avoids having a wrong job ID reference after Job From JSON trigger that kept pushing all updates to the "old" exported job. Additionally, stream variables will now also be read in and be available after Job From JSON node execution.

Last updated