From 572ac7ee7670163acdb3b976a0542a51297c0a19 Mon Sep 17 00:00:00 2001 From: Ben Thompson Date: Tue, 5 Dec 2023 15:51:55 +0000 Subject: [PATCH] Fix toolkit-tutorials issue 109 --- v12/en/data.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/v12/en/data.json b/v12/en/data.json index c475c97..5eddc2c 100644 --- a/v12/en/data.json +++ b/v12/en/data.json @@ -69,7 +69,7 @@ "sections": [ { - "section": "This tutorial demonstrates how the File Exists node can be used with its List mode property in order to discover meta-data about a list of files which are discovered in an input directory. This information is sent downstream to later nodes in the flow. The File Iterator node is used to loop over the list of files, and for each entry in the list propagates a LocalEnvironment that is compatible with driving the behaviour of a subsequent FileRead node to read and parse that specific file. The File Iterator node allows each file to be processed one at a time. If an exception occurs for a particular propagation, the exception is stored, and the remaining file entries are processed to completion. In the provided example, a Filter node is used after the File Iterator node to determine whether the file was last modified before today. If the file was last modified before today then the Filter node propagates down its True terminal and after logging some information using the node Trace2, the file will be deleted. If the file was last modified today, then the Filter node propagates down its False terminal and the File Read node will parse the file and log its contents using the node Trace3." + "section": "This tutorial demonstrates how the File Exists node can be used with its List mode property in order to discover meta-data about a list of files which are discovered in an input directory. This information is sent downstream to later nodes in the flow. The File Iterator node is used to loop over the list of files, and for each entry in the list propagates a LocalEnvironment that is compatible with driving the behaviour of a subsequent FileRead node to read and parse that specific file. The File Iterator node allows each file to be processed one at a time. If an exception occurs for a particular propagation, the exception is stored, and the remaining file entries are processed to completion. In the provided example, a Filter node is used after the File Iterator node to determine whether the file was last modified before today. If the file was last modified before today then the Filter node propagates down its True terminal and after logging some information using the node Trace2, the file will be deleted. If the file was last modified today, then the Filter node propagates down its False terminal and the File Read node will parse the file and log its contents using the node Trace3." }, { "section": "This tutorial provides an application to hold the message flow, and three input files. There are no other pre-requisites needed by the scenario."