Filetypes Counter:
- there is now a choice of the dataset model, JSON or XML
- allow a custom time for starting the scanning
- allow the use of an inline text for the path to the file pool
- allow deleting the files in situ instead of injecting them into the flow and when injecting them into the flow there is an option to limit the combined size of the files to be injected to avoid the application data root disk from filling up for very large file pools.
- when all files were deleted from a folder, the files were not deleted, and the job was sent to the error connection. There is now an option to allow this.
- Empty folders were not correctly removed when there were multiple levels of empty folders. This is now done recursively.
- it is now possible to use an inline text for the path to the hot folder to be monitored
- the error handling has been improved. When the hot folder does not exist, the element will not just log a message, but it will go into a fail state so an error notification can be sent (if so configured in the Preferences)
- allow the use of an inline text for the path to the root folder
- you can now specify that the original files have to be left in their original location, with an additional property to ignore updates or not, just as in Submit hierarchy