Interface - Add "CustomFile/Database", similar to the TREE tool to the Text Box, or ....

[fharper]

Please add either or both

1. "CustomFile/Database", similar to the TREE tool to the Text Box interface tool
2. An option to make TREE Tool "silent" or passive when using the "CustomFile/Database" option

The purpose is to provide a better way to pass data, and thus allow "Action" tool to be used, from interface responses in a previous App chained to the current App.

Use Case:

We had a workflow with 8 TREE tools and 3 of them had significant number of rows associated.  This caused frequent failures where the queries getting the multiple layers of data for the TREE would time out.

Through trial and experiment we determined this was the issue by removing TREE tools until we had consistent function.

Most if not all the TREEs and all of the 3 offending TREEs were used to modify FILTER tools, in this case each of those 3 TREEs 3 or 4 Actions driving the same number of FILTERs

So we had to find a way to break up the operation.  Ultimately I separated the 3 large volume TREE tools into a separate workflow to run first and then CHAIN to the original flow with modifications to read the responses passed from the new 1st workflow in the chain and replaced the FILTER with JOINs, effectively filtering by JOIN.

This worked but was extra work and it made me think of the many other situations where I would like to take input from an external source and affect a FORMULA or FILTER or a few other tools where an ACTION is best/only way to modify tool configuration at run time.

I think this lack of a way to use an ACTION tool with a "Non-Interface" data source has probably limited the opportunities of Applications.

Given the division of labor in an APP,

1. run all Interface tools first and modify config of other tools
2. then run the rest of the tools on the canvas

there is no way to make a run time ACTION tool as it must do its job before the core job runs. 

This adaptation of the TREE tool, which is my preference, or the adaptation of the Text Box tool, offer good solutions that should be fairly simple to code and roll out the the user base.

[fharper]

Side note, I want this to be external source in the way it is in the TREE tool, basically it can be unstructured.

doing it like LIST Box or Drop Down would require it be structured as 2 fields, NAME & VALUE which I don't want.

Had this been available when I fixed this Use Case Workflow I could have basically kept all the logic in the original single flow version and modified those 3 TREE tools to read in the file generated by the TREEs in the initial APP of the Chained App version and not had to remove them and replace with JOINS and one or more INPUTs to feed the JOINs.

Had I needed to do something other than filtering I would have been stuck.