|Download Help (Windows Only)|
Parent Topic: Post-Processing Data Sets with Fileflow Script
To handle in-memory data sets as part of the Fileflow Script, processes must contain code to evaluate and handle ProcessFileflow messages, which the Dataflow Script API uses to transfer data sets from one process to the next.
In the process VI you added to the Fileflow Script, create the following block diagram to handle a ProcessFileFlowBlock message, and then transfer the data set to the next process. Customize the gray sections for your unique programming goals.
|Convert the data set from the previous process, which the Fileflow Script API stores as variant data, to its original format as a cluster with specific elements.|
|Unbundle the reference to the in-memory data set. Post-processing code uses this reference to operate on the contents of the data set.|
|The message-handling case must be the exact name of the ProcessFileflow message.|
|Create process-specific code that performs the post-processing operations you desire.|
|To transfer the data set to the message queue for the next process in the Fileflow Script, call the Get Next Fileflow Process VI and pass the data cluster to it. The Fileflow Script API looks up which process is next in order based on the value of the source input. If the current process is the final process in Fileflow Script, the API sends a event reference message to the File Manager process. File Manager manages complete data sets until they are transferred to the server.|
In the NI InsightCM SDK reference code, refer to IntializeDFScript.vi in the labview\vi.lib\addons\InsightCM\Devices\Shared\Application directory for an example of adding processes to the Dataflow Script.