The Custom Input Table Processor allows the user to set up a new customizable dataset/table with various options.
It is very common that ONE DATA user wants to work with customized data that can be dynamically modified, and using existing Datasets will not help in that case.
Custom Input Table Processor overcomes this issue, and allows the user to even use variables within the table.
First step is to create new workflow.
Then open the processor of interest (i.e: Custom Input Table Processor).
This interface will appear:
User can add Columns/Rows and fill the cells manually by entering the values. He also can paste them from a spreadsheet and if the table content is invalid the user will get notified (by the upper right cell).
NOTE THAT: when a cell value does not match the column type it belongs to, the cell will become red indicating that it is not valid
One of the most interesting features of Custom input Table is to provide the possibility to integrate variables inside the table and thus making it dynamic.
the variable type here must match the column type in which it is declared.
In the result, the variable value will be shown:
After filling the cells with desired values, the processor will generate the dataset which can be further used by other Processors. We can use a Result Table or a Filterable Result Table(FRT) to visualize the output of the CIT:
More importantly, this processor can provide inputs for other Load Processors such as Multi URL API Load, Flexible REST API, or the Query Helper which need specific input format.
It can happen that newly inserted values are not saved in the Custom Input Table. Even though it seems that changes were applied successfully, as soon as the workflow is executed, the old values appear in the results. When reloading the page, the processor configuration also shows the old values.
This issue appears when the table is saved, but one of the cells is still in edit mode. In other words, when the cursor is still in one of the cells.
To avoid the error, remove the focus from the cells, before clicking "Save".
When the workflow was already executed once, and the green tick is visible, for example at a Result Table, you can make sure the values of table were changed when the tick turns orange.
The video below illustrates the issue: