Comment on page
Results panel
The Results panel in Workflows provide information about each node in your workflow. Click on a node to open the panel and see its different sections.
The header of the panel contains general information about the workflow, like the time it was last executed or the connection being used. It also allows expanding to full screen or hiding the panel to leave more space for the canvas.
This tab contains information about the execution of the workflow. Error messages and confirmation for successful runs will appear here.
This tab contains a table visualization of the result of the node's execution.
Next to each column name, you will find this icon 
. Click on it to show some column statistics on the right side of the panel:
For numeric columns, max, min, average and sum are displayed.
For string and date or timestamp columns, the frequency of the top 20 categories is calculated and shown.
The data tab also allows to explore the result in pages of different length, which can be configured in the bottom right corner of the panel:
The copy button 
in the top right corner will copy the content of the current page to the clipboard, using tabs as delimiter, which makes it easy to paste directly into a spreadsheet.
The Map tab shows a preview of the result on a map. It also allows to create a map in Builder using the selected node as data source. When there are more than one columns that could be rendered (several geometry/geography columns, spatial indexes, etc), you can use a selector to make sure the correct column is used in the Builder map.
This tab contains the SQL code that is executed in the data warehouse when the workflow runs from the UI, by clicking on the Run button.
Part of this code handles the creation of temporal tables and other control strategies. These portion of the code is collapsed and hidden by default, but it can be expanded by clicking on the small two dots inline with the code.
The code displayed in the SQL tab corresponds exactly with what is executed in your data warehouse by clicking the 'Run' button in the Workflows UI.
However, this code is different to the one exported or executed via API. In these cases, all the control code is ommitted and CTEs are used instead of temporary tables.
Last modified 8d ago